View Issue Details
| ID | Project | Category | Date Submitted | Last Update | |
|---|---|---|---|---|---|
| 0012227 | Bionic Dues | Bug - Gameplay | Sep 10, 2013 10:36 am | Sep 24, 2013 4:07 am | |
| Reporter | nas1m | Assigned To | keith.lamothe | ||
| Status | resolved | Resolution | fixed | ||
| Product Version | 0.903 | ||||
| Fixed in Version | 0.920 | ||||
| Summary | 0012227: Selection of first bot in a new mission seems random / is unclear | ||||
| Description | I have no idea what factor decides which bot goes first in the next mission. At least some kind of clarification/tooltip is missing here imho. | ||||
| Tags | No tags attached. | ||||
| Internal Weight | For New Player Experience | ||||
|
|
Your bots have a specific order defined at the start of the game, and should always start in that order. Is that not what you are seeing? |
|
|
Nope. Sometimes another exo goes first. Somebody indicated that this might be connected to which Bot was customized last - i could not yet give this a shot, though. EDIT: it may be that the exo last active in the previous Mission is selected now that i think of it... |
|
|
Okay, thanks for the info -- that is strange indeed. |
|
|
Please see my edit above |
|
|
I also see this, and I believe that nas1m is correct that the starting bot is the last bot active in the previous mission. |
|
|
Yes, looks like it is exactly as Aeson says. |
|
|
That is what I have noticed as well. I've gotten used to switching back to my 'default' bot and weapons at the end of a mission. |
|
|
Yep, it's the last bot that you had selected. Though after a Bahamut mission this can lead to problems, as well as this being confusing in general. Keith: can you make it so that the first bot currently in your roster is always selected when you first start a new mission? |
|
|
For 0.920: * Fixed a bug where you would usually start each mission in the last exo you used in the previous mission, rather than the first exo in your roster. Thanks :) |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| Sep 10, 2013 10:36 am | nas1m | New Issue | |
| Sep 10, 2013 12:56 pm | Chris_McElligottPark | Note Added: 0033406 | |
| Sep 10, 2013 12:59 pm | nas1m | Note Added: 0033409 | |
| Sep 10, 2013 1:01 pm | Chris_McElligottPark | Note Added: 0033411 | |
| Sep 10, 2013 1:01 pm | nas1m | Note Edited: 0033409 | |
| Sep 10, 2013 1:02 pm | nas1m | Note Added: 0033412 | |
| Sep 10, 2013 4:10 pm | Aeson | Note Added: 0033420 | |
| Sep 12, 2013 7:34 am | tigersfan | Internal Weight | => For New Player Experience |
| Sep 12, 2013 7:34 am | tigersfan | Assigned To | => Chris_McElligottPark |
| Sep 12, 2013 7:34 am | tigersfan | Status | new => assigned |
| Sep 13, 2013 9:14 am | Histidine | Relationship added | related to 0012387 |
| Sep 13, 2013 2:26 pm | tigersfan | Relationship replaced | has duplicate 0012387 |
| Sep 14, 2013 9:17 am | nas1m | Note Added: 0033698 | |
| Sep 15, 2013 1:27 am | Winge | Note Added: 0033719 | |
| Sep 23, 2013 11:42 am | Chris_McElligottPark | Assigned To | Chris_McElligottPark => keith.lamothe |
| Sep 23, 2013 11:43 am | Chris_McElligottPark | Note Added: 0033984 | |
| Sep 23, 2013 12:58 pm | tigersfan | Relationship added | has duplicate 0012615 |
| Sep 24, 2013 4:07 am | keith.lamothe | Note Added: 0034005 | |
| Sep 24, 2013 4:07 am | keith.lamothe | Status | assigned => resolved |
| Sep 24, 2013 4:07 am | keith.lamothe | Fixed in Version | => 0.920 |
| Sep 24, 2013 4:07 am | keith.lamothe | Resolution | open => fixed |
