SM63Redux
SM63Redux copied to clipboard
GTcreyon
Overlapping cherry clones do not move correctly
Describe the bug i- at this point i dont know anymore it feels like a blj but easier to do just check the screen recording
To Reproduce
just use /cherry more than once, and press right.
if you do this on any screen but the first, you just move to the previous screen.
but on the first screen, theres no screen transition, so you just clip into (and this never happened until this recording, but sometimes through i guess)
Expected behavior multiple marios appear, and move at normal speed
Screenshots video was too big so its compressed to about 49% of the original size https://user-images.githubusercontent.com/83524620/214115475-b79c0bd6-d79a-4581-b823-879bf3d4c697.mp4 what the hell is happening at some point i start hitting random keys i think at least 1 clone didnt clip and is playing as normal, hence the damage and transition at the end what the hell is this fludd btw some kind of emergency hover fludd?
System Information
- OS/Browser: Chrome OS/Chrome
- Game version: v0.1.5
- Other specs: its a chromebook idk
Additional context other times when i tried this, i never clipped through the wall lmao, just stuck in the wall also faceplanting (down thing) before moving kinda cancels momentum but makes the game hell sometimes the only way to get at least 2 working cherry clones without blj speed happening is to move before spawning a new clone because the previous clone gets left where you stood when the command was executed
This occurs because cherry clones sometimes overlap when spawned. This messes with the collision. This would never be an issue in real gameplay, it's just an issue with how the command places cherry clones, and should be easy to fix.
That said, when writing issue reports, please be courteous and considerate. Here are some tips that might help:
- Try to write descriptive issue titles. It's not helpful if I have to change it because you wrote something unnecessarily vague.
- Please try to be constructive and concise. You can remove "what the hell is happening" and "lmao" and the meaning is still there.
- Please describe the issue, rather than only saying to check the recording or look at screenshots. Even a brief description can be helpful.
- Avoid padding the body of your message with content that doesn't add to the discussion. "at this point i dont know anymore" doesn't help us understand the issue. If you want to express your confusion, that's fine, but you can do that more clearly by simply saying "I don't understand what's happening."
- Avoid asking irrelevant questions during an issue report. "what the hell is this fludd btw" is not relevant to the cherry clone issue.
I don't generally want to be policing the way you choose to talk, and the contributions you make with issue reports are much appreciated. Providing a video recording is particularly useful, and I applaud you for that. But do remember that we do have to read these, re-read them, discuss them with the team, and then read them over again to make sure we've fixed them properly. That experience is much nicer when you write a nice report.
Ok, thanks! And yeah, sorry for the vague issue, i just didnt know how exactly to say what i wanted to, sorry.
On Mon, Jan 23, 2023, 2:13 PM Tricia @.***> wrote:
This occurs because cherry clones sometimes overlap when spawned. This messes with the collision. This would never be an issue in real gameplay, it's just an issue with how the command places cherry clones, and should be easy to fix.
That said, when writing issue reports, please be courteous and considerate. Here are some tips that might help:
- Try to write descriptive issue titles. It's not helpful if I have to change it because you wrote something unnecessarily vague.
- Please try to be constructive and concise. You can remove "what the hell is happening" and "lmao" and the meaning is still there.
- Please describe the issue, rather than only saying to check the recording or look at screenshots. Even a brief description can be helpful.
- Avoid padding the body of your message with content that doesn't add to the discussion. "at this point i dont know anymore" doesn't help us understand the issue. If you want to express your confusion, that's fine, but you can do that more clearly by simply saying "I don't understand what's happening."
- Avoid asking irrelevant questions during an issue report. "what the hell is this fludd btw" is not relevant to the cherry clone issue.
I don't generally want to be policing the way you choose to talk, and the contributions you make with issue reports are much appreciated. Providing a video recording is particularly useful, and I applaud you for that. But do remember that we do have to read these, re-read them, discuss them with the team, and then read them over again to make sure we've fixed them properly. That experience is much nicer when you write a nice report.
— Reply to this email directly, view it on GitHub https://github.com/GTcreyon/SM63Redux/issues/55#issuecomment-1400847093, or unsubscribe https://github.com/notifications/unsubscribe-auth/AT5HYDFPEZWEPPSPPJ55BN3WT3J67ANCNFSM6AAAAAAUEFAEEI . You are receiving this because you authored the thread.Message ID: @.***>
Ok, thanks! And yeah, sorry for the vague issue, i just didnt know how exactly to say what i wanted to, sorry.
It's okay. Just a request for the future.