Post by Tamschi in R-Stick Mouse MV + MZ comments

Viewing post in R-Stick Mouse MV + MZ comments

Hm… for what it’s worth, this shouldn’t need specific support for anything other than cursor-change plugins.

If the other plugin polls TouchInput like the engine does, or hooks functions other than the ones below, it should work regardless of load order.
If the other plugin hooks uses TouchInput._onMouseDown and/or TouchInput._onMouseUp, then load this plugin after the other one.

Though, some plugins do indeed use custom mouse event handlers, which means they won’t see the ones this plugin here generates.
Since the VisuStella team updated their plugin (https://itch.io/post/12238393), please try again with the updated version to see if it’s compatible.

RagnarokAesthetic315 days ago(+1)

So I tried your plugin with the updated picture common events, still same issue. Tried my friend's code fix, works fine. So maybe you need to see the code to see what changes were made. Picture common events no longer crashes, but it seems not to work with your plugin in the sense of using picture common event menus. Feel free to reach out for more info or a contact so I can show you the code.

Best,
Ragnarok Aesthetic

Tamschi315 days ago (2 edits)

Sure, though it seems you don’t have published contact details I can use. (Your website has expired.)

You can find my up-to-date contact information here: https://itch.io/blog/480852/tamschis-support-contact-information-inquiries

Note that I won’t look at the edited code without explicit permission to implement the fix on my end, just for legal safety.

Edit: I think the easiest option would be to send the edited plugin via email.

RagnarokAesthetic314 days ago

Won't let me send via gmail, such a headache but I did send a request on discord if you want me to send it there for you.

Tamschi314 days ago (2 edits)

Just as public follow-up, there were no functional edits in the modified version.

There were global functions added to revert/restore the overall input mapping, but this is already available via the API by manipulating Input.gamepadMapper[TSC_RStick_Mouse.parameters.leftClickButton] (with TSC_RStick_Mouse.INTENT_MOUSE_LEFT as value that enables the mapping). You can also disable the initial mapping in the plugin settings.

I generally recommend using the API rather than editing plugins in order to make updating them easier.