How to disable autoresolve for the player

[Gigantus]

You could use the I_ConflictType Naval condition to handle the auto resolve in sea battles (remove the initial autoresolve entry).

monitor_event GeneralAssaultsGeneral true
    if I_ConflictType Naval
        autoresolve false
    end_if
    if not I_ConflictType Naval
        autoresolve true
    end_if
end_monitor

Please note that I haven't tested this.

[Ego123]

You could use the I_ConflictType Naval condition to handle the auto resolve in sea battles (remove the initial autoresolve entry).

monitor_event GeneralAssaultsGeneral true
    if I_ConflictType Naval
        autoresolve false
    end_if
    if not I_ConflictType Naval
        autoresolve true
    end_if
end_monitor

Please note that I haven't tested this.

Unfortunately does not work,the campaign is unrecognized,Thanks for trying,I would leave this excentric thing for the future because now I have a lot of work to do on vital stuffs of my sub-mod.

[Withwnar]

Those should be restrict_autoresolve and no doubt the log will be reporting some kind of error.

[Gigantus]

My bad.

[Ego123]

Something like this?

monitor_event GeneralAssaultsGeneral true
if I_ConflictType Naval
restrict_autoresolve false
end_if
if not I_ConflictType Naval
restrict_autoresolve true
end_if
end_monitor

[Withwnar]

Yes. Though I don't know if GeneralAssaultsGeneral fires on naval battles. Try it out and let us know.

Hmm, not sure if it fires for settlement/fort battles either.

[Gigantus]

That would be GeneralAssaultsResidence

[Ego123]

Sorry guys,I forget to post the result I added like this in the campaign_script

monitor_event GeneralAssaultsResidence true
if I_ConflictType Naval
restrict_autoresolve false
end_if
if not I_ConflictType Naval
restrict_autoresolve true
end_if
end_monitor

The campain is recognized but is not a change,I still have the posibility of autoresolve battles

[Gigantus]

Maybe the event is unsuitable. Possibly this one (from Aik's earlier code) might work:

monitor_event    ScrollOpened    ScrollOpened    prebattle_scroll

[bitterhowl]

How can I restrict withdraw from battle for player in some script cases?

[Gigantus]

Test for your condition, then set a a counter. Then in principle you could use the event from post #8 and instead of forcing the click of a button disable the end_siege button. Somehow an re-enabling of the button will have to be scripted as well.

If your goal is that the player has to fight then post #8 is all you need.

[bitterhowl]

Thanks, it works. I wanted a little different thing - to disable withdraw button when AI siege player's settlement. I made a script when rebels siege settlement with small garrison, without siege_settlement - I break a wall with console_command so they no need to wait while siege equipment will be built. And when I press withdraw on prebattle screen player's garrison go back to a settlement and no battle occures. So, if I could disable withdraw button player can choose to fight or to autoresolve (battle result is doubtlessly lost for player). #8 way is good and working of course.

And one more issue with this script - I wanted to open gates for rebels (as if there's a traitor in a settlement), but command damage_wall {settement_name} gate doesn't work, I have to damage wall, which is less realistic, you know )

[Gigantus]

Check this stuff. Some related things here.

Apparently 'gate' destroys the gate house (shooting and oil disabled) - which does not open the gate.

[Withwnar]

I made a script when rebels siege settlement with small garrison, without siege_settlement - I break a wall with console_command so they no need to wait while siege equipment will be built. And when I press withdraw on prebattle screen player's garrison go back to a settlement and no battle occures.

Do you mean that you're using "siege_settlement ... attack" without doing a "maintain" first? That does create a situation where the Withdraw button is enabled. Doing a maintain immediately before it fixes it...

siege_settlement my_general, the_settlement, maintain
siege_settlement my_general, the_settlement, attack

[bitterhowl]

Thanks a lot! I've read Taiji's list earlier, I learned about damage_wall from it at first time. And I haven't seen maintain+attack in scripts that I discover. Just one nore thing - how spy can open settlement gate? Opening gates from inside is more realistic for my purpose.

[Gigantus]

The simple presence of spy initiates a chance of the gates opening. The better the subterfuge traits of the spy the better the chance. You can stack the effect with up to three spies. It's nearly 100% then I think.

You would have to spawn and move spies into a settlement prior to the attack I assume. Afterward use the kill_character command to get rid of them again.

[bitterhowl]

Do rebels have spies? And it's pity that there's no console command for that.

[Gigantus]

They do have provisions for spies, but they are not enabled afaik. Might need a recruiting line in the EDB.

There is the perfect_spy command but I think that only works in conjunction with a script. (Never tried it)

[Kornstalx]

Maybe the event is unsuitable. Possibly this one (from Aik's earlier code) might work:

monitor_event    ScrollOpened    ScrollOpened    prebattle_scroll

Just in case anyone else was googling like I was for an autoresolve-disable (for purists) that doesn't break naval battles, your suggestion works. Thanks a ton!

;
; Campaign script
;
script


;------------------- DISABLE AUTORESOLVE ----------------------;
    
    monitor_event    ScrollOpened    ScrollOpened    prebattle_scroll
        if I_ConflictType Naval
            restrict_autoresolve false 
        end_if
        if not I_ConflictType Naval
            restrict_autoresolve true
        end_if
    end_monitor