sv: Expression 2 (LOCATOR_E2_WIP_volume control_DEADLYSHIT!): entities/gmod_wire_expression2/core/custom/damagecore.lua:545: attempt to call method 'CPPICanDamage' (a nil value)
when trying to kill an NPC this issue comes up and then the e2 has to be reset in order to work..........i removed a line of code that when i tried to kill an NPC before it would flat out crash the server/game but now it does this can you please redo this wonderful addon to allow killing players/and npc with out an issue? cause my server uses it and when this issue comes up its game breaking :(
Not exactly sure why, but using blast damage causes gmod to crash.
E2 code that i used was only using the standard e2 functions and DamageCore.
Here's a Lua traceback from the minidump:
-Lua Stack Traces-
Client Not in Lua call OR Lua has panicked
I had this crash 3 times, and they all have the same error.
It might also be my awful E2 coding abilities, but the error does not occure always, and the
E2 code is validated.
I've just added a check to Wiremod to prevent this kind of thing from happening, which means that in the July 2018 Release, instead of damagecore breaking E2Helper, it will instead fail to load with the error:
There was an error loading the custom/damagecore.lua extension. Please report this to its developer. entities/gmod_wire_expression2/core/custom/damagecore.lua:95: malformed type ID 'dmg' - type IDs must be one character long, or three characters long starting with an x
my e2 uses this core and ever single time i try to use it on a player i get this error: sv: Expression 2 (LOCATOR_E2_COMPLETE_WITH_DISH_updatedmost_22A): entities/gmod_wire_expression2/core/custom/damagecore.lua:323: bad argument #1 to 'pairs' (table expected, got number)
A lot of users that have both wiremod and this extension are encountering issues and I think it would be best if you added a disclaimer to the workshop or something that this is the case.
You could also add this to the top of the core file to print out a warning or prevent itself from running:
ifWireLib.CanDamagethen...end
But that part is more on our side to handle registerType conflicts better.