Dungeon enemies rebalance: Aberrant Flesh

[ErhardSteinhauer]

About the PR

Aberrant flesh

Desired mob-to-mob difficulty progression:
jareds -> golems -> miner -> flesh horror; clamps and lovers are there just to spice things up a bit.

Changes made:

• Dungeon boss is a ghost role now. Has ability to shoot bone spike salvo;
• Changed mobs movement speeds: for melee mobs increased it to 4.5, for ranged mobs decreased it to 4, for boss increased it to 4.6;
• Nerfed maw: attack rate 1->0.3, reduced health 12->8 and life span 120->60, thus 1 maw attached to unarmoured Urist should deal 72 points of damage (blood loss is not accounted for though) in 60 seconds;
• Decreased the number of spawned mobs;
• Mobs spawned by assimilation sack move and attack at slower rates compared to regular ones;
• Added conditional spawners for individual mobs, hid from spawner menu wizden aberrant flesh mobs;
• Fiddled with bone spike projectile, it should work now.

Why / Balance

Testing the waters with this one, sort of speak. This is part of the rebalance attempt of every expedition faction group based on the data gleamed from this table. Overall goal here is to enforce difficulty progression both on mob-to-mob and on faction-to-faction levels.

Desired faction-to-faction difficulty progression (might change with feedback):
Aberrant flesh -> Carps -> Explorers / Punks -> Dinos -> Mercenaries -> Xenos -> Argocytes -> Silicones -> Syndicates -> Cultists

How to test

1. Spawn aberrant flesh mobs / delve into dungeons with this faction.
2. Spawn assimilation sack and wait for it to spew some mobs.
3. Spawn aberrant flesh horror, become a ghost, take the role, use its ability.

Media

Requirements

• I have read and I am following the Pull Request Guidelines. I understand that not doing so may get my pr closed at maintainer’s discretion
• I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Breaking changes

Changelog
🆑 erhardsteinhauer

• add: Aberrant flesh horror (expedition boss) is now a ghost role.
• tweak: Slightly rebalanced aberrant flesh mobs, updated guidebook entry on them with new values.

[github-actions]

RSI Diff Bot; head commit 6f318b7 merging into ba7e7f1
This PR makes changes to 1 or more RSIs. Here is a summary of all changes:

Resources/Textures/_NF/Mobs/Aliens/flesh.rsi

State	Old	New	Status
spike			Modified
spikeSolution1			Added

Resources/Textures/_NF/Effects/wet.rsi

State	Old	New	Status
wet			Added

Edit: diff updated after 6f318b7

[github-actions]

This pull request has conflicts, please resolve those before we can evaluate the pull request.

[whatston3]

Scanned the changes, they look alright, will fix up the merge conflicts and test locally.

[whatston3]

Interesting, should look into getting something like this into the xeno queen/space dragon mobs. Will see how it looks.

[ErhardSteinhauer]

It looks kinda fine, but perhaps this text suffers from the same issues any rules usually suffer: it might be defined too clearly which might be read by certain players as invitation to look for a way to grief without "technically" breaking any role rules. Idk. In any case, it's game admin issue.

[whatston3]

Minor rewrite, now fits on a window (at least with my UI scaling):

[ErhardSteinhauer]

I added a sprite for the "wet" visual effect to make fully formed aberrant flesh monsters and newborns more distinct visually.

[ErhardSteinhauer]

Not sure why RSI-validator test is failing

[whatston3]

Meaning to get around to this, but should be in good shape, will double check before approval when I can.

[chrome-cirrus]

Super excited to see this one go live, the changes are very cool and more ghost roles is always good.

[whatston3]

Added an icon to the bone spike action to match the dragon/baby dragon's spell (slight QOL improvement, lets you know you're trying to shoot darts)

Fixed up an older changelog entry (my own mistake), and cleaned up a reference to "BibleComponentComponent", which doesn't exist.

Might've fixed the issues with the RSI validator by running in 3.10 - looking at this, we could try and use the same "--break-system-packages" arg, hopefully it'd be isolated to the docker(?) instance, but at least jobs will pass/fail meaningfully now, even if this is a band-aid fix.

Changes seem good, let's go.