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
So I think this issue is noteworthy that it warrants an entry.
This issue exists in
the current live build,
in the current dev build with the mechanism PR by @Gingerbeard5773#2219
and in the obsolete bloody blobs PR by me #1854
Because onSetStatic() in Spiker.as gets run after rejoining, the attachment point offset on spiker gets set to Vec2f(0,-3);.
This code makes sense when first placing the spiker but when rejoining, it could set the offset to this Vec2f even when there already is a spike attached, so it looks incorrect.
It can be fixed by first checking if there already is a spike attached and setting the offset accordingly.
The text was updated successfully, but these errors were encountered:
Description
So I think this issue is noteworthy that it warrants an entry.
This issue exists in
the current live build,
in the current dev build with the mechanism PR by @Gingerbeard5773 #2219
and in the obsolete bloody blobs PR by me #1854
Because
onSetStatic()
inSpiker.as
gets run after rejoining, the attachment point offset on spiker gets set toVec2f(0,-3);
.This code makes sense when first placing the spiker but when rejoining, it could set the offset to this Vec2f even when there already is a spike attached, so it looks incorrect.
It can be fixed by first checking if there already is a spike attached and setting the offset accordingly.
The text was updated successfully, but these errors were encountered: