base

[KuSpa]

create a base:

• [x] extend Tiles to have buildings on them (walls too afaik)
• [ ] update leveldescription to contain special information about buildings - outdated
• [ ] add a base to the leveldescription
• [x] reveal the tile the base is built on (on_start) to provide an area to start with - outdated

[KuSpa]

I don't have enough knowledge of the game to implement this(buildings) properly: I can imagine 2 ways of ownership and relations:

first:

pub enum Tile {
    Ground { concealed: bool, buildings: Vec<Box<Building>>},
    ...
}

pros:

• everything is in one place
• implementing electric fences will be easy, since we can look in neighbor tiles, if they contain a fence as well

cons:

• We need a Box (Building needs to be a trait for obvious reasons)
• Blows up our serializaztion

second:

struct Base {position: &Entity/Parent/Tile/..., ...} 

and add it as child to the Ground Entity

pros:

• lightweight
• correct encapsulation in my opinion

cons:

• (little) more complex lookup of position and neighborhood
• no explicit representation for serialization

[KuSpa]

I prefer the second approach.

[karyon]

yeah, second approach.