| ▲ | rappatic 3 days ago | ||||||||||||||||
I imagine we can do better than a flat array to represent the permanents on the battlefield. Lots of cards filter permanents by type, mana cost, etc. Building a consideration for this into the data structure is a natural idea. | |||||||||||||||||
| ▲ | olivergregory 2 days ago | parent [-] | ||||||||||||||||
Every card, permanent, spell, etc. is an object in Magic. So I’m using a set multimap, with the key being the zone the card is in. Those filters you mention are actually cheap until you get unrealistic numbers like those that let you win this turn or the next one. You could create an index of the mana cost, the types, but that ends up being over-engineered. I’ve tested using an ECS just for handling the core of the objects, but that lead nowhere event though it seemed a good fit from some perspectives. I’m not surprised that an array is actually efficient after trying so many implementations. | |||||||||||||||||
| |||||||||||||||||