Yes. It's a script mod so it doesn't really need updates.

Does this still work?

I highly recommend trying out an alternate mod manager (e.g., https://github.com/Shazbot/WH3-Mod-Manager) . I can't guarantee it will fix the issue with my mod, but that's the only thing I could think of. This is a very simple script mod

All 4 of us do indeed use the vanilla... although my one friend recently god a new one, albeit, it shouldn't be the cause as it was after this incident. It would be strange if it was due to the mod manager, though, I don't know why that would be the case. We had used the vanilla mod manager this whole time, only the most recent update causing issues, as we had the mod for quite some time prior.

If it is a strange confliction between mod managers... that just seems odd. Though, unlikely in our current case as it was before my friend switched, and even then, me as host, the game wouldn't allow my other friend who had just downloaded it to join. Who was also on vanilla mod manager.

Ohh interesting. Are you using the vanilla mod manager? I actually uploaded this mod with Propjoe's mod manager (which is wonderful) but sometimes it causes bugs with people who use the vanilla manager. That's the only thing I can think of.

I can always send you the mod collection if it helps in some way, but otherwise I can't really help explain what was wrong. The main issue simply being that it wouldn't allow us to join a lobby together. As it does the typical "Red outline" across the lobbies name.

All we know is we whittled down the culprits till this mod was the only one left in our load order for multiplayer. We could always do more testing to see if its an incapability thing... but both me and my friend are relatively tired of doing so together, and would rather focus on just enjoying the game.

We've since changed mods to something else. Otherwise, we aren't sure why it suddenly only now stopped working, only that it did and we can't really use it anymore in our mod collection. It could have also simply been a cache issue, but again, we aren't sure, as we had this happen earlier another day... but however this did happen with another friend who just subscribed to the collection as well so... we aren't sure. Sometimes it seems to work, sometimes it doesn't. Sometimes for some people, sometimes not for others.

I just checked the CA version of this script and it does not seem to have changed in any recent updates. In what way is it not working? I have never tested this in multiplayer

The recent update seems to have broken it in a strange way for multiplayer. For some reason, for one of my friends this mod works fine with our setup. But with another 2 of my friends it does not. We aren't quite sure why that is.

This is exactly what I've been looking for. The difference is clearly noticeable. Nice.

I have no idea. This mod does 2 things: it modifies the script that controls how much of your favored corruption you get for winning a battle (it's like 20 per battle in vanilla and closer to 3 or 4 with this mod), and it changes the threshold for when Vampire Counts take non-vampire attrition to make it closer to how it was in TWWH2. It should be compatible with most mods that don't touch these files

is this mod compatible with the mod that makes hashut a corruption type and what type of mods i need to keep away from this one

I haven't checked yet but I imagine it should work in 99% of cases unless CA decides to rewrite the corruption script. I'll go ahead and update it though to get rid of the warning message

work with 5.0?

@Brooks Just checked and it should still work!

@Brooks I would estimate 95% likelihood it still works. I'll boot up RPFM here in a bit to check. I can also update it to get rid of the warning. Sorry about that

@Scrambled Eggs
Hey! Any chance this mod is still viable?

@Scrambled Eggs
Thanks for checking, Scrambled Eggs, appreciate it

I just checked and the only difference between my script and the 3.1 script is the values I changed. So it should still be safe to use

Can I ignore this warning in PropJoe's?
These packs overwrite CA data and should not be used when outdated:
seggs_slow_corruption.pack overwrites:
script\campaign\corruption_swing.lua

I guess that .lua script wasn't updated by CA in 3.1?

awesome idea

Thank you very much !
That's really the mod I was looking for.

Love it.

So for anyone wondering, if my math is correct, vanilla killing 3 full stacks is like 55% of total corruption, which is wild. With this mod it would be like 15%

Yay