Destroying walls

[Uriel]

PLease leave this in bugs, because it should be treated this way.

How the hell am I suppose to remove palisade in my village and make brickwall? How? Wrecking ball destroys 1 tile, I have few hundread. I know that You dont test things before release, but fix it please.

[dageir]

Build a brick wall on the outside of the palisade. Or inside if you wish.

[MadNomad]

I think that the tiles that are next to destroyed one should take about 90% damage and the ones which have less than 50% hp should be vulnerable to palibashing with sledgehammer.

[Headchef]

Cascade was a good thing and removing it was a mistake

[Uriel]

I want to replace wall, not build another next to it. And it should be possible to do in less than a month.

[loleznub]

I'm not really sure what the intent of removing cascading was in the first place tbh.

A player bashing down a wall (offensively) makes no difference if one segment goes down or 15+ goes down. In the end they are able to raid.

The only thing this benefits is a player who had just built their wall (and thus is still handbashable) and realized they messed up. And it's only beneficial if they have to bash less than 5 tiles. I messed up one of my walls prior to this changing and lost ~200+ wall segments and 9 gates, along with the original cornerpost (i.e entire thing destroyed). Honestly, I would rather restart as that only takes 30 min to 1 hour time, versus waiting several months now.

Overall it was an update that wasted not only development time, but also the players time. But hey, I get it, they've gotta get them subs to keep running somehow

[SnuggleSnail]

I imagine it was to stop extension raiding.
IMO it's good extension raiding is gone because it's so new player unfriendly, but this iteration of mechanics I would argue has a lot of abuses that will affect players on the other end of the spectrum. Removing palisades takes like x20 more effort than building them, and unlike building them, usually requires an actualy character. I feel it's self evident why that's bad.

[MagicManICT]

I imagine it was to stop extension raiding.

You already cannot build walls on a claim you don't have permissions on, so that stopped that. There are still more than a few players that don't understand you should extend claims well past walls, but these are either newer or more casual players that don't have much to lose.

It was implemented because too many people were complaining about the amount of cascade. It was ridiculous when you could lose 20-30 tiles when you're just trying to remove a few, and I've heard of more. On the other hand, when you're trying to remove a 30-50 (or more) tile section of wall, too often you'd have to do it a few tiles at a time.

This needs a good mechanic in place to control removal of walls for when you're remodeling. I've seen more than a few ideas on it. For raiding, as long as it's more than a couple of tiles, does anyone care?

[bmjclark]

Cascade was a good thing and removing it was a mistake

This. The reason it was removed was a shitty bandaid to a bug.

It was implemented because too many people were complaining about the amount of cascade. It was ridiculous when you could lose 20-30 tiles when you're just trying to remove a few, and I've heard of more. On the other hand, when you're trying to remove a 30-50 (or more) tile section of wall, too often you'd have to do it a few tiles at a time.

That just isn't the case, it was implemented because there was a bug where you could build off walls that were on claim if their claim didn't extend past the edge of their wall meaning you could bash the unclaimed section after 3 days and get into the base. It opened shitty designed bases to old school palibashing in a way, and this was their bandaid.

Palisades should no longer cascade if smashed by hand, fixing a number of problems we've had recently with wall cascades used to break into bases.

They should have properly fixed this bug instead of giving us this because it is actually incredibly annoying to remodel palisades or even break unsoaked palisades now.

[MagicManICT]

it was implemented because there was a bug where you could build off walls that were on claim if their claim didn't extend past the edge of their wall meaning you could bash the unclaimed section after 3 days and get into the base. It opened shitty designed bases to old school palibashing in a way, and this was their bandaid.

I clearly stated that. This change in no way fixes the exploit. Even with the reduction, you can still apply this particular exploit if you really try. We've been constantly shifting our village layout around, and wall removal has been one of the biggest paisn, and under the current rule, we see 1 tile too often, but still get 3-5 often enough, and 3 in one direction or more is all you need to open a hole.The only way to prevent it is to make sure your claim is extended out past your walls at least one extra tile so that people can't extend a wall into your existing wall.