View Issue Details
| ID | Project | Category | Date Submitted | Last Update | |
|---|---|---|---|---|---|
| 0025360 | AI War 2 | Gameplay Issue | Jun 30, 2021 5:38 pm | Jul 5, 2021 1:18 am | |
| Reporter | Evil Bistro | Assigned To | BadgerBadger | ||
| Severity | minor | ||||
| Status | resolved | Resolution | fixed | ||
| Product Version | 3.306 Tweaks | ||||
| Fixed in Version | 3.309 Hangar Staff | ||||
| Summary | 0025360: Relic train tooltip problems | ||||
| Description | Unsure if this is a case of a bug or an outdated tooltip, but I couldn't get a straight answer on this from discord. The relic train notification currently has an element that says where the train is going next, except that the vast, vast majority of the time (I want to say 100% of the time, but to be honest I haven't paid close enough attention to claim that), the planet the tooltip is pointing to is straight up wrong. The net result of this is that the game gives 0 transparency as to when the train is leaving its current location or where it's going next, given it doesn't use wormholes and is perfectly capable of traveling halfway across the galaxy between "visits." If that's the intended functionality, fine, but the train notification at present does not imply that to be the case. Currently this makes trains a badly losing gamble in most situations for high intensity spire for any amount of cleverness, as unless you're simply dropping the relic where the train stopped or an immediately adjacent planet, the elevated exo response is EXTREMELY easily game ending without a large beachhead set up well in advance, even when you can afford to have all hands on deck with all the Spire fleets you have at your disposal balled up in one place. I don't have a save to conveniently demonstrate this at present, but I'm sure I can scrounge one up if it'd help. | ||||
| Tags | No tags attached. | ||||
|
|
Do you have a save game illustrating this problem? |
|
|
So, I was attempting to reproduce this in another spire game and got a slight variation instead. In this save, the active relic train's notification is *missing* the "traveling to" part of the notification that it normally has, and if you do a watch hack on Gamont where the train is parked at the moment you load the save, you can also fast forward a few minutes of game time and watch the planets left to visit counter drop from 5 to 3 without the train ever leaving Gamont. I did the watch hack to confirm for myself that this was what the train was actually doing and not just a tooltip issue. Definitely something hinky going on there, and I've seen this occur at least one other occasion several patches ago when I was just starting to learn Spire. I'll keep playing and see if I can get a save where the traveling to part of the notification is there and just wrong again. |
|
|
This was working "Technically" correctly, but leading to some subpar outcomes. |
|
|
For Spire Relic Trains, I have rewritten the hovertext for this notification for improved clarity, and also improved the "pick next planet to for relic train" logic to help it find some better planets |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| Jun 30, 2021 5:38 pm | Evil Bistro | New Issue | |
| Jul 1, 2021 1:36 am | BadgerBadger | Note Added: 0062326 | |
| Jul 4, 2021 5:43 pm | Evil Bistro | Note Added: 0062334 | |
| Jul 4, 2021 5:43 pm | Evil Bistro | File Added: relic train gamont.save | |
| Jul 5, 2021 1:17 am | BadgerBadger | Note Added: 0062336 | |
| Jul 5, 2021 1:18 am | BadgerBadger | Assigned To | => BadgerBadger |
| Jul 5, 2021 1:18 am | BadgerBadger | Status | new => resolved |
| Jul 5, 2021 1:18 am | BadgerBadger | Resolution | open => fixed |
| Jul 5, 2021 1:18 am | BadgerBadger | Fixed in Version | => 3.309 Hangar Staff |
| Jul 5, 2021 1:18 am | BadgerBadger | Note Added: 0062337 |
