Issue Data
|
Issue #27368: DoorChain: Cannot call abBusy()/abChained() on a None object
[09/03/2019 - 05:31:06PM] error: Cannot call abBusy() on a None object, aborting function call
stack: [ (0601ED0E)].doorchain.Chained.OnActivate() - "g:\_F4\Art\Raw\Scripts\DoorChain.psc" Line 44 [09/03/2019 - 05:31:06PM] error: Cannot call abChained() on a None object, aborting function call stack: [ (0601ED0E)].doorchain.Chained.OnActivate() - "g:\_F4\Art\Raw\Scripts\DoorChain.psc" Line 52 [09/03/2019 - 05:31:07PM] error: Cannot call abBusy() on a None object, aborting function call stack: [ (0601ED0E)].doorchain.Chained.OnActivate() - "g:\_F4\Art\Raw\Scripts\DoorChain.psc" Line 59 |
Related Issues: 20623
This is essentially the same report as 20623.
Back then, Arthmoor decided to leave the script alone because sanity checks could mask other problems (i.e. we would no longer be able to detect setup errors).
As it turned out however, there are no such problems. The only instances that throw this sort of errors are chains that are deliberately not linked to any door, so there's no point in leaving that script alone.
Added sanity checks.
Back then, Arthmoor decided to leave the script alone because sanity checks could mask other problems (i.e. we would no longer be able to detect setup errors).
As it turned out however, there are no such problems. The only instances that throw this sort of errors are chains that are deliberately not linked to any door, so there's no point in leaving that script alone.
Added sanity checks.
Showing Comments 1 - 1 of 1