I see 2 spaces between Location and (0011@tower), thats not right!
Between those 2 spaces there should be the
descName (The Infinity Tower)
We find this descName by its
baseName (1@tower).
In the previous revisions however, kore searched by the actual full field
name (0011@tower) instead of the baseName...
So this should now be fixed in latest revision.
However, i predict that this does not only affect naming, but also portals.txt and npcs.txt...
This however is kinda tricky since, maps that are:
- - aliases don't necessarily have their npc's|portals at the same locations, since they are independant maps that only reuse the same .fld (ex. new_1-2, new_2-1, ...) = (aliases for: new_zone01)
- instances probably do have their npc's at the same locations, as they are clones of their instanced map. (ex. 0001@cata, 0011@cata, ...) = (instances of: 1@cata)
(btw, in theory, its possible that we have to deal with an aliased map that is instanced on top of that...)
So, what i'd do to solve this is: portals.txt and npcs.txt entries need the name, stripped from a possible instanceID.
hmm i have looked into cmdMove and i see yet another problem.
I believe we will have to start making more use of objects of the Field class than of regular mapnames on some places.
So please keep on testing latest svn and keep supplying information.