Jump to content

Plants crash


cezarica
  • Fixed

Running version 442776 Master shard crashed with this error:

[08:06:19]: Stale Component Reference: GUID 582985, scripts/prefabs/farm_plants.lua:179
[08:06:19]: [string "scripts/prefabs/farm_plants.lua"]:180: bad argument #2 to 'FindEntities' (number expected, got nil)
LUA ERROR stack traceback:
=[C]:-1 in (method) FindEntities (C) <-1--1>
scripts/prefabs/farm_plants.lua:180 in (upvalue) KillJoyStressTest (Lua) <178-181>
   inst = 582985 - farm_plant_watermelon (valid:false)
   currentstress = nil
   apply = true
   x = nil
   y = nil
   z = nil
scripts/prefabs/farm_plants.lua:217 in (upvalue) MakeStressCheckpoint (Lua) <213-245>
   inst = 582985 - farm_plant_watermelon (valid:false)
   is_final_stage = nil
scripts/prefabs/farm_plants.lua:450 in (field) pregrowfn (Lua) <449-451>
   inst = 582985 - farm_plant_watermelon (valid:false)
scripts/components/growable.lua:79 in (method) DoGrowth (Lua) <70-97>
   self =
      task = PERIODIC 582985: 353.000000
      targettime = 28792.33481656
      stages = table: 0xe48f7a0
      magicgrowable = true
      inst = 582985 - farm_plant_watermelon (valid:false)
      growoffscreen = true
      stage = 2
      domagicgrowthfn = function - scripts/prefabs/farm_plants.lua:533
   stage = 3
scripts/components/growable.lua:19 in (field) fn (Lua) <18-20>
   inst = 582985 - farm_plant_watermelon (valid:false)
   self =
      task = PERIODIC 582985: 353.000000
      targettime = 28792.33481656
      stages = table: 0xe48f7a0
      magicgrowable = true
      inst = 582985 - farm_plant_watermelon (valid:false)
      growoffscreen = true
      stage = 2
      domagicgrowthfn = function - scripts/prefabs/farm_plants.lua:533
scripts/scheduler.lua:177 in (method) OnTick (Lua) <155-207>
   self =
      running = table: 0xe6d01b0
      waitingfortick = table: 0xb238c40
      tasks = table: 0xed6d1c0
      waking = table: 0x264234a0
      attime = table: 0xe682440
      hibernating = table: 0xee5d930
   tick = 863769
   k = PERIODIC 582985: 353.000000
   v = true
   already_dead = false
scripts/scheduler.lua:371 in (global) RunScheduler (Lua) <369-377>
   tick = 863769
scripts/update.lua:185 in () ? (Lua) <164-243>
   dt = 0.033333335071802
   tick = 863769
   i = 863769
[08:06:20]: [string "scripts/prefabs/farm_plants.lua"]:180: bad argument #2 to 'FindEntities' (number expected, got nil)
LUA ERROR stack traceback:
    =[C]:-1 in (method) FindEntities (C) <-1--1>
    scripts/prefabs/farm_plants.lua:180 in (upvalue) KillJoyStressTest (Lua) <178-181>
    scripts/prefabs/farm_plants.lua:217 in (upvalue) MakeStressCheckpoint (Lua) <213-245>
    scripts/prefabs/farm_plants.lua:450 in (field) pregrowfn (Lua) <449-451>
    scripts/components/growable.lua:79 in (method) DoGrowth (Lua) <70-97>
    scripts/components/growable.lua:19 in (field) fn (Lua) <18-20>
    scripts/scheduler.lua:177 in (method) OnTick (Lua) <155-207>
    scripts/scheduler.lua:371 in (global) RunScheduler (Lua) <369-377>
    scripts/update.lua:185 in () ? (Lua) <164-243>
    
[08:06:20]: Warning: Widget:SetFocusFromChild is happening on a widget outside of the screen/widget hierachy. This will cause focus moves to fail. Is     ScriptErrorWidget    not a screen?    
[08:06:20]: stack traceback:
    scripts/widgets/widget.lua:605 in (method) SetFocusFromChild (Lua) <602-627>
    scripts/widgets/widget.lua:624 in (method) SetFocusFromChild (Lua) <602-627>
    scripts/widgets/widget.lua:624 in (method) SetFocusFromChild (Lua) <602-627>
    scripts/widgets/widget.lua:656 in (method) SetFocus (Lua) <629-665>
    scripts/widgets/menu.lua:83 in (method) SetFocus (Lua) <74-85>
    scripts/widgets/scripterrorwidget.lua:109 in (method) OnUpdate (Lua) <102-119>
    scripts/update.lua:95 in () ? (Lua) <33-134>    
[08:06:20]: Stale Component Reference: GUID 582985, scripts/prefabs/farm_plants.lua:179
[08:06:20]: Stale Component Reference: GUID 582985, scripts/prefabs/farm_plants.lua:179


Steps to Reproduce

See above trace, I wasn't online at the time.




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.


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...