Brazier mechanics

[darnokpl]

You should be able to eyeball it. And in what twisted world is it straightforward that building more braziers can result in both massively decreased and massively increased damage, and the interface tell you *nothing* about what's actually happening? Do you honestly expect new players to do hours of research on the forums before building stuff in the game, and think it's fair to punish them with base deletion for failing to do so?

+100

[Claeyt]

Because ***** it, critically important features should be too convoluted for any player to understand.

I don't necessarily think you should be able to put an exact number on their damage, no. The mechanic as such is straight forward enough.

At the very least please confirm that my calculated drawings of brazier fire mechanics are correct.

Also he's right about noobs learning this only from here. Can you please give some sort of explanation for new players on the wiki or on the in-game help? This is coming from one of your mods jorb, please listen to him.

[Potjeh]

Wiki ain't no good either. The interface it self should make it perfectly clear what the hell is going on. Though, I wonder why it has to be explained in the first place. I mean, what is the point of complicating defenses like this? To me it looks like just complexity for complexity's sake, with no actual practical benefits.

[Procne]

Because ***** it, critically important features should be too convoluted for any player to understand.

I don't necessarily think you should be able to put an exact number on their damage, no. The mechanic as such is straight forward enough.

I don't think it's about numbers but about mechanic itself. Specifically, whether clustered defenses deal reduced damage if not all of them are in range of player.
Or whether, or not, player can receive damage higher than base if 2 clusters are shooting at him.

[Mereni]

Wiki ain't no good either. The interface it self should make it perfectly clear what the hell is going on. Though, I wonder why it has to be explained in the first place. I mean, what is the point of complicating defenses like this? To me it looks like just complexity for complexity's sake, with no actual practical benefits.

It's an attempt to stop the 'brazier wall', like he said in the announcement post.

[Potjeh]

And how would that not be achieved with simple flat damage, regardless of the number, position and state of the braziers?

[jorb]

The reason being that we want to disincentivize spam.

[Potjeh]

But how would it make sense to spam more manhours into braziers than into the actual infrastructure they're defending?

[Mereni]

But how would it make sense to spam more manhours into braziers than into the actual infrastructure they're defending?

If damage done by braziers was the same across the entire claim, no matter how many or how few braziers there were, it would be incentive to spam. Because damage would continue all the time until all the braziers are gone and the more there are, the more time it would take.

But damage doesn't work that way. They interfere with each other, so you have to be careful how many you build and where if you want them to be effective, or so the update announcement seems to be saying. It'll be interesting to test it all out.

[Potjeh]

If there was more HP worth of braziers than of the actual buildings on the claim you'd just ignore braziers and go straight for a braziers, so there's a natural cap on how many braziers actually accomplish something which is proportionate to the actual level of development of the claim.