Things we'd like to see in the next patch

[geoschmo]

Originally posted by Suicide Junkie:
geoschmo: Bigger internals, smaller armors get hit first.

Right, and that's what I meant to say. I remeber you saying the smaller armor goes first. But what I saw in my tests was an almost randomly even distribution of armor damage between armor I's and Armor III's. No advantage to either. Or when you say smaller for armor do you actually mean tonnage? Are armor components destroyed by size while internals are destroyed by structure?

Geoschmo

[Dragon of the void]

Very interesting tests, and thanks to you for taking the time AND telling us the result, so we can understand SE4 dynamics better.

Just one question:
When you do your tests, what kind of weapoon are you using ???

If, for example, you use a weapon that can not destroy the big component in one hit (or the left over damage from a hit after destoying a component is not enough to destroy another big component), you get the following result:

Comp. A (big) is hit, but not destroyed. Points are stored. Next hit, another random component is selected. Stored points are added.

Comp. B (small) is hit, and destroyed.

This has nothing to do with what component is selected randomly more often than the other, but with the viewable result you get (destroyed component). Or do you have a way to tell what component was hit, but not destroyed ???

[overminder]

Here is a thought. What about making population used in ship/base building. say 0.1 for the smallest size then incressing as the ship size did. It would make older, more heavly pop worlds all the more importen. maybe even for troops. A single troop could be a 0.001 pop. It would make smaller ships a lower drain on worlds to build but give organics a new plus.

[tesco samoa]

Fix the ship movement and ship combat initative. From being one empire goes first then the other.

And as always... Fix that one on one relationship with names...

[tesco samoa]

How about this one.

When you are in the colonize window... ANd you have scrolled down near the bottom of the list... Select the colonize button...

The list stays where it is and does not reset to the top of the list

[ckotchey]

Here's one...
When I start my turn, for example, let's say I've built 5 colonizers, so I have 5 identical Messages in my turn log. I go to the 2nd one, and click "goto", which takes me to the ship, so I do my things with that ship. I bring the log back up, but the list is "reset" with the "cursor" on the first entry in the log...so I can't remember now...did I just handle the message for the 2nd colonizer? the third? I think when it comes up, the "current" item should be remembered from the Last time I had it open.

[Slick]

Originally posted by ckotchey:
Here's one...
When I start my turn, for example, let's say I've built 5 colonizers, so I have 5 identical Messages in my turn log. I go to the 2nd one, and click "goto", which takes me to the ship, so I do my things with that ship. I bring the log back up, but the list is "reset" with the "cursor" on the first entry in the log...so I can't remember now...did I just handle the message for the 2nd colonizer? the third? I think when it comes up, the "current" item should be remembered from the Last time I had it open.

Yes, I sumbitted something similar to MM requesting "goto next[previous] log entry" HOTKEYS which would send you to the next[previous] location and show you the appropriate log entry. That way you could quickly go through the log and take actions on any entry as required.

Slick