Resolved: Weapon causing access violation
 

Through working on a weapon on server "Versus", I have found what seems to be a bug!

When I fire the weapon, and then update the script again, I get "Access violation at address 00000000. Read of address 00000000."

The weapon then deletes itself from the client (but not the attributes), and only reappears when the script is next updated/logging onto the server again.

However! If you do not fire the weapon, then script updates do not cause a problem.

Nothing is output to the F2 console about the weapon, or any errors.

The weapon name is "Axe" on the server "Versus", and this does not happen with other weapons.
(Edit) It does with the Wood Cutting Axes too, but similar scripting. (Edit)
I have also never experienced this before now.

I can't really post the script, but if someone could please check this out, I would appreciate it.

I remember getting the same error every now and then when working with weapons. But I don't remember the weapon leaving from attributes.

EDIT (in repsonse to below):
Sorry, I meant that I didn't remember the weapon leaving the client.

Well, like I said, it didn't leave the attributes.

IT has done this to me a couple of times too. I'd like to know how to fix it.

Yeah. We've been getting that on Versus. You have to remove the NPC(s), and it gives you another access violation when you remove them, then you have to add them back. After you add them back it's fine, but it's really annoying.

I get the same access violation when I hit F3 sometimes. Then all the boxes magically uncheck themselves, text size increases, then text size increases additionally after I hit F3 again. It also steals all audio from my speakers coming from Graal.

I checked the problem, the attr[] variable was not protected and it was possible to overwrite it by your own array, but the engine doesn't expect the attr[] variable to disappear, so it crashes / gives an error. I have fixed it in my v4 version, please also don't use this.attr[] for storing temporary variables since it is not meant for that.

Ah, thank you for sorting that.