Issue271

Title Make waypoints be global, to let bots return to their home
Priority feature Status open
Assigned To Keywords
Linked issues Watchers

Submitted on 2011-07-24 19h07 by tracker_migration, last changed by ahuillet.

Messages
Author: tracker_migration Date: 2010-02-12   14h23
Submitted by matthiaskrgr
How to reproduce:
Go to Temple Wood and pull some bots from there into entrance of Cryo Stasis Lab.
Move into the actual laboratory (get out of bot sight).
Stay there some time.
Go back, the bots are still in Cryo Stasis Lab and did not return to Temple Wood.

When you return in invisible mode (Ctrl+Alt+Shift+c, than press i, than q to resume to game) you'll see that all the bots from Temple Wood are in "purewait" mode. (Set Options ->Droid Talk -> All in gams speech ON)

rev. 2412

Thank you for your fine work!
Matthias Kr\u00fcger
Author: tracker_migration Date: 2010-02-12   14h42
Posted by stedevil
The underlying issue for this is closely related to
https://sourceforge.net/tracker/?func=detail&aid=2688621&group_id=54521&atid=474019
Author: tracker_migration Date: 2010-02-13   09h32
Posted by ahuillet
I don't think it is related.

This issue simply has to do with the bot trying to go to waypoint number X - but on the wrong level.
Our waypoints are designated per-level and can't be adressed from another, and this is the cause of the problem.
Author: tracker_migration Date: 2010-02-13   10h18
Posted by stedevil
How is it not related? The other trackitem is also about needing a way to specify target waypoint on target map.
Author: tracker_migration Date: 2010-03-02   17h26
Posted by ahuillet
It is not related because the problem here is simply that our waypoints are per-level.
Make them global and the issue goes away. We don't need to specify a target waypoint : the bot already has one - but it doesn't know the target waypoint isn't on its current level, that's all.
Author: tracker_migration Date: 2010-03-02   20h02
Posted by stedevil
> the problem here is simply that our waypoints are per-level. Make them global and the issue goes away

Exactly the same, global WP definitions, would solve the other tracker item, no? So how is it not related?!?
Author: tracker_migration Date: 2010-04-17   02h06
Posted by stedevil
Lets make global WPs a target for 0.14
Author: tracker_migration Date: 2010-08-11   15h21
Posted by fluzz
Transfered to Feature Requests tracker, and changed the summary.
Author: tracker_migration Date: 2011-03-21   08h43
Posted by ahuillet
Global WPs not for 0.15.
History
Date User Action Args
2011-07-28 06:22:32ahuilletsetpriority: bug -> feature
2011-07-24 19:07:50tracker_migrationcreate