Using the Atrox (46238) item crashes clients (incl. vincinity) #398
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: prk/issues#398
Loading…
x
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Describe the bug
Using the Atrox item (46238) crashes the client
To Reproduce
Steps to reproduce the behavior:
Expected behavior
To be changed into an Atrox without crashing, including other nearby players.
Playfield info:
Extended location information:
Server id: 1, character id: 50000:434, time: 2023-12-29 03:12:52 (UTC)
Version: 00.3.6_EP1, map id: NOT FOUND, build: 52606.
Is this an item which should actually be used from the inventory, or a dynel which should be placed in the world, like the buttons in the old character creation playfield/Parnassos?
Pretty minor, either way, considering this is unlikely to happen in regular play
Im not sure where or how the item is to be used in normal circumstances. Only reason that this is reported as it causes player (other than the user) to be disconnected. Perhaps its worth considering adding items that cause crashes to a denylist in order to avoid players crashing another when using such items.
Confirmed.
Using this item indeed crashes the client that used it along with other clients in the vicinity. Upon logging back in, the character that used the item has the body of an Atrox but retains their original head. Other characters in t he vicinity that also crashed are not affected by the Atrox change.
Using the similar Solitus Female item (
/item 46243 46243 1) also crashes the using client and all nearby clients. It may have also caused a playfield crash as attempting to log in immediately after resulted in several minutes of "Server Error" at the login screen.Bumping to priority 1 until it can be confirmed that this isn't causing a backend crash along with the clients.
These items can only be obtained by GMs with access to the item command, and it's not clear whether this item was ever intended to exist in an inventory (vs being used in some background process during character creation or shape changing).
It's the template action message broadcast which is causing crashes, I suspect because the item is invalid, investigating further - if nothing else, item creation should fail
Item is a dynel, only reason it's spawning is because we have an NPC in our database which just so happens to share instance IDs. Item spawning should fail. To fix, prevent creation of template type 70002 with item creation tools at very least.
Most likely parnassos as you already said, just happened to be around there and was struck by the 1 to 1 similarity
Doesn't seem to do anything, Only takes effect after zoning, but at least also doesn't crash the client here :Dchanging this to low priority as it's only possible through a spawned item
Re-closing as this was closed prior to migration from Github.