Page 1 of 1

Anti-Downhit Declaration Code Discussion

Posted: Thu Apr 18, 2013 4:42 pm
by Darnivan
So the attacked ally trigger that lets you declare is just for unguilded? It sounded like the idea talked about last age for letting people declare on anyone that had attacked your ally but we tried to use it in game today and it didn't let me :(

Prevent downhit makes multi-guild wars frustrating, are we just supposed to try to do only 1 on 1 guild wars with so few options? So if you are the largest guild you are forced to downhit guild to guild because the game doesn't allow downhits kingdom to kingdom? Seems to encourage downhitting rather than discourage it.

Last 3 wars i've been in it is like all I can do is watch while the rest of my guild gets slowly killed by the people not in the guild we declared on while I can only give them a slap on the wrist because I'm too big to be allowed to fight back anymore. :(

Re: Anti-Downhit Declaration Code Discussion

Posted: Thu Apr 18, 2013 8:26 pm
by Darnivan
Oo, my post got split into a new topic.

Since it isn't in the same thread anymore my post was refering to:
Kaz wrote:Other configuration changes this age include :

'Preserve BRT' turned off in all games. Recent discussion has suggested that you'd rather not end up with less BRT buildings destoryed, so I've turned the feature to preserve them off.

'Enforce Guild or Quad' has been turned on in Domination and Guilds. This is a new feature to try and promote guilded or quaded play in those games designed for that purpose. You will be unable to declare war unless you are in a guild or quad. You will also be unable to declare war on any player that's not in a guild or quad.

Exceptions to this declare block will be in situations where the target has recently attacked you or an ally. The alliance can be made after the attack has occurred. Attacking an ally also allows for the normal downhit declaration preventions to be avoided.
I assumed the "Attacking an ally also allows for the normal downhit declaration preventions to be avoided." worked for guilded kingdoms as well but that doesn't seem to be the case.

Re: Anti-Downhit Declaration Code Discussion

Posted: Thu Apr 18, 2013 8:46 pm
by Kaz
The attacked ally trigger is not just about hitting Unguilded

There are 2 possible declaration preventions.

1. Prevents you declaring war on a kingdom with less that 90% of your total land
2. Prevents you declaring war on an UG (unless it's an NPC)

Both of these should not trigger in the event that the kingdom you are trying to declare on has recently attacked one of your allies.

By recently, that means attacks that are still listed in the kingdoms 9 vio slots. These are the slots that trigger the warmonger messages and they can be overwritten after 24 hours.

---

Ahh....

I see what the issue might be.

The kingdom that I suspect you want to hit has 'declared war' on Mickal right?. The one that you've declared on with your other kingdom?

If he's declared on your ally, that means that it wont create a vio entry (which is what your needing for the declare). Vio slots are for calculating the warmonger messages, so a declaration actually starts the process of clearing the number to free up vio slots.

That would count as an unforeseen circumstance that would create what would 'seem' to be a bug. Although it's not really a 'bug', just something I didn't think to code for.

If a kingdom has declared war on your ally you ought to be able to declare war on them. They can - after all - kill your troops through your alliance. You ought to be able to fight them for it

Re: Anti-Downhit Declaration Code Discussion

Posted: Thu Apr 18, 2013 8:49 pm
by Kaz
Ok... unless I've just killed the alliances screen with a parse error, you should be able to declare on a kingdom that is declared on an ally

[edit] there isn't a parse error so the one example where the new code fails to achieve it's intent, ought now to work as expected.

Re: Anti-Downhit Declaration Code Discussion

Posted: Thu Apr 18, 2013 8:58 pm
by Kaz
Now.... assuming that's no longer bugged, do your other comments still stand?

If they do, are they really downhit code relate? or would something as simple as the ability to declare on multiple guilds work just as well, without undoing the code that prevents certain abuses.

Re: Anti-Downhit Declaration Code Discussion

Posted: Thu Apr 18, 2013 9:08 pm
by Darnivan
Multi guild declarations would solve the issue as well I believe. How it is now is just horrible. I wasted so many turns getting ready to hit today only to not be able to do anything...I used turns on my human to get cash for my goblin and then had to send it back to my human when my goblin couldn't attack and use what turns the human had left to attack with... Though if you have the ally thing fixed that wouldn't have been so bad, I could have actually made a real attack at least, but that is still not nearly as good a solution as being able to make more than one guild declaration at a time.

Re: Anti-Downhit Declaration Code Discussion

Posted: Thu Apr 18, 2013 9:35 pm
by Darnivan
I burned my dec to test to see if the ally declared on issue was fixed for sure and it seems to be fixed.

Re: Anti-Downhit Declaration Code Discussion

Posted: Fri Apr 19, 2013 3:13 am
by Igneous
Yes! Waste your turns...... ::swings pocket watch:: do not downhit at all, especially on multiple guilds at the same time, no matter how hungry you are for land or how bored you get just never do it.......... ::snaps fingers::

Re: Anti-Downhit Declaration Code Discussion

Posted: Fri Apr 19, 2013 11:44 pm
by Aeropagitica
Come Igneous. Don't make us down hit. Uphit at us! Show us your many chest hairs!

Re: Anti-Downhit Declaration Code Discussion

Posted: Sat Apr 20, 2013 9:05 pm
by Igneous
Alas, I think I can only uphit due to my vertical taco neck syndrome, after so long of fighting from a smaller kingdom, I can only look up! :-) ::that, and i suck at this game, so i'm always driving my subcompact electric powered kingdom around:: at least my chin is stuck in the upright position!