GHABRY'S PROFILE

I would like to request a callback "onMoveCommand" which is invoked when any movement command of a move route is executed. (not when the MoveCommand event is executed but a MoveRouteItem of a MoveRoute)

I could also write the hook for this callback on my own, but the address of the "execute move route" function would be super useful. Maybe @PepsiOtaku or @Corti have an idea?

I need this for unit tests in EasyRPG (comparing RPG_RT behaviour with Player). Useful to automatically find bugs and regressions.

"(You can actually get those monsters back into battle with that event command that shows (right click'd) hidden monsters). "

Of wow. That's silly. Something new learned. Mass self destruction with reappear each turn, that's evil ;)

Yes, we don't have any development priorities, everybody contributes what he wants. We do it this way since years and it works. It could be probably speeded up with a tighter roadmap but where is the fun in this? There is only some small planning done in IRC to prevent that multiple people program the same.

You are only one person that invests a lot of your freetime in one project, that's fine - it's your freetime so you can assign it freely. We are usually around 3-4 developers but the Player isn't a full-freetime task for any of us, that's why it's going so slow. For me it isn't a high priority task either, sometimes I don't contribute anything for weeks. This slows down the project, but I don't care because my other hobbies profit from my additional time.

Some important "core" features that were missing since years were finally contributed some weeks ago. E.g. Vehicles (Boat, Airship, ...) they were not extremely difficult to program but there was never the need by anyone until a few weeks ago to implement them. Now they are in and many more games playable, cool. Looping maps will also come in the next weeks, this is the last missing component to make Yume Nikki fully playable. The undocumented LSD savegame format is also making further progress in being understood, from ~30% documented fields at the beginning we are now already at ~70%. This is a very time consuming task because you can only figure it out via reverse engeneering or try&error.
The progress is slow but steady. Someday we will be finished and being full compatible but I can't say when but I guarantee it will happen.

The ports are just some side projects when a developer is currently not motivated to do normal programming on the Player and wants to do something else because it's fun. Emscripten was just a funny project to play around with a new technology. Or say the Android port, one could argue that this is not core functionality that contributes to a better game experience but it makes many people happy that they can enjoy there games on there smartphones/tablets. And the cost of maintanance after the port is finished is usually almost zero because everything is compiled automatically.

Of course it's a shame that there is no visible progress for the editor but when only one person works on it and this one has no time for it (even other hobbies can be a reason, not only work) then this is fine. I won't blame him for not working for months on it, it's not his job so he can halt it as long as he wants.
I'm not interested in an editor therefore I only contribute to the Player. The same seems to be the case for the other developers, nobody of them works on the Editor and we can't force them.

Basicly it's possible to simulate DynRpg functionality by reimplementing the functions provided by the plugins.
But depending on the plugin that is a lot of work because we don't share any code with the original RPG maker. Plugins like (elsemini) math and datetime are e.g. simple.
For this part I'm open for discussion (and code patches are welcome ;)).

The hugher pain are the DynPatches that are patching arbitrary in memory locations to move e.g. GUI elements around. It is possible to emulate this, too. But that is so extreme ugly... that I don't want it.

I had a similiar problem after installing a new version.
Try terminating it (e.g. with Advanced Task Manager) or reboot your phone.