New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

葬 (Sou): Interpreter hangs after entering to new map #927

Closed
fdelapena opened this Issue Jul 11, 2016 · 1 comment

Comments

Projects
None yet
3 participants
@fdelapena
Contributor

fdelapena commented Jul 11, 2016

Name of the game: 葬 (Sou) v1.03. Download. Contains Japanese files, unpack with unar.

Player platform: Any

Attach files:

Describe the issue in detail and how to reproduce it:

Open the savegame and go downstairs to the next map. Then it won't be able to move.
The game menu showing the items held (Ib style) won't be accessible either, so it looks interpreter related.
Reported by モノ via Android app email bug report.

Note: This was already hanging before merging recent character movement fixes.

@fdelapena fdelapena added this to the 0.4.2 milestone Jul 11, 2016

@Zegeri

This comment has been minimized.

Show comment
Hide comment
@Zegeri

Zegeri Jul 12, 2016

Member

This is caused by an auto-starting event that takes 1 frame to complete. In easyrpg, other events aren't allowed to run their self movements. But in RPG_RT, they can.
There's a deeper problem behind this: auto-starting events that take more than 1 frame shouldn't waste a frame to loop to their beginning (just like repeating move routes). Fortunately, these two issues can be fixed together quite nicely.

94cbf21 should fix this.

Member

Zegeri commented Jul 12, 2016

This is caused by an auto-starting event that takes 1 frame to complete. In easyrpg, other events aren't allowed to run their self movements. But in RPG_RT, they can.
There's a deeper problem behind this: auto-starting events that take more than 1 frame shouldn't waste a frame to loop to their beginning (just like repeating move routes). Fortunately, these two issues can be fixed together quite nicely.

94cbf21 should fix this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment