Hmm, not too familiar with the structure of MZ projects, but is the actual function defined on every object? I figure there is some place upstream where you are calling some kind of randomizer, where the randomizer function can be replaced with something custom?
I can take a look in the code and see if I can figure it out sometime, and let you know if I see anything.
Alright, taking a look, I was able to make a ‘mini-plugin’ that hijacks your display function and de-randomizes it. It catches it automatically whenever an object gets touched, so nothing has to change in the data.
The changes are adding one file to the js/plugins directory and then registering the plugin at the js/plugins.js file.
I’ll share these via pastebin, not sure what a cleaner way would be.
This first one is LoopDialogue.js, that’s the ‘hijacker’. It goes in the js/plugins/ directory. This is the code, but unless registered it doesn’t do anything on it’s own.
This second one is the adjusted plugins.js file. What I did here is add the plugin I made (LoopDialogue.js) as the final entry, it looks like this:
{“name”:“LoopDialogue”,“status”:true,“description”:“Fixes random dialogue loop.”,“parameters”:{}}
You can either replace js/plugins.js with this file entirely, or just add the line above as the last item. Either way, make sure and save a backup of plugins.js, in case something goes wrong. The first bit of code won’t have any effect on its own.
I haven’t tested it extensively, but I’ve modified my own and it seems to be working fine, and covering all the objects.
Feel free to contact me if anything doesn’t make sense or goes wrong, and please don’t go back and edit the logic object-by-object, that’s no fun at all!
