How to disable autoresolve for the player

**Aikanár** · February 19, 2012, 02:09 PM

That's a rather short one, in contrary to what might be communis opinio, disabling autoresolve for the player is a) very simple and does b) not, in any way, affect the AI! It definitely does not lead to a freeze in the AIs turn.

All one needs to do is to add restrict_autoresolve true after the general counter section of the campaign_script.txt without any monitor.

campaign_script.txt

Code:

;
; Campaign script
;
script
        ; ---------------------
        ; counters
		
        declare_counter Opened_Faction_Overview_Scroll
		declare_counter Opened_Settlement_Scroll
		declare_counter mongols_sarkel
		declare_counter mongols_yerevan
		declare_counter mongols_baghdad
		declare_counter timurids_sarkel
		declare_counter timurids_yerevan
		declare_counter timurids_baghdad
		
        
        ; ---------------------
        ; start up

        freeze_faction_ai aztecs
	restrict_autoresolve	true

        ;----------------------
        ; monitors

That's about it, but this disables autoresolve all together.

Another way of forcing the player to do something you intend him to do on circumstances is to force him to fight, autoresolve or withdraw by exploiting:

Code:

;---- forcing player to fight/withdraw/autoresolve
monitor_event	ScrollOpened	ScrollOpened	prebattle_scroll
log	always ;just for testing
disable_cursor
generate_random_counter	pbs	1	3	;to show randomness
campaign_wait	1
if	I_EventCounter	pbs	=	1
ui_flash_start	prebattle_fight_button
campaign_wait	1	;could be longer to let the player take a longer look at the prebattle_scroll
select_ui_element	prebattle_fight_button
simulate_mouse_click	lclick_down
select_ui_element	prebattle_fight_button
simulate_mouse_click	lclick_up
end_if
if	I_EventCounter	pbs	=	2
ui_flash_start	prebattle_auto_resolve_button
campaign_wait	1
select_ui_element	prebattle_auto_resolve_button
simulate_mouse_click	lclick_down
select_ui_element	prebattle_auto_resolve_button
simulate_mouse_click	lclick_up
end_if
if	I_EventCounter	pbs	=	3
ui_flash_start	prebattle_withdraw_button
campaign_wait	1
select_ui_element	prebattle_withdraw_button
simulate_mouse_click	lclick_down
select_ui_element	prebattle_withdraw_button
simulate_mouse_click	lclick_up
end_if
enable_cursor
end_monitor

Enjoy modding

**Savoyard** · February 19, 2012, 05:24 PM

Why wouldn't you leave auto resolve to a player's preference? Unless it's some story telling mod where you need to railroad the player, I don't see the point.

**Aikanár** · February 19, 2012, 05:32 PM

The point is the possibility and how to achieve it.
To what purpose this might be used is a different matter and up to the modders who might use it.

**Gigantus** · February 28, 2012, 10:06 PM

Nice find!

It actually works with the 'false' argument as well, making the long workaround obsolete, see docudemons:

Identifier: restrict_autoresolve
Parameters: [true|false]
Description: Enable/disable battle autoresolve restriction
Sample use: restrict_autoresolve true
Class: RESTRICT_AUTORESOLVE

**Aikanár** · February 29, 2012, 09:31 AM

Yep, false enables autoresolve again

One only needs such a workaround when you want to force the player to actually autoresolve.

**alleycat** · October 13, 2012, 10:30 AM

I've written this script based on yours, it disables siege for the player. good fun. I think I'll compile a list of buttons and scrolls next week and post it here, as finding the right name for things is the hardest part of this feature. Thanks again
edit:just saw they have the buttons listed in docudemons, I always do things the hard way.
monitor_event ScrollOpened ScrollOpened siege_scroll
and I_TurnNumber >= 1
;log always ;just for testing
disable_cursor
ui_flash_start siege_end_button
campaign_wait 1
select_ui_element siege_end_button
simulate_mouse_click lclick_down
select_ui_element siege_end_button
simulate_mouse_click lclick_up
enable_cursor
end_monitor

**Aikanár** · October 13, 2012, 01:43 PM

I'm glad that it's of use to you

Enjoy modding

**Gigantus** · March 31, 2013, 06:17 AM

We used this script in 1648 - it basically disables the mouse\cursor when the prebattle interface comes up, in this case the hist_schlacht counter is set by scripted battles once you agree to fight them, so you can't flee either

:

Code:

    ;--- Keine Feigheit vor dem Feind ---
    declare_counter hist_schlacht
    monitor_event ScrollOpened ScrollOpened prebattle_scroll
        if I_CompareCounter hist_schlacht = 1
            campaign_wait 1
            disable_cursor
            ui_flash_start prebattle_fight_button
            campaign_wait 3
            select_ui_element prebattle_fight_button
            simulate_mouse_click lclick_down
            simulate_mouse_click lclick_up
        end_if
        enable_cursor
        set_counter hist_schlacht 0
        
    end_monitor

**bitterhowl** · August 03, 2014, 09:40 AM

I have a problem with auto_win command. When I script slave army to attack player's settlement with auto_win the game shows prebattle window, to choose fight battle or autoresolve. And I want slave army to capture the city by auto_win. How can I solve this?

**Gigantus** · August 03, 2014, 10:11 AM

You need to change this line in my script above for the auto resolve button and adjust it into your script:

select_ui_element prebattle_fight_button
to
select_ui_element prebattle_auto_resolve_button

Sample:

Code:

    declare_counter auto_resolve_only
    monitor_event ....
        conditions for your slave attack
        set_counter auto_resolve_only 1
        other commands for your slave attack, eg spawn_army, attack
    end_monitor

   ;--- Battles are forced to auto resolve ---
    monitor_event ScrollOpened ScrollOpened prebattle_scroll
        if I_CompareCounter auto_resolve_only = 1
            campaign_wait 1
            disable_cursor
            ui_flash_start prebattle_auto_resolve_button
            campaign_wait 3
            select_ui_element prebattle_auto_resolve_button
            simulate_mouse_click lclick_down
            simulate_mouse_click lclick_up
        end_if
        enable_cursor
        set_counter auto_resolve_only 0
        
    end_monitor

**bitterhowl** · August 03, 2014, 12:10 PM

This is the script

Spoiler Alert, click show to read:

Well, here is the log

Spoiler Alert, click show to read:

**Gigantus** · August 03, 2014, 10:25 PM

Puzzling, both button entries are present in the EXE. I wonder if they need to be listed in a text file? Try replacing the auto_resolve with fight and then test if it gives an error message as well. It should force you to have a battle, but don't mind that - I just want to know if the old version works.

**bitterhowl** · August 05, 2014, 01:38 AM

Well, fight button works correctly. Battle on battle map begins by the script.

**Gigantus** · August 05, 2014, 04:35 AM

Did you try to fight the battle? Did the attacker win? I wonder if the auto_win attacker command means that regardless what happens in a battle the attakcer always wins? Or does that only work with autoresolve?

**Squid** · August 07, 2014, 11:27 PM

If my memory servers me, the script command auto_win attacker sets a flag so that the next auto resolved battle gets resolved in favour of the attacker's side.

**Gigantus** · August 08, 2014, 01:04 AM

Ah drat, any idea why the prebattle_auto_resolve_button isn't accepted? The prebattle_fight_button is fine. See post #12 for the HEX editor find.

**bitterhowl** · August 10, 2014, 12:24 AM

Well, when I fight on battle map I got Victory message after pressing Start battle button, because rebel army has no siege equipment.

**Ego123** · October 20, 2014, 04:40 AM

Very good script but in the naval battles i can chose only the windraw option,I don't get the autoresovle button,Is any way to fix that I want so bad to have this script in game I didn't autoresolve a battle from four years

I'm a die-hard player

this script fits perfect for my.

for now all I added in campaign_script is restrict_autoresolve true

**Aikanár** · October 20, 2014, 12:29 PM

^That is because there are nor "real" naval battles in M2K, all you have is autoresolve, hence why you are stuck with the withdraw option. You would have to enable autoresolve for naval battles with a monitor_event in the campaign_script.

**Ego123** · October 20, 2014, 05:19 PM

I play this game from 5 years I know they are not real naval batlles

.I just wanna find a solution to enable the autoresolve only for naval battles,could you recomand me a monitor_event specific for this?

Thread: How to disable autoresolve for the player

Thread Tools

Search Thread

Display

How to disable autoresolve for the player

Re: How to disable autoresolve for the player

Re: How to disable autoresolve for the player

Re: How to disable autoresolve for the player

Re: How to disable autoresolve for the player

Re: How to disable autoresolve for the player

Re: How to disable autoresolve for the player

Re: How to disable autoresolve for the player

Re: How to disable autoresolve for the player

Re: How to disable autoresolve for the player

Re: How to disable autoresolve for the player

Re: How to disable autoresolve for the player

Re: How to disable autoresolve for the player

Re: How to disable autoresolve for the player

Re: How to disable autoresolve for the player

Re: How to disable autoresolve for the player

Re: How to disable autoresolve for the player

Re: How to disable autoresolve for the player

Re: How to disable autoresolve for the player

Re: How to disable autoresolve for the player

Posting Permissions