View Issue Details
| ID | Project | Category | Date Submitted | Last Update | |
|---|---|---|---|---|---|
| 0002059 | AI War 1 / Classic | Suggestion - Interface Ideas - Galaxy Map Management | Dec 16, 2010 2:05 am | Jan 17, 2011 12:20 am | |
| Reporter | MaxAstro | Assigned To | Chris_McElligottPark | ||
| Status | resolved | Resolution | fixed | ||
| Product Version | 4.051 | ||||
| Fixed in Version | 4.068 | ||||
| Summary | 0002059: Option to disable "Swallow" ships | ||||
| Description | Among the many and varied types of ships in the game, Spire Maws win the award of being the first I would actually like to disable. They are annoying to kill, there is often no way to tell that you have lost ships to them except that your capfleets are suddenly smaller than they used to be, ships freed from them don't remember any previous orders and have to either be microed or just sit there to die, and they seem to take ~forever~ to finish eating things; especially annoying with Mark I scouts, as losing a couple to a maw and being down to a capfleet of only 5-6 scouts seriously reduces early scouting potential. Also I could swear they are permanently eating certain ships. I lost a Mark III engineer to one early in the game, and my capfleet has been down one engineer up to about an hour into the game. Plus, the button at the bottom of the screen that tells me where my engineers are normally shows ships in maws listed as "in transport", but in this case the game seems to just be pretending that 13 Mark III engineers is all I'm allowed to have (it's a 2-player game so 14 is my normal cap). In any case, the Swallow mechanic is a neat idea, but I would personally support it being put up with cloaking and mines in the list of "turn them off if you don't like them" mechanics. | ||||
| Tags | No tags attached. | ||||
| Internal Weight | |||||
|
|
I'd probably still play with them on but being able to turn them off if you wanted to would be nice and seems in keeping with the other things we can turn off in that menu. |
|
|
I'm happy to make them disable-able, for the same reason as some of those other ships. However, something for a bit later, because there are indeed some bugs with them permanently eating some ships at the moment, and I'd really like to make sure that people have experiences with them fully working properly before turning them off. I still have some usability things on my list that I'd like to get them through before doing this, too -- global notices of when your team has ships inside swallowed ships, and what their combined health is for the moment, etc. That way some of the mystery of these ships (do I have eaten ships? When will I get them back?) is removed. |
|
|
Actually, this was done last release. :) |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| Dec 16, 2010 2:05 am | MaxAstro | New Issue | |
| Dec 16, 2010 11:41 am | wyvern83 | Note Added: 0006304 | |
| Dec 16, 2010 12:53 pm | Chris_McElligottPark | Note Added: 0006316 | |
| Dec 16, 2010 12:53 pm | Chris_McElligottPark | Assigned To | => Chris_McElligottPark |
| Dec 16, 2010 12:53 pm | Chris_McElligottPark | Status | new => feature for later |
| Dec 20, 2010 9:08 pm | Chris_McElligottPark | Status | feature for later => minor fix for later |
| Dec 20, 2010 9:10 pm | Chris_McElligottPark | Status | minor fix for later => feature for later |
| Jan 17, 2011 12:20 am | Chris_McElligottPark | Note Added: 0008811 | |
| Jan 17, 2011 12:20 am | Chris_McElligottPark | Status | feature for later => resolved |
| Jan 17, 2011 12:20 am | Chris_McElligottPark | Fixed in Version | => 4.068 |
| Jan 17, 2011 12:20 am | Chris_McElligottPark | Resolution | open => fixed |
