VWF Dialogues Patch v1.2

Every color is white after a message is done

Seeing people use 1.3 how do you get it?

If you want to combine this with SRAM Plus, edit sram_plus.asm, find sram_locs (around line 48 in the current version), and change $2002 to $6002. Otherwise, save file B will crash the game.

Alternatively, you can change $702000 to $706000 at the top of vwfconfig.cfg. You'll also need to adjust other resources that use VWF dialogues.

Good Patch But I Cannot Install Newest Version (v.1.2)

Is there a way to make all of the text appear instantly? And if so, how? There most likely isn't, I believe.

Thank you for this, this has worked using version 1.7

It seems the patch broke at some point with an Asar update. So currently, your best bet is to use an older Asar version for the patch until it's fixed.

I'm having trouble with applying this patch. I keep getting an error message that includes
warning (W1026) Function "floor" redefined
and many variations on error (E5053) regarding remap RAM
function remap(X) etc wasn't found

I'm assuming this is a problem with the path- I've tried to paste files from the "shared" and "includes" folders everywhere to avoid this problem, but I'm still getting this error message. I would be very grateful for any help on this.

A tool which streamlines the process of inserting this and configuring everything would be highly useful.

If you configure it that way, yes.

does this still let you use the normal message boxes?

A great replacement for Romi's VWF Cutscene Tool, although for me, the text box is glitchy at first blush and can take around two or three dialogues to show up correctly in Higan (and not at all in SNES9x).

I still recommend. 8/10

Cool, that seems like a very practical sheet! Good work!

https://bin.smwcentral.net/u/31439/VWFdialoguesHeader.xlsx
If you use this, you can easily create headers.

16 - bit mode doesn't work.

Bitmode must be either '!8' and '!16'. Simply entering '16' (or likewise '8' for that matter) will just break the code.

Great update. Much friendlier and cleaner compared to the older versions. I also appreciate the new updates made after some of my suggestions, and the width generator is pretty handy for custom text drawers/rippers. Thanks!

I wrote more stuff here regarding the abort dialogue function for those interested or curious about it.

Thanks for the hint! Fixed.

Actually, it’s vwfconfig.cfg now.

Note @Blind Devil: We tried to incorporate most of your feedback given in the previous removal log, but decided against some of it.

• We didn't bother too much fixing any 16-bit mode stuff and instead decided to deprecate it, since probably noone uses it.
• I did not get rid of the .cfg file, because it being separate from the .asm was precisely the point. I wanted the end user to not have to open the .asm file at all to customize the patch, unless doing advanced stuff.

We also weren't able to fix some of the bugs yet, but made sure to mention them in the manual.

below comment: couldn't reproduce on a clean rom + lm with current version of asar (1.50). added a print pc before incsrc vwfmessages.asm (around line 4513 in vwfdialogues.asm) and it gave the same address ($928015) every it was patched

I'd like to warn everybody using this or thinking of using this: the patch, as it is written currently, leaks freespace badly. In fact, some testing I've done has shown that it doesn't even bother removing the message data when you reapply it. In my hack, for example, I lose about 3 KiB of space every time I patch this.

The way freespace is managed here is beyond my comprehension. Despite that, I have found a temporary fix to it. Every time you want to reapply the patch (yes, every single time), turn the header and the first couple of bytes of your first message into a hex string and look for that in a hex editor. You'll arrive at the start of your message data (if you've reapplied the patch a lot of times, you'll have multiple results the first time you do this, 13 in my case; add one autoclean line for every one of those results). Go back 20 bytes and you should be at the start of the RAT (you should have selected the S in STAR, shown in the text view of the hex editor). Take the offset at which the tag is at, turn it into an SNES address with, e.g., Lunar Address, and make an ASM file with the line "autoclean $xxxxxx" in it (replacing "xxxxxx" with the address you got). Patch that to clean the message data. You'll now only lose 22 bytes when you reapply the main vwfdialogues.asm.

I haven't really tested this technique heavily yet, so please make a backup if you'll be attempting it. Also, only do this if you'll actually be reapplying vwfdialogues.asm, because what you're doing here is destroying the message data.

I noticed that you can crouch while a VWF message is on the screen, the "moving player setting" is at 0, you're riding Yoshi annd you're above a solid tile (steping on it).

Just a note when you use this patch: worldpeace made a small fix for a long time when you teleport or die but it's for the old version so you have to do some tweaks to insert the fix to the newer version and (the more important thing) !varram should be changed to $706000 as one save file on a ROM with SRAMPlus patched uses 8192 (8190 usable bytes and 2 for checking if the save is new) or 0x2000 bytes multiplied by 3 as there are usualky 3 save files it uses total 24576 or 0x6000 bytes and because the default address for VWF dialogues is on $702000 there would be a patch conflict. Just my two (pun unintended) cents.

They're done using $EE and $F3 commands, see the switch palace message included on original for details.

How do I make colored ! blocks on the text boxes?

This may be a hard-to understand patch, but it gives the message boxes a whole new great look. Reccomend this to people who are making big time proyects and such.