PyWeek - Galacticus Basic design


Galacticus Basic design:


What to get working first:

Stars provide the steam clouds around
them for Stellarconstructions to collect

Hyperships can attack other hyperships and stellarconstructions (eats up lots of steam for defender)
Can move in straight line … through or above every thing (eats up steam)
Can build Stellarconstructions (eats up steam)
Can carry steam (which is the both fuel and health bar)

Stellarconstructions collect steam and build hyperships using steam.

Player has name and password. He can login and give move, build and attack orders to his Hyperships and Stellarconstructions. When he logs out all the hyperships and stellarconstructions remain on the server.

Server logs players in and keeps track of their property. Also it produces time step; only it can move and change the game state. It can receive orders and messeges form players.

Client program that Player uses to view the server state in 3D. It also sends and gets messages from server.

Player Creation. Give player Stellarconstructions and some Hyperships. Create then next to another player so that immediate contact and possible conflict happens. (Rather then players feeling board on different corners of the galaxy)

Messages a frame work for a global in-game-chat. User GUI and server side broadcast all.

Done second:
Run extensive test, including at least 3 hours in game and make pyunit tests where possible. Provide packaging and readme


Done third:
Make that other computer a dedicated server for galacticus – keep it running.
Add more Hyperships and Stellarconstructions types (and speselizations)
Hyperships:
Builder
Fast scout
Regular
Week Long rage
Slow Good long range
Support Carrier (carry steam)
Fast Regular
Stellarconstructions
Steam Collector
Factory for each type of Hyperships
Carrier Dock
Steam Node (connection to other steam nodes)
Add stop order and groping(Ctrl-#)
Add queues for orders

— Treeform on 2006/03/27 07:34 of Galacticus