Skip to content
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

Yume2kki: Shogi Board debug save difference #2207

Closed
purupurupuruin opened this issue May 11, 2020 · 1 comment · Fixed by #2208
Closed

Yume2kki: Shogi Board debug save difference #2207

purupurupuruin opened this issue May 11, 2020 · 1 comment · Fixed by #2208

Comments

@purupurupuruin
Copy link

Name of the game:

Yume2kki (Version 0.112 without hotfix patches)

Player platform:

Linux

Attach files (as a .zip archive or link them)

shogiboarddebugsavebug.zip
easyrpg_log.txt

Describe the issue in detail and how to reproduce it:

Since I was told any incompatibility with debug saves is a bug I decided to report this.
In Shogi Board, loading a debug save in Player or entering the area normally the map looks like this:
shogiunbug

However, loading a debug save made in Shogi Board in RPG_RT the area looks like this:
shogibug
The flying shadows are all glitched looking.
To reproduce:
I attached 2 saves
Save 1 is immediately before Shogi Board, Save 2 is inside Shogi Board
Load the second save in both Player and RPG_RT, wander around the area to see the difference.
Then load the first save in RPG_RT and interact with the pit, Shogi Board looks normal, like when loading the second save in Player.

@Ghabry
Copy link
Member

Ghabry commented Sep 10, 2020

This is fixed by #2208

When loading the attached Player save in #2208 the shadows look glitched the same way as in RPG_RT.
When saving again with #2208 Player and loading in RPG_RT the shadows look correct 👍

Old savegames are "corrupted" and not fixed but switching the map solves it.

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

Successfully merging a pull request may close this issue.

2 participants