Running this mod made Evac All stop working. Unsubscribed and Evac All worked again. I saw some other strange stuff going on too - like my research tree was full of projects from other mods that should have been gated behind other research projects. I'm running LWOTC and mod jam (195 mods in total) - mods are weird in their interactions, is my takeaway.

This has an odd incompatibility with:
"[WOTC] Proficiency Class Plugin: Skirmisher" as it overrides the cost of the skirmisher abilities, notably Marauder
https://gtm.steamproxy.vip/sharedfiles/filedetails/?id=1990637687

Maybe mushashis ability as secondary mod (I think that's what it's called)

Any way to make it so that you use your Primary instead of Secondary?

@Dragon32 Wish granted

WOTC port of my original code is up:

https://gtm.steamproxy.vip/sharedfiles/filedetails/?id=1868288591

I've included the crit part, it was a good idea.

@BloodXIII:
No, apparently not. Whch is a real shame. I've been hoping for a while that GauravDas will update it.

So this doesn't work with WoTC?

Got a compatability issue for you somehow this and smart overwatch all(the one that reloads then overwatches if possible). Enabling this gets rid of the smart overwatch ability.

@FnD I just gave up in the end, I'm putting together a working modlist again, it's a shame this is a dead mod

Tested and it's crash in WOTC. It run fine if your soldier doesn't have Bladestorm, but when they have it, it crash in mission if place near enemy.

@reallyhairydave Have you come up any solution for this? I got stuck dame as you, crash when moving near the enemy

Confirmed, can run my modlist without this mod and no issue.

for WOTC*

No joke, i am 65% certain this mod broke the SPARK ability screen. I've been goign through a couple mods at a time, and this is the first so far that has caused the break.

All tweaking came up short, disabling the mod stopped the game crashing. While I'm disappointed the mod is broken with WotC there appeared to be something unexpected, bladestorm appeared to work as I set it up with this mod (a troop drop on top of my ranger activated bladestorm 3 times on the enemies moving away), this may be a result of not having unbound it (the option isn't appearing for me, I'll probably have to wait until I'm back on the Avenger).

The game starts up fine however now that I have bladestorm I'm hitting a crash every time my ranger gets close to enemies, I'm going to tweak the settings and if that doesn't work, disable the mod entierly, I will let you know the results

Working okay in WOTC? Also is it possible to disable the damn Muton counter to bladestorm? would it still counter if the range was 2?

nice work

@Derp King 1991 -_-:
You don't have to, from the Description:
If you do not want to use ModConfigMenu or prefer to modify the INI files manually, look for details here.

Just saying but i dislike having to use the ModConfigMenu -_- just saying

Note that this mod doesn't change combatives conunter-attack.

Tested and compatible with LW2 1.3. This mod modifies Bladestorm, which did not get changed in 1.3.

Is this mod impacted by the Shinobi changes in LW2 1.3?

I'll definitely use it on my next campaign! Thanks for making it LW2 compatible.

Thanks GD, that was exactly the response I was looking for. I never used bladestorm in vanilla because A) it sucked as you described and B) it required the risk of getting close. Atleast this mode can fix A) ...

GM: "You're leaving his zone of combat? Alright, you're taking an attack of opportunity. What's your AC?"

@LightenendDark
I personally use it with just the default settings, which remove the overwatch penalty from Bladestorm, but otherwise keeps vanilla behaviour.

I remember having a Bladestorm ranger in vanilla, way before mods like these existed. He managed to land just 3 of a total of 17 Bladestorm attacks thanks to the overwatch penalty.

Ah, lost my description after the last update!

@Greenburger
Need the mod config screen mod too.

Does the Mod Setting screen comes with the mod or do I need the mod config screen mod for that?

So uh, what are people doing with this mod once they subscribe?

Updated. Those semicolons shouldn't have been there, but I didn't think it would actually affect anything. UnrealScript is weird...

Just thought you should know: the semicolons you put after 3 of the ini options broke alien AI for me. As in the aliens just stand there looking stupid after you break concealment, they'll still patrol before they see you, but then just stand there like target practice. Removing those semicolons fixed it.

@mutant
That's Additional Icons by GrimyBunyip. I have disabled the loot indicator though.

could you tell me what is the mod you use to show ennemy stats and modifiers near their HB plz ?

the tactical usefullness of bladestorm is highly reduced in LW2 anyway, since you don't know where reinforcements will land (that was the most usefull feature IMO, to be able to shred reinforcements rigt away by putting the character at the cnter of the landing zone)
but still, your mod makes the skill more "real" =)

@ Professor Spank It
Is it a visualization bug, or does the attack really have crazy range?

I have seen a visualization bug in vanilla where Bladestorm attack animation happens before enemy move animation completes. I haven't changed the visualization code, so it is not fixed in this mod.

Haven't really seen any range bugs, with or without this mod.

Does this fix the base-game bug of bladestorm sometimes already having crazy range?

I've always felt that Bladestorm should have been epic considering the vast personal danger you have to place yourself in to use it.

Most melee attacks have a range of 144 when they cover only 1 tile to make sure they reach i guess. Look at the Andromedon punch as an example. It's also used for the Body Pickup action.

BIG_DAMN_PUNCH_RANGE=144 ; Unreal units away from body that is acceptable, one and a half tiles

@talemore
Oh, I understand now. Yes, the walls definitely do not count.

@GauravDas
1 tile = 96 in units
This is nerdy, but when a soldier is flanked, the soldier is no longer hugging the cover so the amount of units to reach the target should be increasing. i just wondered if tve game actually bother about walls at all or if them are all fake. Your answer answered the question = walls in xcom2 are fake.

Added a screenshot (4th one) of Bladestorm vs ADVENT Turret. Attack trigger works, no issues. Sweet explosion too.

If you can you should also implement a "one attack per turn" restriction. Bladestorm is easy to abuse if you park your BM Ninja in a Chryssalid group that's bunched up for example. The same way Combatives works. Just a thought. Subbed.

@The Artful Doge-er
Yes, Bladestorm will be triggered from attacking enemies adjacent to the Shinobi.
Do note however, that Bladestorm won't trigger on the same enemy twice in one turn.

@Naga48 ON by default. I will update the description.

You said that you could not add attack trigger option, but is it ON or OFF by default in this mod. I would gladly change old version on new one, to get trigger "on move away" but I don't wanna lose "on attack" trigger.

Does this mod make the Bladestorm perk can be triggered by any attacking enemies that are standing next to Shinobi or any soldier that uses Bladestorm?

@talemore
Bladestorm doesn't trigger with a gun, just with swords.

The gun equivalent for Bladestorm is the Assault's Close Combat Specialist ability. And modifying Close Combat Specialist would be an entirely different mod.

I don't exactly understand the melee range thing you mention. Bladestorm has a 1 tile range by default, and lowering it will mean that Bladestorm will never trigger.

Do you mean you don't want Bladestorm to trigger on enemies which have cover relative to the attacker?