Jump to content

server crash when baby beefalo is dead


kokaisum
  • Fixed

i'd make a new world with zero mods

using command c_spawn("babybeefalo") and kill it,then crash
 


Steps to Reproduce

server_log:

[00:06:20]: [string "scripts/stategraphs/SGBeefalo.lua"]:621: attempt to call method 'ShouldKeepCorpse' (a nil value)
LUA ERROR stack traceback:
scripts/stategraphs/SGBeefalo.lua:621 in (field) onenter (Lua) <611-636>
   inst = 106890 - babybeefalo (valid:true)
   load = false
scripts/stategraph.lua:590 in (method) GoToState (Lua) <528-599>
   self =
      timelineindex = 1
      tags = table: 9ABBB360
      mem = table: 9C5178D0
      statemem = table: 9ABBA898
      currentstate = table: 9C21C828
      timeinstate = 0
      sg = Stategraph : beefalo
      inst = 106890 - babybeefalo (valid:true)
      bufferedevents = table: 4D782FC0
      statestarttime = 14.80000077188
      lastupdatetime = 14.833334106952
      laststate = table: 9C432A10
      lasttags = table: 4D781558
   statename = death
   params = false
   state = table: 9C21C828
scripts/stategraphs/SGBeefalo.lua:42 in (field) fn (Lua) <40-44>
   inst = 106890 - babybeefalo (valid:true)
   data = table: 9B14EC80
scripts/stategraph.lua:468 in (method) HandleEvent (Lua) <463-471>
   self =
      timelineindex = 1
      tags = table: 9ABBB360
      mem = table: 9C5178D0
      statemem = table: 9ABBA898
      currentstate = table: 9C21C828
      timeinstate = 0
      sg = Stategraph : beefalo
      inst = 106890 - babybeefalo (valid:true)
      bufferedevents = table: 4D782FC0
      statestarttime = 14.80000077188
      lastupdatetime = 14.833334106952
      laststate = table: 9C432A10
      lasttags = table: 4D781558
   eventname = death
   data = table: 9B14EC80
   handler = table: 9B5C4DB8
scripts/stategraph.lua:479 in (method) HandleEvents (Lua) <473-488>
   self =
      timelineindex = 1
      tags = table: 9ABBB360
      mem = table: 9C5178D0
      statemem = table: 9ABBA898
      currentstate = table: 9C21C828
      timeinstate = 0
      sg = Stategraph : beefalo
      inst = 106890 - babybeefalo (valid:true)
      bufferedevents = table: 4D782FC0
      statestarttime = 14.80000077188
      lastupdatetime = 14.833334106952
      laststate = table: 9C432A10
      lasttags = table: 4D781558
   buff_events = table: 4D782FC0
   k = 1
   event = table: 15CBDA78
scripts/stategraph.lua:154 in (method) UpdateEvents (Lua) <148-157>
   self =
      updaters = table: 9ABBA208
      OnEnterNewState = function - scripts/stategraph.lua:27
      tickwaiters = table: 168ACF58
      haveEvents = table: 9ABBAAC8
      hibernaters = table: 168AD0E8
      instances = table: 168AD2A0
   evs = table: 9C20F688
   k = sg="beefalo", state="death", time=0.23, tags = "nointerrupt,busy,"
   v = true
scripts/stategraph.lua:145 in (method) Update (Lua) <109-146>
   self =
      updaters = table: 9ABBA208
      OnEnterNewState = function - scripts/stategraph.lua:27
      tickwaiters = table: 168ACF58
      haveEvents = table: 9ABBAAC8
      hibernaters = table: 168AD0E8
      instances = table: 168AD2A0
   current_tick = 451
   waiters = table: 9BC6D518
   updaters = table: 9C20F278
scripts/update.lua:288 in () ? (Lua) <224-298>
   dt = 0.033333335071802
   tick = 451
   i = 451

[00:06:20]: [string "scripts/stategraphs/SGBeefalo.lua"]:621: attempt to call method 'ShouldKeepCorpse' (a nil value)
LUA ERROR stack traceback:
    scripts/stategraphs/SGBeefalo.lua:621 in (field) onenter (Lua) <611-636>
    scripts/stategraph.lua:590 in (method) GoToState (Lua) <528-599>
    scripts/stategraphs/SGBeefalo.lua:42 in (field) fn (Lua) <40-44>
    scripts/stategraph.lua:468 in (method) HandleEvent (Lua) <463-471>
    scripts/stategraph.lua:479 in (method) HandleEvents (Lua) <473-488>
    scripts/stategraph.lua:154 in (method) UpdateEvents (Lua) <148-157>
    scripts/stategraph.lua:145 in (method) Update (Lua) <109-146>
    scripts/update.lua:288 in () ? (Lua) <224-298>




User Feedback


A developer has marked this issue as fixed. This means that the issue has been addressed in the current development build and will likely be in the next update.
37 minutes ago, Adgycarp said:

This one was already patched by a dev in an earlier report :thumbsup:

i just tested and not fixed yet

Share this comment


Link to comment
Share on other sites



Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×
  • Create New...