players getting kicked with jackhammer

I had a player report this to me yesterday. they reported that they got kicked after using a jackhammer on a meteor. I asked if it was the big one that need explosives and they said no.

I just tested this and it happens when you use a jackhammer on a "Normal" sulfur meteor. I pulled this from the log so I hope this helps. update this will happen on any Normal Meteor using a jackhammer.

 

NullReferenceException: Object reference not set to an instance of an object
  at OreResourceEntity.OnAttacked (HitInfo info) [0x0006f] in <fa5bc33ffcdf4090ada554e73762793f>:0 
  at BaseMelee.DoAttackShared (HitInfo info) [0x00037] in <fa5bc33ffcdf4090ada554e73762793f>:0 
  at BaseMelee.PlayerAttack (BaseEntity+RPCMessage msg) [0x00939] in <fa5bc33ffcdf4090ada554e73762793f>:0 
  at BaseMelee.OnRpcMessage (BasePlayer player, System.UInt32 rpc, Network.Message msg) [0x001d9] in <fa5bc33ffcdf4090ada554e73762793f>:0 
UnityEngine.DebugLogHandler:Internal_LogException(Exception, Object)
UnityEngine.DebugLogHandler:LogException(Exception, Object)
UnityEngine.Logger:LogException(Exception, Object)
UnityEngine.Debug:LogException(Exception)
BaseMelee:OnRpcMessage(BasePlayer, UInt32, Message)
Jackhammer:OnRpcMessage(BasePlayer, UInt32, Message)
BaseEntity:SV_RPCMessage(UInt32, Message)
ServerMgr:OnRPCMessage(Message)
ServerMgr:OnNetworkMessage(Message)
Facepunch.Network.Raknet.Server:ConnectedPacket(Connection)
Facepunch.Network.Raknet.Server:Cycle()
ServerMgr:Update()

6 hours ago, LizardMods said:

I had a player report this to me yesterday. they reported that they got kicked after using a jackhammer on a meteor. I asked if it was the big one that need explosives and they said no.

I just tested this and it happens when you use a jackhammer on a "Normal" sulfur meteor. I pulled this from the log so I hope this helps. update this will happen on any Normal Meteor using a jackhammer.

 

NullReferenceException: Object reference not set to an instance of an object
  at OreResourceEntity.OnAttacked (HitInfo info) [0x0006f] in <fa5bc33ffcdf4090ada554e73762793f>:0 
  at BaseMelee.DoAttackShared (HitInfo info) [0x00037] in <fa5bc33ffcdf4090ada554e73762793f>:0 
  at BaseMelee.PlayerAttack (BaseEntity+RPCMessage msg) [0x00939] in <fa5bc33ffcdf4090ada554e73762793f>:0 
  at BaseMelee.OnRpcMessage (BasePlayer player, System.UInt32 rpc, Network.Message msg) [0x001d9] in <fa5bc33ffcdf4090ada554e73762793f>:0 
UnityEngine.DebugLogHandler:Internal_LogException(Exception, Object)
UnityEngine.DebugLogHandler:LogException(Exception, Object)
UnityEngine.Logger:LogException(Exception, Object)
UnityEngine.Debug:LogException(Exception)
BaseMelee:OnRpcMessage(BasePlayer, UInt32, Message)
Jackhammer:OnRpcMessage(BasePlayer, UInt32, Message)
BaseEntity:SV_RPCMessage(UInt32, Message)
ServerMgr:OnRPCMessage(Message)
ServerMgr:OnNetworkMessage(Message)
Facepunch.Network.Raknet.Server:ConnectedPacket(Connection)
Facepunch.Network.Raknet.Server:Cycle()
ServerMgr:Update()

 

Yeah, This problem is listed on main plugin page. I tihnk i found solution for that, but right now i am tryign to improve the meteor display (sometimes, in rare cases they are invisible) and will release it in new version.

Changed Status from Pending to Closed

Changed Fixed In to 1.2.0

I was going to put in another tick. when I first loaded the updated version there was a weird bug when using the jackhammer. It would only mine on the hot spot. this was happening on vanilla ore as well. but then I fully unloaded the plugin to test this and after loaded the plugin it just work. maybe there was something still in memory but it works now.

anyway thanks for the quick fix.

On 7/19/2022 at 9:21 AM, LizardMods said:

I was going to put in another tick. when I first loaded the updated version there was a weird bug when using the jackhammer. It would only mine on the hot spot. this was happening on vanilla ore as well. but then I fully unloaded the plugin to test this and after loaded the plugin it just work. maybe there was something still in memory but it works now.

anyway thanks for the quick fix.

Fixed in 1.2.1, will release today/tommorow another version with few extras.