1
2
Dec 27 2012, 11:50 pm
|
|
Hmm.. The only case I can think of where setting loc will fail is when you try loc=locate(x,y,z) before run-time generation of the map. In this case, locate will return null.
|
In response to Jemai1
|
|
Jemai1 wrote:
Hmm.. The only case I can think of where setting loc will fail is when you try loc=locate(x,y,z) before run-time generation of the map. Maybe it was setting the loc of two things to the same loc in the same tick? I can't remember. |
I believe you're talking about Move instead. Setting loc doesn't do any checking or whatsoever. It simply sets the location.
|
In response to Jemai1
|
|
Jemai1 wrote:
I believe you're talking about Move instead. Setting loc doesn't do any checking or whatsoever. It simply sets the location. I'll dig up the source where it occured. Perhaps it was a bug. |
Hmm, turns out it was if Cross() returns 0 before a delayed loc = blah is set to happen.
area/transfer This would happen when the destination location had a box on it which overrode Cross() and returned 0 |
Are you certain that location is a turf? loc = locate(location.x,location.y,location.z) shouldn't pose any problem.
|
1
2