Thanks for the heads up!
But that's what I figured, based on how they dealt with the other trackers and overlays.
I am planning to open source it (when I am at least somewhat happy with the implementation) but without any references to the bazaar.
It just so happens that it uses items with cooldown and similar systems that deal with burn, poison, haste etc. ;)
You can then bring your own items and play out the simulations and maybe your items just so happen to be based on the bazaar or maybe you create your own custom items based on lord of the rings or whatever.
Right now, the project's primary purpose is to be an interesting problem that needs to be solved and helping me learn new things.
Btw. your tool looks great! A shame that team tempo is against these kinds of community driven tools
I am working on a battle simulation for the game 'The Bazaar'.
I was quite frustrated with how the original devs handled monetization going into open beta, which sparked my motivation.
Trying out Kotlin for the first time and having a blast so far!
Also using an ECS architecture for the first time. It's quite a different way of reasoning about things, but it definitely helps with the dynamic fights that need to be simulated.
This seems to be very dismissive of all the physical evidence we _do_ have.
Text isn't the only way to store information, i.e. we can draw lots of conclusions from fossils, ruins or even sediment layers etc.
I am planning to open source it (when I am at least somewhat happy with the implementation) but without any references to the bazaar. It just so happens that it uses items with cooldown and similar systems that deal with burn, poison, haste etc. ;)
You can then bring your own items and play out the simulations and maybe your items just so happen to be based on the bazaar or maybe you create your own custom items based on lord of the rings or whatever.
Right now, the project's primary purpose is to be an interesting problem that needs to be solved and helping me learn new things.
Btw. your tool looks great! A shame that team tempo is against these kinds of community driven tools