I would love to see a new type of door implemented, that instead of open or closed steps through its states one at a time.
One state advanced per button press, maybe even two button types(next state, and previous state).
No automation at all. No auto open or auto close, no action permitted by AI.

This could be used for screen covers, multi state shutters, movable equipment, reactor inspection covers, airlocks that require one door to always be closed, etc...

I'm wondering if this is even possible, and if so it would be an amazing feature to have.  Could be lumped in with the existing door object in the designer.

I suggest this because even non-automatic doors still close themselves after a time and that prevents their use for many of these things.

Currently if you capture any city of an advanced empire, you get access to ALL their patents.

I suggest that most (not all) patents get deleted from the city before the ownership transfer happens. Akin to the people shredding all the confidential patent research before trying to escape or surrender. A few random patents can be left behind as you always miss something when you are in a rush.



This would limit that major reward from capturing one city from an advanced empire. Force them to actually capture more than one city if they are attempting to gain patents.

I will point out that yes, patents aren't that valuable right now, since if you can use a patent you can also make it. But this could apply to other things too maybe, such as dumping fuel and weapons upon capture.

Currently is it impossible to upgrade your Capitol building or your Military Headquarters to a new blueprint without removing the whole city/base. Same with moving the building once it is managing a city/base.

I was thinking that maybe it would be useful if we could hold down CTRL when placing a new building and it would place the new building and transfer all settings to it and remove the old building.
For example placing a new Military Headquarters would instantly bulldoze the old one, allowing you to both move it and upgrade it to a new blueprint.

Currently a LOT of players accidentally make their first starship with a Wormhole P FTL Drive, and are then confused about why they can't return to their home system after going through a one way wormhole connection.

I suggest making the Wormhole PN FTL Drive the default/first, and then change Wormhole P FTL Drive into something else.
For example you could rename it to Wormhole P+ FTL Drive and make it cheaper to make and operate than the normal Wormhole PN FTL Drive. Or something like that.
Or simply remove the Wormhole P FTL Drive altogether.

Original post: http://hazeron.com/mybb/showthread.php?t...248#pid248

I would love to see electricity behave differently from normal commodities.
Have power plants produce a static amount of power based on job amount per tick. Then have static power consumption be subtracted and use the remaining output to recharge batteries in power plants and military installations. If not enough static power is produced, drain some from power plant batteries.

Vehicles not Tallied
Vehicles in my town do not affect the construction or manufacturing processes there.

Finished the code that was intended to do this.

• All vehicles in town are shared by all buildings. For example, one farm machinery would be enough to satisfy every farm in town.
  
• Vehicles are tallied if they are at any building site or in any building of the same town as the building that is looking for one. Vehicles must belong to the same empire to be counted.
  
• When a vehicle is added or removed from the town, it can take a few minutes for all buildings to notice.
  

• Pilot turn code had an error when calculating turns in negative angle directions. A sign was wrong on a value in the calculation.
  
• Pilot initiation of turn on a spacecraft at rest needed to signal the need for immediate processing by the physics thread.
  
• Initial rotation call on a spacecraft at rest calculated a huge turn due to an elapsed time error.
  

Building Quality of Operation
The quality of operation of buildings is confusing. It imposes a year long delay on new empires before they can compete fairly with other empires.

Building quality of operation removed.

• With the removal of building quality of operation, tech items no longer serve any purpose.
  
• Mass media building no longer produces tech items. Mass media building does nothing at all any more. It might be repurposed as a morale building.
  
• Repair shop quality is no longer a factor when repairing or recovering spacecraft.
  
• Detection range of buildings now appears on the building design analysis.
  

• Deep space detection range is reported on the design analysis.
  
• As with cities and buildings, emissions from the solar system containing the ship are not detected.
  
• Systems only emit their signal once per six hours. A spacecraft would have to loiter that long in a system, to detect every possible signal.
  
• The ship itself does not indicate when it detects a signal. It just responds appropriately so the star map gets updated.
  

The empire standing's page is occasionally left down after a server restart. If it's possible, automating the startup for the standing's page as part of the server restart process would be useful.

A player recently quit the game, saying they felt the game mechanics forced you into a subscription for a year. I assume they were referring to the quality progression of buildings and the size limits on spacecraft related to that quality.

The quality progression of buildings was not intended to create a subscription requirement. It was intended to make the technology associated with that quality more valuable, not so readily available.

How important is that quality/time progression? Does it add to the game or take away?

If I buy a game of Monopoly, I can compete equally with seasoned players, right away. There is no time delay before I can mortgage properties. Should we adopt that sort of philosophy?

Store Emission and Detection Info
The emission and detection information resulting from power usage in solar systems is not saved between server restarts. It takes a long time to accumulate.

Emission and detection information is now saved and restored between server restarts.

This also flushed out a minor bug that caused solar systems to be updated to the client at times when no update was needed.

Kick Dying Body
Sometimes when a creature falls to the ground dying, I want to roll them over to see them better.

Attacks on a dying body now cause it to change dying position, even if the attack does not cause any damage.

Body Cleanup
Poison and disease are not always removed when I die, particularly in primeval world.

Fixed dead body cleanup code. 

Village Reputation Reset
My reputation with the village gets reset when I die but the villagers continue attacking me.

Stopped indigenous from attacking when the target's reputation is reset.

Client Crash
My client crashed while I was dying in primeval world and villagers were kicking my dying body.

Fixed thread conflict when rendering on screen messages.

Repair Exchanges
The blueprint exchanges contain designs that are no longer valid or that do not match the design analysis shown in the exchange. It is confusing.

Developed functions to clean up the blueprint exchanges.

• Each design is loaded and analyzed.
  
• If it is no longer valid for manufacture or construction, the exchange entry is removed.
  
• If the design analysis report changes, the exchange record is updated with the new report.