Currently we're using pools as a way to implement lava pools. This works ok and on the client side we made a tool to export the pools as a json so we can load it into the configurator without much work.
However, we're leaking too many details to the client. The client shouldn't worry about effects and effect mechanics. So we should find a way for the client to export the lava pools as such (maybe with a type: lava field or similar) and have the configurator set up the effect and effect mechanics accordingly. That would also allow us to configure the lava damage from the configurator without having to modify the client to export the lava pools with the new changes
Currently we're using pools as a way to implement lava pools. This works ok and on the client side we made a tool to export the pools as a json so we can load it into the configurator without much work.
However, we're leaking too many details to the client. The client shouldn't worry about effects and effect mechanics. So we should find a way for the client to export the lava pools as such (maybe with a
type: lavafield or similar) and have the configurator set up the effect and effect mechanics accordingly. That would also allow us to configure the lava damage from the configurator without having to modify the client to export the lava pools with the new changes