Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

QPlugins Port for RPG Maker MZ

MZ port of QPlugins by Quxios, adapted by LeashaDevGames with bug fixes and customizable code for smoother performance. · By LeashaX

Followers Lag

A topic by Sehanbrel created 62 days ago Views: 36 Replies: 3
Viewing posts 1 to 3

Works pretty well once I got the load order right (all of the Q plugins at the very top). My only complaint is that followers don't work smoothly at all. It runs at one animation frame, stops, runs, stops, runs, over and over, and the followers lag very far behind pretty quick when using anything higher than the default setting of 1 for pixel/tile movement. And even when using the default setting, followers only use the first frame of the walk/run animation, and keep restarting on it.

Unfortunately, this issue persists even in an otherwise bare-essentials test project with only the 5 Q plugins active.

So, I was wondering if you'd be willing to consider implementing a fix for the followers plugin in particular? I would also appreciate if you could include load order guide/instructions to the product page, if it's not too much trouble.

Do let me know if you need anything from me! And thank you for your time.

Developer

Isn’t it due to incompatibility with other plugins? I’m still going to check to see what it can be, if I achieve something I’ll upload an update

I appreciate you checking. I would normally think it's incompatibility as well, but since I tried in a blank test project with no other plugins installed, I think it's just the Q plugins. Might be due to the base engine having recently updated?

Developer (1 edit)

Apologies for the delay in responding. It’s likely a mix of both factors: incompatibility with new versions of RPG Maker MZ and the interaction with newer plugins. Personally, I use the latest version of MZ, and it works fine for me—I use many plugins, and the performance is stable.

My recommendation would be to keep your project as clean as possible from other plugins that might interfere with the movement functions. For instance, plugins like VisuStella’s “Events AND Move Core” often cause issues, and not all pixel movement plugins deliver consistent results. Testing in a project with minimal plugins might help pinpoint whether the problem lies with plugins or something else specific. Additionally, it might be a good idea to place the problematic plugins at the end of the load order. Setting them as a priority by moving their placement sometimes changes how they interact with other plugins. Hope this helps! 😊