Skip to content

Customize the chained damage of the wall #1776

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 5 commits into
base: develop
Choose a base branch
from

Conversation

TaranDahl
Copy link
Contributor

@TaranDahl TaranDahl commented Jul 17, 2025

Customize the chained damage of the wall

  • In vanilla, when the wall is damaged, it will deal 200 damage to the walls in the 4 nearby cells. This makes connected walls more vulnerable to damage compared to single walls.
  • Now you can customize that damage by using the following flag.

In rulesmd.ini:

[CombatDamage]
AdjacentWallDamage=200  ; integer

@TaranDahl TaranDahl added Needs testing ⚙️T1 T1 maintainer review is sufficient ❓Unhardcoding / Customization Make something more tweakable labels Jul 17, 2025
Copy link

github-actions bot commented Jul 17, 2025

Nightly build for this pull request:

This comment is automatic and is meant to allow guests to get latest nightly builds for this pull request without registering. It is updated on every successful build.

@TaranDahl TaranDahl requested a review from Coronia July 17, 2025 16:28
@Coronia
Copy link
Contributor

Coronia commented Jul 17, 2025

could it be made into a value tag that decide how much damage should be dealt to adjacent wall instead of the fixed 200? Could be named as AdjacentWallDamage perhaps, and use 0 to omit the damage

@TaranDahl TaranDahl changed the title Customization on whether the wall is recursively damaged Customize the chained damage of the wall Jul 22, 2025
@Coronia
Copy link
Contributor

Coronia commented Jul 22, 2025

c3d2231be09dc3188b8b943dc6571152 0 damage is not working in our testing, and it seemed that other damage value also didn't make a difference in the rate of wall destruction

@TaranDahl
Copy link
Contributor Author

@Coronia I guess your testing method might be incorrect. To clearly see the difference, you need a unit with a CellSpread less than 0.01. This is because the range within which projectiles damage the walls is the RangeFinding range, which is equal to CellSpread + 0.99.

@Coronia
Copy link
Contributor

Coronia commented Jul 24, 2025

AdjacentWallDamage=0 did make a warhead without CellSpread not damage walls around. But it seemed that higher value can't destroy wall either. This screenshot is from a test record where AdjacenetWallDamage=9999, with Conscript's warhead having Wall=yes

b2c28434de446a8626bb0a8851a9cb99

@TaranDahl
Copy link
Contributor Author

Strange, the testing on my side seems to be working properly?

@TaranDahl
Copy link
Contributor Author

@Coronia did you notice that the flag should be written in the section CombatDamage?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needs testing ⚙️T1 T1 maintainer review is sufficient ❓Unhardcoding / Customization Make something more tweakable
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants