[Big] Feature/engine 2#4
Conversation
| id: BusId | ||
| x: float | ||
| y: float | ||
| asset_type: AssetType |
There was a problem hiding this comment.
why would you assign buses to a certain asset type? Multiple assets should be allowed into the same bus.
Also, I would not include ice cream information into the bus
There was a problem hiding this comment.
Do you remember when we were discussing at your house we said that we don't want people making generators/loads on the same bus as we want to force players to build transmission instead of building self-sufficient islands?
Also that there would be general buses as well as one special bus per player where they keep their ice cream.
To achieve this I was thinking to describe the limitations of what can be connected to each bus.
NPC Load bus -> Anyone can build a load
NPC Generator bus -> Anyone can build a generator
Player Load ice cream bus -> Only for the one player's ice cream
I am not proposing to keep track of how much ice cream is on the bus, that property is just a quick way to understand which buses are ice cream buses (same thing as a player bus) and which ones are not
There was a problem hiding this comment.
but remember that we would like to have a local market in each bus, so that it is possible to have both supply and demand (but from different players). Thus, the condition could be that for each bus, a player can only have one type of asset: generation or load. Remember we also spoke about the number of access points per bus (including transmission, consumption and generation).
RomanCantu
left a comment
There was a problem hiding this comment.
Perfect, we are on a good track. We could define from here separate tasks to work on simultaneously.
No description provided.