I found another bug... if you use a message code like \first from yanfly's message system... then the pop window will do the same it was doing before version 1.09. Not huge deal, but it makes it so you can't bold or italics anything.
Galv's Message Styles
● ARCHIVED · READ-ONLY
-
-
I have just gone back and tested with yanfly's message system again.
- I do not see a \first code in Yanfly's message system.
- I can successfully italic and bold text using \fi and \fb without any issues.
Please make sure you have latest version of all plugins and do the usual disabling plugin tests to try to work out if it's another plugin conflicting. Try to replicate it in a fresh project (or this plugin's demo) -
Apparently the order matters when you put the code in... if the \auto is before \fi then the bug happens... not true if you put it after.
-
I don't see a \auto command yanfly's message system either. Am I missing something?
As long as you got it working now, that's good. -
I don't see a \auto command yanfly's message system either. Am I missing something?
As long as you got it working now, that's good.
It's a code from the ExtMessPack1, an extention to the Message Core. It make it's so the message box is only as big as the text. You can also do autoevent[x] and the message will float over an event. It works great with your message styles to make a comic style dialogue. As long as you leave the faces off... -
When reporting any bugs, please provide the full details. You didn't mention this plugin extension.
I had a look at the it and it looks like it does nearly everything the Message Styles plugin does? If there are issues it might be best to use one or the other. -
When reporting any bugs, please provide the full details. You didn't mention this plugin extension.
I had a look at the it and it looks like it does nearly everything the Message Styles plugin does? If there are issues it might be best to use one or the other.
I thought that the extension Pack was understood as part of the message core since it was written by Yanfly and posted months ago. The extension pack does do a lot of what this plugin does, but it doesn't add the tail at the bottom to indicate who is actually talking. I find that tid bit to be important, since it doesn't look right other wise.
So far there aren't any game ending issues, just minor visual ones. I've worked out the things that need to done to work around those issues so no problems at all anymore. -
Hi, Galv! Great plugin, I plan to use it, but I found an issue: if I put an message code, like "\!", "\|" or "\.", it's executed before the message. Or is my hesitation?
I'm having this issue when I use the <br> to manually line break the message... Not sure why, since I thought I had fixed it. I guess I didn't. -
I will test that out when I get time
-
I will test that out when I get time
Thanks... -
No response from MB on making this compatible with MapZoom....
-
I just discovered that, if you put this plugin above Yanflys' Message Core Plugin, it does not work.
If you put it below, it works fine.
Just saying, in case anybody has faced the same problem as me :) -
In general you should always put core plugins first :)
-
Is there a way to change the bubble arrow in-game? Like say you want to swap it from the standard arrow to a thought bubble's kinda thing?
(If it's not possible, then no big deal, I'll just work around it somehow) -
Sorry, not in the current plugin. I will see about adding changes like that when I finish a lot of my to-do list :)
-
Ah, ok! Good luck with your to-do list, then! I know how tough those can be sometimes :rswt:
-
The plugin is really nice, good job on that, Galv! :D
Did I miss how to make the Dialogbox follow the Mainhero?
I looked in the Demo and could see that you tied a variable to it but how do you do it in the Mainhero (Sorry if that's a stupid question ;))? -
You can use \pop[-1] for the first position in the party (so it will display on the leader)
-
Would there be an option to disable/enable this with plugin commands in future? It's just, I'd probably need to use the regular for some tutorial texts and other things like that and can't really make use of this style right now.
-
Yeah on my to-do list is adding ability to change windowskins which would mean normal message can be done