Thanks. I know roughly why this happens: Sprite_Cursor is a Sprite_Picture so that Dynamic Pictures can be used to make it dynamic. It seems that VisuStella Picture Common Events assumes Sprite_Picture appears only under specific circumstances and/or never has a pictureId of 0. (I chose that ID specifically to avoid interference with other plugins, since for example in this case any other would risk turning the cursor into a button.)
Normally this would be easy to figure out and patch, but there are two reasons I don’t provide further support in this case:
-
The plugin is not publicly available. I can’t efficiently debug something I don’t have access to.
Their Terms of Use also explicitly forbid you from sharing it with me, as it has to be repurchased for each developer who works with it separately.
(It’s fine to (privately) share my plugins within your team freely. I only care about how many entities publish games with them.)
-
Second, as you can tell by the
<computed>in the stack trace, VisuMZ plugins are obfuscated. That makes it, mildly put, difficult and/or cumbersome for other plugin creators to ensure compatibility.(I guess I care too much about providing a good product to do that. The obfuscation also hurts performance of the finished game.)
You’ll have to ask Team VisuStella about it. For what it’s worth, fixing it (assuming it’s the only incompatibility) shouldn’t take them more than ten minutes or so and would improve compatibility of their plugin in general, not just with R-Stick Mouse.