You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's my old roadmap about change of item handling in Singularity.
My branch is here: https://github.com/Xenega/singularity/tree/items
No pull request for now, I want to rethink the idea and it's not my priority.
General
TODO - Include item pane in a scroll widget/list widget.
=> Allow more 4 item type.
=> Allow more than 1 item per type.
TODO - List pane for cpu item + intern modification for list of cpu.
=> cpu can have differents items, ie one per class.
=> example: 5 cluster + 20 server.
DONE - Use a slider in item build dialog.
=> Avoid the input dialog after choose the item to build.
DONE - Use differents sizes for cpu.
=> A cluster don't use the same place than a PC.
TODO - Data file for item type.
=> Item type define in a data file.
=> You can define additional item type.
TODO - Custom data type for base class.
=> You can define the item type available for a base.
=> Need a usercase
Power supply (partially independant of general)
TODO - Implement power need of cpu.
=> Each computer need power.
=> The power is taken from the power grid.
TODO - Implement power supply of reactor.
=> Each reactor provide power.
TODO - Use power grid increase discovery.
=> Formula to find.
(after different size for cpu)
TODO - Use differents sizes for reactor.
=> You can have more one reactor.
=> Reactor cost place with cpu.
TODO - Only urban location can use power grid
Build&Transfer (after general, provisional)
TODO - Implement a way to transfer item
TODO - Implement a way to stock item
TODO - Implement a way to build item
Others (can be implemented anytime):
DONE - Dehardcode list of locations (pop).
DONE - Implement a physics size instead of slot.
=> Example: 0.2m for a slot.
The text was updated successfully, but these errors were encountered:
Also from me, great ideas (I played and finished it several times, still under easiest level).
I know that the save games contain a lot item data that may need to be separated from save-game. So I now wonder if your changes are compatible (and affect) with old save games? I can make mine accessible for you if you need them. But then I need to send you a link by email.
It's my old roadmap about change of item handling in Singularity.
My branch is here: https://github.com/Xenega/singularity/tree/items
No pull request for now, I want to rethink the idea and it's not my priority.
General
TODO - Include item pane in a scroll widget/list widget.
=> Allow more 4 item type.
=> Allow more than 1 item per type.
TODO - List pane for cpu item + intern modification for list of cpu.
=> cpu can have differents items, ie one per class.
=> example: 5 cluster + 20 server.
DONE - Use a slider in item build dialog.
=> Avoid the input dialog after choose the item to build.
DONE - Use differents sizes for cpu.
=> A cluster don't use the same place than a PC.
TODO - Data file for item type.
=> Item type define in a data file.
=> You can define additional item type.
TODO - Custom data type for base class.
=> You can define the item type available for a base.
=> Need a usercase
Power supply (partially independant of general)
TODO - Implement power need of cpu.
=> Each computer need power.
=> The power is taken from the power grid.
TODO - Implement power supply of reactor.
=> Each reactor provide power.
TODO - Use power grid increase discovery.
=> Formula to find.
(after different size for cpu)
TODO - Use differents sizes for reactor.
=> You can have more one reactor.
=> Reactor cost place with cpu.
TODO - Only urban location can use power grid
Build&Transfer (after general, provisional)
TODO - Implement a way to transfer item
TODO - Implement a way to stock item
TODO - Implement a way to build item
Others (can be implemented anytime):
DONE - Dehardcode list of locations (pop).
DONE - Implement a physics size instead of slot.
=> Example: 0.2m for a slot.
The text was updated successfully, but these errors were encountered: