View Issue Details
| ID | Project | Category | Date Submitted | Last Update | |
|---|---|---|---|---|---|
| 0003829 | AI War 1 / Classic | Suggestion - Interface Ideas - Unit Selection, Management, and Orders | Sep 8, 2011 9:07 pm | Sep 10, 2011 7:52 pm | |
| Reporter | mindloss | Assigned To | |||
| Status | new | Resolution | open | ||
| Summary | 0003829: Rethink rally posts | ||||
| Description | I'm just going to point out a problem, and someone smarter than me can suggest a solution. The rally posts as currently implemented could use some love and/or redesign. The little thing: I'm not sure why there are two options instead of just the one superior combination of both: drop a rally point, optionally have it redirect if clicked elsewhere, serve as rally post if clicked on itself (like normal dock behavior). However, this is hardly hurting anything and I'm sure some folks prefer the rally post to the redirector, so nevermind. :) The bigger thing: They allow for some very cool behavior and time-saving if used correctly, but as I'm sure anyone who's done redirect chains has experienced, also headaches. If I have them set to be conveying my fleet production right out to the front lines, and then all of a sudden I need to make a hasty retreat from a pitched battle into the previous system, sending my ships through the wormhole and having them immediately reappear is not my idea of fun. If there's a way to override this without going back to the redirect post in question and resetting it to point somewhere else, I apologize and please fill me in. Actually, one idea now springs to mind. As far as I can tell, the main advantage to allowing that behavior--having a ship 'bounce' off a wormhole--is to allow actual production systems to include themselves in the chain. If you set up an initial bounce off a previous wormhole, you set yourself up for minimum adjustment later down the road and can split fleets etc. on the fly. Well, that, and it was no doubt easier to code since it's the logical behavior. Instead, detect if a ship would bounce and if so, let it through to park in its destination system. To compensate for that and still allow you to do all the neat redirect tricks you want, allow redirection from docks etc. directly to a redirection post, which the game would interpret as "treat all ships being spawned from this building as just having entered the system under normal redirect post rules". Yeah. Low priority stuff, but it can't hurt to get it in the system. | ||||
| Tags | No tags attached. | ||||
| Internal Weight | |||||
|
|
As for the first thing... That's already how it works. A redirector acts like a normal rally post if they don't redirect anywhere. The reason for there being two is that one is mobile and non-redirectional, the other is non-mobile but can redirect rallies to elsewhere. As for the second... I'm not sure if it solves anything for you, but you can create a chain of movement commands from a single redirector; just shift-rightclick to create multiple waypoints. This also works for loops. |
