So in my game I’m making there are 251 collectibles. Amazing. And since there are so many collectibles I want to incorporate a save code (which is 308 digits long).
Anyway the base system for the collectables is:
251 Triggers (10% Memory)
200 Item Images (3% Memory)
61 Text (4% Memory)
Which means the base system adds up to 17% memory. No changing that. So what I need help with is the system which stores the collectible in the save code. Right now what I have is: A trigger increments a counter, which updates a property. Then when that property updates, it uses a trigger with blockcode to add it to a final property that stores the save code. The thing is the property limit is 128 so I’m fresh out of ideas. Does anybody have any?
Hmm, the property limit would be hard to work around. If you link multiple items to one property and have multiple properties linked to one trigger. Would that be of any use?
Hmm. How about reusing the same trigger? Like in the block code it could check for certain conditions. However, that wouldn’t really work unless you spam zones -_-.
I guess each collectable would need a property value. Then when the trigger activates it checks the number and see’s which value it is and make actions according to that.
Wait what if each counter thats linked to the trigger starts at [0, 1, 2, 3, 4, etc], then it would update the same property for all counters, then it would find the digit in the save code property and set that digit to 1?