oh ... mb didn't look much into it other than searching for it

Uh, thanks but I already know that since I have discussed that specific error with REITERPALLASCH literally below your comment.

Ok thank you.

Don't know what to tell you, I'm not script savvy so I tend to use really simple ROR scripts or incorporate other scripts with credits from other modders.
Considering that Volume I and II do not share common scripts I'm inclined to think that the error might be a simple reference error in my ROR scripts triggered due to how they are structured rather than anything else.
I wouldn't be surprised if that would be the case since I have seen many ROR scripts with different structures from other modders.
Considering that my ROR units work just fine I wouldn't be so worried about those errors.

Hey man just so you know this and volume 2 cause a script error "attempt to call a nil value" when using the console command mod that just recently had the ability to detect script errors built in. Not sure why.

love this pack, thanks for the work

Great collection love the work thank you

Yeah, I'm aware of 6.0.
Will update when the update is ready.

greenskin units will need updated they are not recruit-able atm and possible for tech changes.

thats good to know

Collections are always updated after I'm done updating ALL of my individual mods, so I wouldn't count on that "soon" too much if I were you.
On the bright side I don't see any outdated tables or errors in RPFM so the mod should still be safe to use even if the launcher says that it's outdated.

hope too see these 2 updated soon

thx zerg !! I really love and enjoy your masterpieces !!

Yes.
If you are still having issues or crashing, make sure that you actually have the latest version of the mod by unsubbing and resubbing.

So it updated on 26'th so I assume it's up to 5.x?

alright just makin sure your aware, cant wait for update these are nice units too use

I know that.
All unit mods need the 5.2 update.

both this collection and 2 need updating for 5.2

Thank you for the update

Correct.
This one still needs the 5.0 update.
Last update for this one was back in the 4th of April at 8:35 pm, exactly like this steam item's "Updated" section is claiming.

Hey, I believe this one isn't updated for 5.0 yet? My WH3MM claimed it was updated yesterday, so I came here to verify. I accidentally activated this with a bunch of 5.0 ready mods (all working) which makes the WH3 app "hang" before reaching the main menu.

Can't wait to use this one again, ready for 5.0. I see you were very productive, already updating a bunch of your mods. Keep up the good work bro, hang in there! <3

Yeah, you are not the first one to report lackluster battle performances with the Greater Feral Dread Saurian.
It got already buffed for the same reason back in Warhammer 2 but I guess that the first buff wasn't enough.
Getting the right balance with certain units can be complicated at times.
I'll try to improve his survivability a little bit.

I really like the giant version of the Lizard Man in the mod, but the unit data is a bit conservative. For example, if the size of the beast doubles, can its weight and health be doubled or increased by 50%. The volume of the dream saurian has doubled, and it will be attacked by more infantry at the same time. Can its health increase to 24000 or more, just like the big guy in the dwarf artifact mission. Because the original and the story's Dream Saurian are top-level monsters with limited recruitment, but they perform mediocrely when used

After re downloading, everything worked fine. Thank you for your reply

You see, since Warhammer 3 has horrible Lods generation most of my custom units are currently 0 Lod only.
This means that my custom units will ALWAYS have an higher performance cost if compared to vanilla units or other custom units that have normal Lods (maybe not performance hungry like a 4k graphic mod, but still).
So, even if you have the latest NASA PC, it would be wise to avoid having big battles with multiple full stacks of my custom units or you could end up (this is just me taking a wild guess so take it with a pinch of salt) experiencing graphical bugs or even crashes due to your PC running out of memory.
I may fix the whole 0 Lod situation in future (mainly for my fellow potato gamer fans) but that entirely depends on Ole and the next stable version of Asset Editor.
Ole once said that he was working on customizable Lod generation but nothing is certain or fully confirmed.

Just had a full stack battle with both of the normal and ror version against a full stack of black orcs and I couldn't replicate the bug with any level of zoom.
Again: the bug was caused by vanilla lowpoly references that were incompatible with those custom models.
The number of units on screen and casualities are completely irrelevant and have nothing to do with this specific bug.
So I think at this point that you may either have corrupted files on your part or steam didn't download the update properly, unsubbing and resubbing may fix that.
If not and assuming that you are still testing with only this mod enabled, then I would be inclined to think that you are experiencing a different but similar type of visual bug generated by the fact that your PC is struggling to have a full stack or even multiple full stacks of my custom units on screen.

It seems like it has been fixed, but the model is normal when there is only one or two teams. However, when customizing battles, more than ten teams of cavalry and enemies fight with more than half of the casualties, the model problem still occurs

Update is live and everything seems good now.
The issue was caused by a bunch of incompatible vanilla lowpoly imposter models that were tied to the riders.

Issue confirmed.
Will fix.

Can you fix the bug in war ox riders, or delete war ox riders? I really like the Lizard Man mod, but the bug in war ox riders has always affected the gaming experience

There is a big bug that existed from the beginning,is war ox riders，When the cavalry dies and the perspective is zoomed out, the model will tear and flicker in large areas, which is a serious bug. Running this mod alone will also do the same

I didn't care for the lizard men until the mod made me Kerrigan

Ok, everything is good here now.
Apparently the Greater Feral Bastiladon unit featured in the More Ferals for Lizardmen mod was still using the super old attribute resist_heat (Not sure why I gave it the attribute in the first place since it was pretty much deprecated already back then in Warhammer 2, but oh well) and CA decided to completely remove said attribute from the game which in turn caused that mod and this compilation to crash on startup.

Yeah I changed stuff about rampage and it could be related to that...but the thing is that I made very similar rampage changes to other mods included in this compilation and I don't have crashes with those.
The only mods that are currently crashing for me are the main compilation and More Ferals for Lizardmen so I'm 100% that something is wrong there.
Gotta understand what.

Rampage was changed... maybe its that? Sorry man not sure. Good luck

Yeah I'm aware of that, trying to understand why.
Seems to be tied to the More Ferals for Lizardmen mod somehow, since that's also crashing.
It's hard to understand what's the cause since RPFM is not giving me back any error atm.
It could possibly be tied to unit sets stuff but I'm not sure.

causing CTD after update

Aw www, wholesome moments here in the comment section....
You cuties! <3

Ah, Warhammer 2 nostalgia...good times!
Glad to see someone that enjoyed my simplier stuff from back then (even if I was way more inexperienced with a lot of things related to modding).
Thanks!

I'm honored you even know my mods exist! I've used yours since WH2's feral dinosaurs.

btw Zerg you make awesome mods, keep up the great work! <3

P.S. I have no idea if the update managed to bork specific submods for this mod or larger compatibility submods that include this mod like for example Bardathe111's Great Big Compatibility Packs and such.
You might want to wait for an update on the situation from the submodders.
Again, sorry for the possible trouble.

As some may have already noticed the visual update is live: please do check the change notes for additional details.
That said, we have just reached 1.5 GB of size, which in my opinion is pretty much critical mass for a compilation of units.
As of today this mod will NOT get any additional content.
We are officially in maintenance mode and all of the future updates to this pack will be just version updates, minor fixes and possible balancing.
All of my future eligible mods will be integrated in the Zerg Collection Volume II.

Also make sure to not run separately the latest mods that were included into the pack.

Try to unsub and resub, might fix that.
The update was pretty big.
Pretty sure that is not save compatible either, sorry for the trouble.

CTD after the last update

*DO NOTE x2*
Today's update is just the 4.1 update.
The visual update is still not ready.

*DO NOTE*
I'm currently updating most of my mods to fix various minor stuff.
This compilation currently DO NOT HAVE those updated versions.
This compilation will be updated at very end of this update process.

https://psteamcommunity.yuanyoumao.com/workshop/filedetails/discussion/2857626194/3431201423161262608/

It would be helpful to see what's inside this huge collection