ID:2605528
Aug 19 2020, 7:37 am (Edited on Aug 19 2020, 7:45 am)
|
|||||||
Not Feasible
| |||||||
This causes lag in large projects if ..() is being called in Login(). I can't think of a single instance where this default behavior of searching for an available tile close to 1,1,1 instead of just locating the mob at 1,1,1 (regardless of what's on 1,1,1) is useful.
|
Aug 19 2020, 12:45 pm
|
|
Lummox JR resolved issue (Not Feasible)
|
The easiest way to avoid this is to not call ..() in Login(). Or alternatively, you could override Move() and change the behavior when the new location is an area.
Removing the default behavior would break so, so many old projects. |
Not to mention breaking one of the earliest core features of the language, the original purpose was for MUDs to pick a starting room for the player.
|