-
Notifications
You must be signed in to change notification settings - Fork 565
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
Weird floating nested guy #4561
Comments
I think one way to reproduce was to have shaking marines before nesting. Coffee or neurotoxin. I noticed it happened once when a marine was shaking then nested sometimes they pop out like that |
I think that has to do more with #4547 then this one. In that issue, the nest is still on the wall, but the person is floating away from the nest. In this issue, the nest is floating, but the person is secured in the nest with correct position. i think this is probably(?) a mapping issue, like a xeno spawn is in the middle of the room instead of on the wall of the room |
Yeah this is probably due to setting initial() x and y offsets somewhere but the issue is the entire thing needs changed so we have a list of things offsetting our mob with references to what has offset it so when one offset stops we recalculate our total offset rather than set back to original offset. (This is when I looked into this like six months ago so I may be misremembering). |
Testmerges
#4505: 'Get Flat Icon Fixes' by Drulikar at commit 6021245 #4391: 'Hijack objectives' by morrowwolf at commit c34cb00 #4534: '"Fixes" missing window frame icon states' by morrowwolf at commit 7cf004c #4535: 'Floodlight rework' by morrowwolf at commit 311b510 #4549: 'Helmet Optics Update' by morrowwolf at commit a7820b1 #4550: 'Xeno structure cheese reduction' by morrowwolf at commit 54f1154
Description of the bug
I saw this midround on LV-522: Chance's Claim. No clue what causes it. The nest is not near any walls whatsoever, but still nested.
What's the difference with what should have happened?
Nests should be on walls.
How do we reproduce this bug?
...
Round ID was 18881 if that helps.
Issue Bingo
The text was updated successfully, but these errors were encountered: