Tiny Buildings Limits 1.0

[Wrda]

You could use a hashtable to map the ability to the build unit type using a hashtable, it will most likely be faster than looping through all the array
I think you can actually return the item charge to the inventory by "uses an item", since this event is triggered after the construction event. You'd basically register the building and associate it with the unit who built.
So if unit dies, check if has a "tiny" builder associated with, and give the charge back

Quite a useful system that expands on the "limit" concept from the standard way of building. If you want I can make an official review right now, but I don't think it is fair since it has this incompletion. Also, add GUI tag since you're also making support for it.

 

[Barade]

Hm I thought about just preventing the construction event and not the ability event in the beginning but then I have to kill the building and yes return the charge. I guess it is not possible that the hero uses the item and starts the construction of a building with a human build ability before it starts the construction with the item since it is already used. Not sure what prevented me from doing it this way. Not registering anything would be much better yes.

edit:
I think that the issue might be that you are not 100% sure if the associated item is the one which helped to construct the building.

The hero might use an item which does something completely different and then construct a limited building with a unit ability which might be very unlikely but possible. The unit ability could be based on a Tiny XXX ability and would not check the limits? In this case, you would return charges to the wrong item.

Maybe I could add some "exclusion" functions for this very unlikely but possible usecase.

 

[Wrda]

edit:
I think that the issue might be that you are not 100% sure if the associated item is the one which helped to construct the building.

The hero might use an item which does something completely different and then construct a limited building with a unit ability which might be very unlikely but possible. The unit ability could be based on a Tiny XXX ability and would not check the limits? In this case, you would return charges to the wrong item.

Maybe I could add some "exclusion" functions for this very unlikely but possible usecase.

Good point. Yes I think it's safe to say that the "exclusion" functions protect the users from themselves and the game.
Implement whenever you can