diff options
| author | orwell96 <orwell@bleipb.de> | 2018-10-17 21:02:43 +0200 |
|---|---|---|
| committer | orwell96 <orwell@bleipb.de> | 2018-10-17 21:05:06 +0200 |
| commit | fe4b4a695af2df5a9c0c43efb9255bbdbf783a12 (patch) | |
| tree | 818657ffc2ef1fc0190c36cf13fc8132d07c5d2b /advtrains_interlocking/models | |
| parent | 267ce6fe6da5c8a59c6ccdbb86b0c66d4398e098 (diff) | |
| download | advtrains-fe4b4a695af2df5a9c0c43efb9255bbdbf783a12.tar.gz advtrains-fe4b4a695af2df5a9c0c43efb9255bbdbf783a12.tar.bz2 advtrains-fe4b4a695af2df5a9c0c43efb9255bbdbf783a12.zip | |
Fix node database ATC rail bug
After successfully registering newly-placed ATC rails in the nodedb, the rail's after_place_node() callback
(local apn_func()) immediately cleared it again by passing a "node" object that was actually a player object
and thus had no "name" or "param2" to ndb.update(), which it handled how it should not in this situation.
Since those ndb.update calls were unnecessary anyways, I removed them completely.
Diffstat (limited to 'advtrains_interlocking/models')
0 files changed, 0 insertions, 0 deletions