Animosity

[Ploeperpengel]

Heh, great sems to work now! I will add the promotions to the units now and upload a new patched version of WH tonight in the forum

 

[El Loco Mono]

Heh, great sems to work now! I will add the promotions to the units now and upload a new patched version of WH tonight in the forum

I hope you noticed my promotions.xml was an example only, I had Lions as invisible for tests and can't remember if I changed it back. Also the Show'Em promotion gave -1 terrian movement cost as well as +1 movement, i think

 

[Ploeperpengel]

I hope you noticed my promotions.xml was an example only, I had Lions as invisible for tests and can't remember if I changed it back. Also the Show'Em promotion gave -1 terrian movement cost as well as +1 movement, i think

Can't notice any more changes than the +1 movement there. If you used the latest xml uploaded I see no problem.

 

[El Loco Mono]

Having issues with the XML implementing the multiple Protaginists like the FreePromotions in the Unit XML. My structure is wrong somehow and I can't see why.

Sooo what I am going to do is just add 3 tags, Protagonist, Protagonist2, Protagonist3 and use them like the original single entry. It's not as tidy as making an array in the XML, but it's easy. It just means if you want more than 3 protagonists, it's a code change again - that's what I was trying to avoid with the array.

Hope this is OK - should get it uploaded tomorrow. And then I will get into the more "now" issues, like playtesting and bug hunting.

 

[Ploeperpengel]

Having issues with the XML implementing the multiple Protaginists like the FreePromotions in the Unit XML. My structure is wrong somehow and I can't see why.

Sooo what I am going to do is just add 3 tags, Protagonist, Protagonist2, Protagonist3 and use them like the original single entry. It's not as tidy as making an array in the XML, but it's easy. It just means if you want more than 3 protagonists, it's a code change again - that's what I was trying to avoid with the array.

Hope this is OK - should get it uploaded tomorrow. And then I will get into the more "now" issues, like playtesting and bug hunting.

Thx,
btw I'm totally stuck until the Warlordversion runs. Could you have a look at this first then?

Edit:
another note. We get ctds occasionally when the pythonbg lists getem. Because it's random I got no reliable save though. Hopefully it's not the formations again. I hoped the workaround we had actually worked
As soon the Warlord ctd is solved we should give it some serious playtesting before we convert the code also. I want to be sure there aren't any ctds in xml before we get back to python/SDK.

 

[El Loco Mono]

Both changes are done and tested, but I going to merge them on top of LO's latest spell code, so it won't be up until tomorrow now, but no later than that.

EDIT: Changes uploaded Animosity 2.1 there's an example in the spoiler of the DLL thread of how to populate the new 3 protagonist fields

 

[Ploeperpengel]

Thx.
A new patch is uploaded in the constr-site but I get crashes. Could you also have a look at it? I thought animosity probably giving some ctds since the pythondbg listed getem and showem as last actions. After anotherplaytest (public version) this times with the orcs I'm not sure anymore. Getem seems to work fine and they get each other a lot(probably will reduce animositychance to 5%). I never saw showem though during my wars. Maybe show em is crippled or it's something only if the orcs are AI or formations again or something else.

 

[El Loco Mono]

Thx.
A new patch is uploaded in the constr-site but I get crashes. Could you also have a look at it? I thought animosity probably giving some ctds since the pythondbg listed getem and showem as last actions. After anotherplaytest (public version) this times with the orcs I'm not sure anymore. Getem seems to work fine and they get each other a lot(probably will reduce animositychance to 5%). I never saw showem though during my wars. Maybe show em is crippled or it's something only if the orcs are AI or formations again or something else.

Looking into it now, have you got a save game I can use to replacte this (the problem is at version C?)

 

[Ploeperpengel]

Looking into it now, have you got a save game I can use to replacte this (the problem is at version C?)

I had 2 crashes with version C that weren't repeatable with the savedgame(each time the logs noted some animosity action- of course this still could mean it's because of formations)
version d is allways crashing instantly after turnend.
And Warlords is crashing during progressscreen.
Now that's some good score!

 

[El Loco Mono]

strange, sounds like a regression and a functions missing in the C++ code. Am I missing an XML patch after D, because the mod raises a whole bunch of errors in the UnitInfos.xml (i think it's the spell defines). (i just grabbed the latest ones in the construction thread)

EDIT I just said ok to the errors to get to the mod, and I did not get any crash, created a huge stack of Orcs and they did each other in fine with Get'Em without crashing. There must be a fundamental difference between your environment and the latest in the construction thread

EDIT2 Just got a ShowEm event, on a roll of 93, so it belive that's working OK. I do a full lenght, playtest with the orcs with the construction version version tomorrow and see how it runs.

 

[Ploeperpengel]

strange, sounds like a regression and a functions missing in the C++ code. Am I missing an XML patch after D, because the mod raises a whole bunch of errors in the UnitInfos.xml (i think it's the spell defines). (i just grabbed the latest ones in the construction thread)

EDIT I just said ok to the errors to get to the mod, and I did not get any crash, created a huge stack of Orcs and they did each other in fine with Get'Em without crashing. There must be a fundamental difference between your environment and the latest in the construction thread

oops seems I added the wrong unitclassinfos. Just delete the first couple of unitclasses until Lion should be ok then. That's just magicjunk from the old WH from JPeriod.

Edit: hm I'll check another time.

 

[Ploeperpengel]

No the crashes in the first round with version d certainly aren't animosityrelated. I think it's the spells. I placed a couple of wizards and books and tried to cast-nothing. After a couple of rounds it crashes again. I will try another without placing wizards just to see.(btw this time I used the version uploaded patched to version d-deleted the previous so it MUST be the same filestructure)

 

[Ploeperpengel]

Bump.

Need feedback about animosity. Is it fun? Happens too often, not often enough?

 

[Tue2000]

Its super fun, but very hard to control!

I'd probably reduce it just a little bit, as it seems very hard for the orcs to muster any kind of attack without getting a bloodbath amongst themselves .

 

[Ploeperpengel]

I will reduce it a little. Right now only Black Orcs can quell animosity but they're available maybe too late. I'm thinking about including an early hero that can quell animosity also.

 

[Opferlamm]

@Elm
I'm currently integrating animosity to the game.
thing I'd like to have changed:
-the promtion to quell animosity should only affect units in the same tile. Blackorcs leading a stack should quell all squabbling in their stack but shouldn't prevent being attacked by neighbor stacks.

What about a big Waaaghhboss being able to quell even the neighbouring tiles?

and what about the leader- and Waagh-updates (standard and army standard bearer) could they decrease the change for squabbling?