You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
definee=Character('Eileen', color="#c8ffc8")
imageeileen=Transform("images/eileen happy.png")
transformt:
linear1.0xpos0.5labelstart:
"BUG REPRO: trailing colon after show at statement does not cause parse error, but changes behavior: character warps to left before moving"showe:
xpos0.7"Ready to move?"# 1. Uncomment this for expected behavior# show e at t# 2. Uncomment this for odd behaviorshoweatt:
"Moving!"return
Run with line 1. uncommented to see expected behavior.
Run with line 2. uncommented to see odd behavior: character warps to left (apparently due to xpos reset) before moving to target position
Oddly enough, even when I used a colon with actual code below to change sprite xoffset, the xpos seemed to reset as well. So maybe the colon is actually setting up something in all cases, then since there is no code below to set positions, the default values show off?
The text was updated successfully, but these errors were encountered:
MWE
Repro bug - Trailing colon after show at caused property reset.zip
Or just the code below in your script.rpy:
Run with line 1. uncommented to see expected behavior.
Run with line 2. uncommented to see odd behavior: character warps to left (apparently due to xpos reset) before moving to target position
![Renpy 8 1 1 trailing colon show at reset property](https://private-user-images.githubusercontent.com/1067772/249611444-c6b5bc11-b8d3-4969-b4b7-4c3093341d86.gif?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjA0MTc3ODcsIm5iZiI6MTcyMDQxNzQ4NywicGF0aCI6Ii8xMDY3NzcyLzI0OTYxMTQ0NC1jNmI1YmMxMS1iOGQzLTQ5NjktYjRiNy00YzMwOTMzNDFkODYuZ2lmP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI0MDcwOCUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNDA3MDhUMDU0NDQ3WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9MmQ1MzkyN2YyYTAyNmM3ZWJkMTA1ODBkZWI2ZDkxNDBjNzlkNTM3ZTcwODAzYmUyNDE5ZTEzMTk3Zjk0MmQxYyZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QmYWN0b3JfaWQ9MCZrZXlfaWQ9MCZyZXBvX2lkPTAifQ.fTl6oI6U54GvY_XkxUOx5g_1mjP26f2Udsz9B28o5cc)
Oddly enough, even when I used a colon with actual code below to change sprite xoffset, the xpos seemed to reset as well. So maybe the colon is actually setting up something in all cases, then since there is no code below to set positions, the default values show off?
The text was updated successfully, but these errors were encountered: