Comments - polloio

It's a feature of the game's engine, which locks the text when it encounters overflows.

Saving and reloading solves it.

It can happen with WSE (which is not a software of ours). Try moving the files from the WSE folder into the main Warband folder.

It should solve the issue.

We're working on it. No promises yet.

Yup, we're sorry for that error, but correcting it would require Nameless (the one with the admin rights to this page) to delete and reupload the whole thing....which we might do in the future when another fix comes out, solving this unfortunate error once and for all :)

We'd love to, but as of now we completely lack the manpower needed for more 3D art works, with the only two people in the team already working full time on fixing the (many many) items in the mod and completing the spells' visuals.

I'd say yes.
The mod has no spec table, being it just a mod...which means that you should check first and foremost the top specs recommended for the main game (Mount and Blade Warband) as the most solid guideline.

That usually happens when the engine decides that the text logs is overflowing.

Save and reload the game, it should solve it.

Unfortunately no.
There has been an attempt though, but it didn't work.

Join the discord server, where we post hotfixes and experiment with fixes.
Though be ready to restart from time to time as patches usually require a new game.

Also, gor that bug, you should check the patch for that exact bug posted here 1 week ago.

Come to our discord and download the exe (link in one of the previous news articles) or go to the taleworlds forum, search for WSE and download their exe.

The issue is caused by WSE being picky with the native exe for some reasons...

I awake from my slumber....

I read all the comments below this, and all the issues being pointed out find the same solution:

READ THIS GUIDE --> Docs.google.com

I won't write it so manh times, so I am doing an omnicomprehensive answer.

Cheers :)

That means that your WSE release is not made for your Warband release, so the Warband version you are using is outdated.

Anyway, read this guide: Docs.google.com

The Demigryph Knights can only be captured when defeating sepected imperial lords or rescued, mounts can be found through merchants.

It was in the 2014 release but had to be taken out as it would mess up everything for the factions using multiple skeletons/skins, making it impossible to work properly.

Reload your save and see if it starts showing them again.

If ut doesn't, start a second game and see if in that savefile it shows the messages.

If it does, then it's just Warband shutting down the messages because they are overflowing.
If it doesn't...well, the reason remains the same, no solution to that.

They'll eventually come back, when the engine decides that they are few enough.

Sure, and you didn't read through the past 5 years of explaining why that had to be done.

Which is a bad kickstart on the "lore" of modding Warband already...

You can't change your map icon in any way.

That is probably the only thing we don't need help with at all, but thanks for volunteering :)

The bug should have been solved by the last patch here on ModDB...but it wasn't apparently.

We're indeed giving it another go.

Which OPCODE errors are?
Have they started appearing after something specific happened in-game?

Yes, from Cyrus the Wizard's shop if I' not wrong.

Casters can only be rescued or taken prisonera at the moment.

An old bug left behind by Taleworlds when they moved to Steamworks.

Read thus guide please: Docs.google.com

Neither of those are available.

Also, mammoths are too big to be made as mounts.

We were already working on it but had to stop because of limited manpower.

Could be that or simply the fact that there are too many messages, not mandatorily bug ones, popping up.

Also, if those red messages say OPCODE 2077, you haven't installed or are not launching the mod properly.

Please read the instructions

There is no problem with skaven directly, just the random crash issue that in your case is triggered by skaven.

Read the guide (you can find the link in other comments of mine) please, that should help you mitigate those crashes.

As much as I hate to correct you mate, this time I must say that it's a "maybe" :)

Both of you, please read this guide :)

Docs.google.com

It won't solve the issue completely, we are aware of it, as we still don't k ow what is the cause of those random crashes, but it will mitigate their frequence.