[2.5.2 release YZAZ] Raiders siege looped infinitely

[Ruapehu]

A siege of a tribal holding bugged and now I get money for looting it infinitely.

No Mods, Ironman. Version 2.5.2, not beta.

I played as an Irish tribal count and attacked another Irish tribal count with Make Tributary casus belli. I had a small army of my own and raiders spawned from tribal event. I captured the first tribal holding by waiting. The enemy had a Cathedral in the same province and I stormed it. However, something's bugged and I got the message of successful siege over and over again and it gave me money over and over as well. You can see it on the screenshot.

Maybe it is connected with the new 'Groom an Heir' ambition. I canceled it, then picked 'Become King of Ireland'. Did not do anything else unusual from my early start.

Have a look at the screenshot attached.

Edit: Uploaded my Ironman save as well.

 

[rageair]

Interesting, it seems related to the fact that there's an allied army trying to siege the province while you're raiding it. I've added an issue to the internal database.

 

[Calvin_McG]

I'm looking at this same bug from the other side. Playing as Amalfi and my Capua trading post will occasionally get raiders besieging it. The first siege goes normally and takes the normal amount of time. After that, if the bug fires, the siege is "lost" again every single day until something moves the raiders. I've had 1k+ treasuries emptied to -250 on an ironman save because of this bug. The only way I've found to stop it is to force a battle, even if it's just ~12 guys going after the few hundred raiders. Of course, the bug can start back up again if the raiders decide to keep siegeing but sometimes the battle must push the AI into a different train of thought and the raiders leave.

 

[Keitaro_Ura]

I had the same bug.

As a hungarian king of Israel, I raided my neighbour Saffarid (Persia) until they defeated my army. For some reason I couldn't raid them anymore, I don't know if this is WAD (I had this happen in multiplayer).
To bypass that, I joined the kingdom of Mesopotamia in their war against Persia. I could raid them again and that's what I did.
After a while, I think that the castle that was already looted lost its "looted" state, and its levy and garrison went to 0 (I think i won the siege again, but I disabled the notification window for sieges).

The siege couldn't end and I earned more than 20 gold per day, it only stopped when the war ended (I couldn't raid at all anymore, just like before I joined the war).
I was alone on the siege, no ally involved.

I had all DLC's except the Sunset Invasion and Conclave.

There are two saves as attached files, one before and one during the bug.

 

[Neece]

I haven't seen the infinite looting scenario yet, but I did become unable to raid Wessex as Cornwall (Ruler Designer, Germanic faith). I didn't check immediately for I didn't know it, but it was after I lost a battle in Wessex. Hmm... going to try to recreate it now. Without and then with mods/ruler designer.
Oh, I'm using for mods Novus Graphicus, Ruler Designer Unlocked!, Your Personal Castle and [VS] Who wants to live forever?. As for DLC, I have habiliated Sunset Invasion, Sword of Islam, The Republic, Legacy of Rome, The Old Gods. And a lot of those portrait/song/model ones.

Just tested this on the same game. Raised a tiny (48) stack of vassal levies, led them myself, lost battle... could still raid them. "Big" (for the start of the game) army of 2.5k.
Tested again, same game, now 250 odd vassal army. Lost again, had an interesting effect. Now I could see the pillaging icon... with the message "Not allowed to loot King Alfred of Wessex". Lost a new battle with a 1k army, still like that. I think it's important to mention that, before my 250 strong army being killed, not only I couldn't raid but the icon didn't even apear. My 2.5k pillaging army could stand on any county without even triggering hostility - with pillaging on, land borders, ships to store loot, etc.

So, I'm starting to think this is Working As Designed... but in a non-intuitive & unclear manner. Does being defeated preclude you from looting someone? If so, for how long? Permanently? Some years? Until one of you die?
Well, just tested using the Console Commands. On this test, if the enemy ruler dies, you can raid again - I used the Kill command on King Alfred, could loot wessex provinces right after it. Tried it again in another game of mine that I had abandoned believing raiding was bugged, as a tribal ruler (same mods, starting in kiev with germanic faith). Also worked.
Just tested killing myself (on the kiev tribal game where I had heirs). It also removes the restriction.
Again with my Cornwell game, I could raid again in march 875. I didn't keep the date of the lost battle, but it couldn't be more than a couple years before that, as the Viking Age start is in 867, and at least some 2 years had passed. I'm going to guess 2~5 years, most likely five.

Well, since it seems to be consistent, even with few tests, it seems to be intended. The lack of information about it is a killer, though. Even the wiki had nothing about losing battles stopping you from looting. Is this information anywhere? The thing that makes it seem like a bug is the looting being impossible without any warning and your troops being able to, even while raiders, cross the forbidden territory and even stay on it without any repercussions (you don't become hostile) or a "can't loot" icon for gods know how long.

Sorry if I can't help with the multiple siege problem, but I hope this helped with the unable to loot one, Keitaro. It helped me, as I wouldn't have thought to test it if it wasn't for your idea of it being WAD. I hope we get some clarification on it, though.

 

[Keitaro_Ura]

I saw elsewhere on the forum that since the last patch you can't raid someone for 5 years if your looting army gets defeated by him (someone had to check the game files). So I'm guessing this is WAD, but it would be nice to have some feedback from the game, though, because the icon, as you said, doesn't appear. Thanks Neece, for testing that

I suppose forcing into raiding again by declaring war or joining one against the target will create the infinite loot bug, maybe.