Page 1 of 2

r7399 | bot not creating instance for maps.txt

Posted: 30 Jun 2010, 10:08
by xiaoTing

Code: Select all

Exp Gained: 81/44 (0.00%/0.00%)
[Guild] Experience Gained Base:81 (0.00%) Job:44 (0.00%)
mapchanged : 0011@tower.gat (41, 354)
Exist NPC : Unknown #110016043 (50, 360) (ID 110016043) - (0)
Allowed other player invite to Party
Other players are not allowed to view your Equipment.
where
location (0011@tower) : 41, 354 << the map did not show me The Infinity Tower

so i cant type move somewhere else command

Re: [BUG] bot not creating instance for maps.txt[2.1][r7399]

Posted: 01 Jul 2010, 07:47
by h4rry84
true, it's still didn't support for instanced map.

Re: [BUG] bot not creating instance for maps.txt[2.1][r7399]

Posted: 01 Jul 2010, 07:50
by Technology
But it loads the right .fld right?

Re: [BUG] bot not creating instance for maps.txt[2.1][r7399]

Posted: 01 Jul 2010, 08:00
by EternalHarvest
What about NPCs and portals in instanced maps? How they're processed?

Re: [BUG] bot not creating instance for maps.txt[2.1][r7399]

Posted: 02 Jul 2010, 09:17
by xiaoTing
npc and portals, i think should be no problem only if the bot follow his/her master,
and the bot will auto atk the monster and calculating the route if it saw monster,
but if the bot follow lost and stuck in a place, if we cannot apply move x, y
then the bot will not able to proceed next map forever.

Re: [BUG] bot not creating instance for maps.txt[2.1][r7399]

Posted: 02 Jul 2010, 10:05
by EternalHarvest
I mean there is NPCs/portals database, which probably should treat instanced maps as a single map, independently of instances.

Re: [BUG] bot not creating instance for maps.txt[2.1][r7399]

Posted: 02 Jul 2010, 11:21
by xiaoTing

Code: Select all

Existing NPC : Tombstone (262, 353) (ID 110005411) - (0)
Existing NPC : Lady#Rosa Airynite (260, 354) (ID 110005410) - (1)
Allowed other player invite to Party
Not allowed other player view Equipment
You are now sitting.
Map Changed: 0011@tower.gat (12, 387)
Exist Portals : Unknown #110014697 (12, 393) - (0)
Allowed other player invite to Party
Not allowed other player view Equipment
where
Location  (0011@tower) : 12, 387
when i type move 12 393, it still same unable to move to next map

Re: r7399 | bot not creating instance for maps.txt

Posted: 09 Aug 2010, 23:05
by Technology

Code: Select all

Location  (0011@tower) : 12, 387
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.

Re: r7399 | bot not creating instance for maps.txt

Posted: 09 Sep 2010, 01:43
by Technology
changes had been made in svn, please test and report wether it functions properly or not...

Re: r7399 | bot not creating instance for maps.txt

Posted: 22 Oct 2010, 12:32
by kLabMouse
Updated work with 'Field'
Should work fine.

Please Report if it's broken.

P.S. Moved to Fixed Bug Reports.