-
Notifications
You must be signed in to change notification settings - Fork 29
lacuna reboot
Iain C Docherty edited this page Mar 27, 2016
·
16 revisions
There is a risk of second system syndrome where we add more features and fail to deliver so treat this as a wish-list of possible ideas. Some of the ideas are only going to be possible with a reboot (e.g. rebalance Essentia, plans etc.) and would be difficult to implement later so these should have priority. Other ideas may be possible to be implemented later.
- Zone Reorganisation
- Admin Thoughts
- Essentia Sink
- Server Code Revamp
- Fleet Action
- Official Client
- Phase over to new server
- Resource Balancing on Reboot
- Star and Resource Distribution
- Player Contributions
- Slack Integration
- Ensure that empire names in Lacuna-1 cannot be chosen in Lacuna-2 except by their existing owners.
- Images that may be useful in end-of-days (https://www.dropbox.com/sh/a08uw6pqqpszkh6/AACweBTQ5ztl2OgivN8SzPbha?dl=0)
- It should be able to flip a captitol, AI or Player. like when a fissure explodes on the captitol, the player 'escapes' to a new planet to start again.
- Introduce the concept that a planet has limited resources. Once mined out production drops significantly. Colony need then to relocate or to supply chain from elsewhere. This is modeled here https://www.boundless.com/biology/textbooks/boundless-biology-textbook/population-and-community-ecology-45/environmental-limits-to-population-growth-251/logistic-population-growth-930-12186/
- Lottery payout should vary.
- If more people purchase Essentia then the lottery payout should increase proportionatly
- The more people playing the lottery in a zone, the higher the payout in that zone
- Incentives for existing players to move to new server
- Medals for 'long service'
- Increased base affinity points over the standard 45 based on length of service.
There are some changes we can make on efficiency to make the code more responsive.
- Only send status/empire/body blocks on request, or if there is a change
- Instead of sending all data, just send changes for the above.
- Farm off changes to body (updates) out of web request into a scheduled job.