Pazyryk
Deity
- Joined
- Jun 13, 2008
- Messages
- 3,584
32 bits would be enough for me. Is that 1 or 2 integers? If two, call them UNIQUE_FEATURE_MEMORY_1 and _2. These would keep track of special items gotten from UFs or other UF-related events or quests.
Edit: I could use 4 more integers for another project I'm working on. Call these ARTIFACT_1 through _4. (Won't give away too much, but two of the artifacts are a Golden Feather and a Coin of Mammos.)
It would sure be nice if these Feats or "memory" variables could be created by XML.
While I'm putting in requests, it would be nice if perTurn python scripts could be added modularly. I figured out that I can do this by adding a new trait to the barbs with a python call, but this is kind of inelegant.
Edit: I could use 4 more integers for another project I'm working on. Call these ARTIFACT_1 through _4. (Won't give away too much, but two of the artifacts are a Golden Feather and a Coin of Mammos.)
It would sure be nice if these Feats or "memory" variables could be created by XML.
While I'm putting in requests, it would be nice if perTurn python scripts could be added modularly. I figured out that I can do this by adding a new trait to the barbs with a python call, but this is kind of inelegant.