@Galv
It's bugged. All of my message boxes use the same format, and yet after some input, it breaks. The \pop command no longer works for a few messages.
I've uploaded a video demonstrating it.
I have tested this in my demo project but cannot replicate. I have a feeling it might be a plugin conflict. If you can replicate the issue in a new project, please let me know how. Else you might need to do tests to see which other plugin is conflicting.
I have tested this in my demo project but cannot replicate. I have a feeling it might be a plugin conflict. If you can replicate the issue in a new project, please let me know how. Else you might need to do tests to see which other plugin is conflicting.
Huh, you are right - that's odd. Thanks for letting me know, I will investigate why that is happening.Hi Galv. I have a question (probably dumb).
What if I change the resolution of the game? How do I align the message arrow on the top of the event?
It doesn't seem to align properly at my resolution (1104x624).
Thanks in advance.
Still doing it in new project with just your plugin. Only on the line where the \n[1] is called in the message box.
Huh, you are right - that's odd. Thanks for letting me know, I will investigate why that is happening.
I still cannot replicate this issue. If you are sure you have the latest plugin version, are you able to upload the fresh project it is happening in so I can take a look?
EDIT: The positioning of the windows is off when using a different screen size to the UI area size.
This will be fixed in an update soon!
No, sorry - that was an unrelated issue.So my custom resolution is breaking the \n command in \pop?
My resolution is set to 1280*720 for both.
Thank you for this - I notice that it happens when the \n[x] is on the first line and comes after the \pop[x].
For a quick fix for now, put the \pop command at the end of the first line as that appears to work.
I will investigate why this happens when I am able.
Ahh thank you! That does work.
I usually put my message format coding at the beginning of my lines so I didn't think about trying it at the end. I didn't really think it mattered. But thank you for investigating the issue for me.
It was just a bug on my part - I have fixed it now in version 1.8 - should be able to put it anywhere on the first line now.