Report this content

As you say, the health manager detects health modifications. This is by far the most efficient and reliable way to transfer damage to targets, so you can just use that.

Unless you test some piece of logic and find it causes problems, I'd recommend just using that logic. Don't replace something with something more complicated if you don't need to, you know? Assuming that any logic you see has to be rubbish and bad for your project isn't a good way of going about building, or even optimising.

Test stuff, run experiments based on the expected uses of that logic, and expected scale of how much of that logic will be active at any given time. Base your decisions of how you want to change the logic on real data. Then a) you can make your own mind up on whether you "should" or "should not" use a given logic setup and not look for someone else to tell you, and b) the decision will be made for your specific circumstances instead of what someone on the internet who has no idea what your project involves said.

In summary: there's nothing inherently bad or inefficient about any gadget or tool in Dreams. You can tell that by the fact it's in Dreams. What makes a gadget bad is if it's not doing the thing you need it to--in which case scrap it and use something else that does the thing you need it to. What makes a gadget inefficient is if it has performance issues or uses too much thermo for what you need it for--in which case, see if you can change its settings to optimise performance, or use another method that uses less thermo. Until you *know* it's bad for your project, there's no need to worry about it.

Anyway... I hope this helps you move forward with your project.