- Joined
- Dec 31, 2013
- Messages
- 5,110
- Reaction score
- 617
Power blocks have one ID. Defined in ./data/config/BlockProperties.xml
You can't have different power block textures. It is the same with shields, thrusters, AMCs, etc...
That is true, isn't it?
My suggestion now is, to have not a single ID, but a range of IDs which have the same function.
AMC-Block-ID = 16:2
// means starting at ID 16, 2 IDs (16 and 17)
That prepares the way for an ID/inventory-collaps of all colored into one type, if it is desired to add it later to the game.
This prepares the way to add slightly different factions (Ork vs Eldar or rebels vs government).
This feature can either be used to mark primary and secondary colors / styles (so that they are both chooseable by the user when buying blueprints), to implement well-maintained vs weared-down items (later have a x% penalty on armour or efficiency) or factions which look completely different.
If then block-config has an option to add an overlay to the texture (2 textures), it could improve the game a lot.
Note for those who are worried about performance: if a caching mechanism creates one final texture, it doesn't need to calculate them every time.
Note for those who are worried about time requirements on implementation: damage overlays are already implemented. Just project one partially transparent texture onto the "prototype" texture of the blockID for rendered blocks
You can't have different power block textures. It is the same with shields, thrusters, AMCs, etc...
That is true, isn't it?
My suggestion now is, to have not a single ID, but a range of IDs which have the same function.
AMC-Block-ID = 16:2
// means starting at ID 16, 2 IDs (16 and 17)
That prepares the way for an ID/inventory-collaps of all colored into one type, if it is desired to add it later to the game.
This prepares the way to add slightly different factions (Ork vs Eldar or rebels vs government).
This feature can either be used to mark primary and secondary colors / styles (so that they are both chooseable by the user when buying blueprints), to implement well-maintained vs weared-down items (later have a x% penalty on armour or efficiency) or factions which look completely different.
If then block-config has an option to add an overlay to the texture (2 textures), it could improve the game a lot.
Note for those who are worried about performance: if a caching mechanism creates one final texture, it doesn't need to calculate them every time.
Note for those who are worried about time requirements on implementation: damage overlays are already implemented. Just project one partially transparent texture onto the "prototype" texture of the blockID for rendered blocks