Org Mobile Site
Thread: alpaca's Script-O-Rama
Note that this is only about editing campaign_script.txt (and show_me scripts)
I had a novel idea:
We seriously need a scripting tutorial. I think it's pretty hard to learn it by yourself, but at the same time that's what you desperately have to do if you want to become good.
So, I will start working on a basic tutorial, which I will edit into this very post, but in addition to that, the script-o-rama will contain a few other sections (in following posts):
- Scripting examples (how-tos mainly, and tutorials about special script features)
- Scripting tasks (these are supposed to challenge would-be scripters to think a bit first, and will have a proposed solution attached)
- Scripting concepts (here, I'll talk about some tricks and concepts I often use that are not exactly trivial, but can be very useful - these will be more like articles really)
For all of that, I'd like to ask for the help of the community.
Anybody who feels like he'd like to contribute a bit can write an example, task or concept article - and over time, I hope that the script-o-rama will become a knowledge-base in which all different experience levels of scripters are well-served.
You can also ask questions here or pose a scripting challenge which people can try to solve - I'll do that from time to time, as I think it's a good way of finding a good solution to have thoughts from different people on the topic.
At long last, this will go to both the .org and the TWC which will give it hopefully maximum exposure.
Please comment on what you think about this idea
--------------------------------------------------------------------
Contents
I The Tutorial
II How-Tos
II.1 Spawning characters and armies
II.2 Scripting for difficulty settings and player/ai only
III Articles
III.1 Logging for Scripters
III.2 Available UI Elements
III.3 Things to look out for
IV Examples
III.1 A good four turns per year script
III.2 A take on a re-emergent factions script
--------------------------------------------------------------------
Section I: The Tutorial
Prerequisites
To follow this tutorial, you'll need:
- Either the files released by CA(here) or the files export_descr_character_traits.txt, export_descr_ancillaries.txt, text/export_VnVs.txt and text/export_ancillaries.txt unpacked from the packs - for the latter two you need to convert them from the unpacked .strings.bin files using my .strings.bin converter
- A working mod folder, or a config using file_first. See this tutorial for instructions
- CA's docudemon files
It will also help to read these tutorials and articles:
- My traits tutorial
- My trigger tutorial
- The "Things to look out for" article
Please note that I will use [ex][/ex]-tags to signify additional information that you won't necessarily need, but you should refer to if you want to know something specific or didn't understand something. It will look like this:
In syntax definitions, I'll use the following symbols:
<x> - required argument
[x] - optional argument
{x,y,z} - set of required arguments (i.e. choose one, the special set {logic_token} means you can use one of the following: {<,<=,==,>=,>,!=} so smaller, smaller or equal, equal, greater or equal, greater, not equal)
Scripting
Writing a tutorial is always a hard and arduous process. It entails a lot of frustration and demands a large time commitment, but on the other hand it's often a very good way to become better at what you're writing about.
So, why am I writing this tutorial? To get better at scripting? Probably not. I'm already somewhat good at it, and most of what will go into this tutorial will probably be daily routine for me.
I'm writing this tutorial to allow new modders an easier access to one of the most difficult, but at the same time most interesting, areas of modding.
The problem I have with writing a scripting tutorial is that it's already pretty difficult to explain the basic concept behind it, but once you have grasped that, thinking out and developing your own scripts won't become easier.
A last word before I get to the actual tutorial: Before attempting to script, you should make yourself comfortable with editing traits or ancillaries, and especially with triggers. These are a bit easier to handle and provide a good start before you continue with scripting.
In this tutorial I want to walk you through the steps that you have to follow to create your first own script, which will give you some money and fire an event once you conquer Constantinople playing the Turks (note that I'm not one to start with a "hello world" equivalent for scripting but will take you right into the action).
1. The campaign script
The campaign script (data/world/maps/campaign/imperial_campaign/campaign_script.txt) is executed once at the start of the campaign and will then continue to run until its end. The state of the campaign script (including counter values and such) is stored in the save-game, in contrast to RTW.
So, what can you do with this file? If you open it in a text editor and have a look at it, you will notice that it's already pretty long in its unmodded state.
It contains a part that handles the Mongol and Timurid invasions (which is linked to descr_events.txt) and a few tutorials for the player.
However, for this tutorial, please copy the file and in the original, delete everything until it looks like this:
What you see above is an empty script, except for the wait_monitors command which tells the game to wait until all monitors are finished:
2. Monitors
Ah yes, the basic and most important scripting construct. If you want to become a scripter, it's paramount to understand these correctly.
Ok, but what is a monitor? First of all, there are two different types of monitors: monitor_event and monitor_conditions. Of these, monitor_event is far more important and more frequently used, because most conditions have a trigger requirement and therefore can't be used in a monitor_conditions
For our tutorial, we will only use a single monitor_event that will observe our capturing Constantinople:
This monitor is fairly straight-forward. It checks on a general capturing a settlement, and if that settlement is Constantinople and the general is Turkish, it will execute the code.
Nothing much fancy happens there, either: We throw a historic event for the player (we'll need to describe that later, mind) and give the Turks 20000 florins in cash.
3. Counters
Another important scripting aspect are the so-called counters. If you did a bit of programming in the past, these are somewhat similar to variables, but not quite.
The main use of counters is to store values, however it's often difficult retrieve these values again. To do that sometimes requires a lot of creativity and unorthodox thinking (I'll write a few how-tos later to show some of these principles and get you started) so a lot of counters are only used for boolean (i.e. yes/no) operations.
To use counters, you will first have to declare them. The syntax for this is:
This will initialize your counter and set it to 0
You can then interact with it via the set_counter and inc_counter commands and the I_CompareCounter condition.
In our example, I want to modify the above monitor to give the Turks less money when they capture the city for the second time and no money at all when they lost and recaptured it twice (but still fire the message).
Consider this code:
4. Describing the Event
Well this doesn't actually have anything to do with scripting, but we need to do it to finish our tutorial. To add the turks_capture_constantinople event to the game, we need to give it a title and body in data/text/historic_events.txt:
If you also want to have a custom picture for the event, you'll have to create data/ui/southern_european/eventpics/turks_capture_constantinople.tga and respectively for all cultures (I used the Jihad successful picture).
Now, enjoy your new historic event
--------------------------------------------------------------------
Section II: How-Tos
Spawning characters and armies
Scripting for different difficulty settings and player/ai only scripting
by tornnight
Section III: Articles
Logging for Scripters
Available UI Elements
Things to look out for
Section IV: Examples
A good four turns per year script
A take on a re-emergent factions script
by Red Spot
I had a novel idea:
We seriously need a scripting tutorial. I think it's pretty hard to learn it by yourself, but at the same time that's what you desperately have to do if you want to become good.
So, I will start working on a basic tutorial, which I will edit into this very post, but in addition to that, the script-o-rama will contain a few other sections (in following posts):
- Scripting examples (how-tos mainly, and tutorials about special script features)
- Scripting tasks (these are supposed to challenge would-be scripters to think a bit first, and will have a proposed solution attached)
- Scripting concepts (here, I'll talk about some tricks and concepts I often use that are not exactly trivial, but can be very useful - these will be more like articles really)
For all of that, I'd like to ask for the help of the community.
Anybody who feels like he'd like to contribute a bit can write an example, task or concept article - and over time, I hope that the script-o-rama will become a knowledge-base in which all different experience levels of scripters are well-served.
You can also ask questions here or pose a scripting challenge which people can try to solve - I'll do that from time to time, as I think it's a good way of finding a good solution to have thoughts from different people on the topic.
At long last, this will go to both the .org and the TWC which will give it hopefully maximum exposure.
Please comment on what you think about this idea
--------------------------------------------------------------------
Contents
I The Tutorial
II How-Tos
II.1 Spawning characters and armies
II.2 Scripting for difficulty settings and player/ai only
III Articles
III.1 Logging for Scripters
III.2 Available UI Elements
III.3 Things to look out for
IV Examples
III.1 A good four turns per year script
III.2 A take on a re-emergent factions script
--------------------------------------------------------------------
Section I: The Tutorial
Prerequisites
To follow this tutorial, you'll need:
- Either the files released by CA(here) or the files export_descr_character_traits.txt, export_descr_ancillaries.txt, text/export_VnVs.txt and text/export_ancillaries.txt unpacked from the packs - for the latter two you need to convert them from the unpacked .strings.bin files using my .strings.bin converter
- A working mod folder, or a config using file_first. See this tutorial for instructions
- CA's docudemon files
It will also help to read these tutorials and articles:
- My traits tutorial
- My trigger tutorial
- The "Things to look out for" article
Please note that I will use [ex][/ex]-tags to signify additional information that you won't necessarily need, but you should refer to if you want to know something specific or didn't understand something. It will look like this:
In syntax definitions, I'll use the following symbols:
<x> - required argument
[x] - optional argument
{x,y,z} - set of required arguments (i.e. choose one, the special set {logic_token} means you can use one of the following: {<,<=,==,>=,>,!=} so smaller, smaller or equal, equal, greater or equal, greater, not equal)
Scripting
Writing a tutorial is always a hard and arduous process. It entails a lot of frustration and demands a large time commitment, but on the other hand it's often a very good way to become better at what you're writing about.
So, why am I writing this tutorial? To get better at scripting? Probably not. I'm already somewhat good at it, and most of what will go into this tutorial will probably be daily routine for me.
I'm writing this tutorial to allow new modders an easier access to one of the most difficult, but at the same time most interesting, areas of modding.
The problem I have with writing a scripting tutorial is that it's already pretty difficult to explain the basic concept behind it, but once you have grasped that, thinking out and developing your own scripts won't become easier.
A last word before I get to the actual tutorial: Before attempting to script, you should make yourself comfortable with editing traits or ancillaries, and especially with triggers. These are a bit easier to handle and provide a good start before you continue with scripting.
In this tutorial I want to walk you through the steps that you have to follow to create your first own script, which will give you some money and fire an event once you conquer Constantinople playing the Turks (note that I'm not one to start with a "hello world" equivalent for scripting but will take you right into the action).
1. The campaign script
The campaign script (data/world/maps/campaign/imperial_campaign/campaign_script.txt) is executed once at the start of the campaign and will then continue to run until its end. The state of the campaign script (including counter values and such) is stored in the save-game, in contrast to RTW.
So, what can you do with this file? If you open it in a text editor and have a look at it, you will notice that it's already pretty long in its unmodded state.
It contains a part that handles the Mongol and Timurid invasions (which is linked to descr_events.txt) and a few tutorials for the player.
However, for this tutorial, please copy the file and in the original, delete everything until it looks like this:
Code:
script wait_monitors end_script
2. Monitors
Ah yes, the basic and most important scripting construct. If you want to become a scripter, it's paramount to understand these correctly.
Ok, but what is a monitor? First of all, there are two different types of monitors: monitor_event and monitor_conditions. Of these, monitor_event is far more important and more frequently used, because most conditions have a trigger requirement and therefore can't be used in a monitor_conditions
For our tutorial, we will only use a single monitor_event that will observe our capturing Constantinople:
Code:
monitor_event GeneralCaptureSettlement SettlementName Constantinople
and FactionType Turks
add_events
event historic turks_capture_constantinople
date 0 0
end_add_events
console_command add_money turks, 20000
end_monitor
Nothing much fancy happens there, either: We throw a historic event for the player (we'll need to describe that later, mind) and give the Turks 20000 florins in cash.
3. Counters
Another important scripting aspect are the so-called counters. If you did a bit of programming in the past, these are somewhat similar to variables, but not quite.
The main use of counters is to store values, however it's often difficult retrieve these values again. To do that sometimes requires a lot of creativity and unorthodox thinking (I'll write a few how-tos later to show some of these principles and get you started) so a lot of counters are only used for boolean (i.e. yes/no) operations.
To use counters, you will first have to declare them. The syntax for this is:
Code:
declare_counter <name>
You can then interact with it via the set_counter and inc_counter commands and the I_CompareCounter condition.
In our example, I want to modify the above monitor to give the Turks less money when they capture the city for the second time and no money at all when they lost and recaptured it twice (but still fire the message).
Consider this code:
Code:
declare_counter turks_capture_constantinople_counter
monitor_event GeneralCaptureSettlement SettlementName Constantinople
and FactionType Turks
add_events
event historic turks_capture_constantinople
date 0 0
end_add_events
if I_CompareCounter turks_capture_constantinople_counter == 0
console_command add_money turks, 20000
end_if
if I_CompareCounter turks_capture_constantinople_counter == 1
console_command add_money turks, 10000
end_if
inc_counter turks_capture_constantinople_counter 1
end_monitor
4. Describing the Event
Well this doesn't actually have anything to do with scripting, but we need to do it to finish our tutorial. To add the turks_capture_constantinople event to the game, we need to give it a title and body in data/text/historic_events.txt:
Code:
{TURKS_CAPTURE_CONSTANTINOPLE_TITLE}The Turks capture Constantinople
{TURKS_CAPTURE_CONSTANTINOPLE_BODY}An incredible event has occured! The Turks captured the unconquerable, glorious city of Constantinople and now have a foothold in Europe. The whole occident trembles in fear before the mighty new conquerors who were able to take one of the greatest cities of Christendom apparently effortlessly.
Now, enjoy your new historic event
--------------------------------------------------------------------
Section II: How-Tos
Spawning characters and armies
Scripting for different difficulty settings and player/ai only scripting
by tornnight
Section III: Articles
Logging for Scripters
Available UI Elements
Things to look out for
Section IV: Examples
A good four turns per year script
A take on a re-emergent factions script
by Red Spot
Post 2: Scripting Challenges
Allright people, this post is for now reserved for what I'd like to call scripting challenges.
I'll issue these from time to time to instigate research and thoughts about certain scripting problems, or simply to show off when I found out something cool and want to tell everyone how good a scripter I am
Anyways, here we go with the first challenge:
Scripting Challenge #1: Re-Emergent factions
issued on May, 20th 2007
The task is simple: Create re-emergent factions similar to those you know from the original MTW. I didn't try to do that myself, yet, so I'm not sure if it's possible. If you have a proposition, simply post it in this here thread.
The best one will be put into the script-o-rama, and I will participate, too.
Solution:
alpaca
Scripting Challenge #2: Attrition
issued on August, 30th 2007
This one is a very open challenge. I think a large part of the community is looking for the best way to simulate the effect that prolonged campaigns and diseases have on an army (especially a medieval one which would certainly live off the land in a very ruinous fashion). So, let's hear your suggestions! The best propositions will be put in here and if it makes sense I'll write a how-to or an article about it, combining them in some way.
Allright people, this post is for now reserved for what I'd like to call scripting challenges.
I'll issue these from time to time to instigate research and thoughts about certain scripting problems, or simply to show off when I found out something cool and want to tell everyone how good a scripter I am
Anyways, here we go with the first challenge:
Scripting Challenge #1: Re-Emergent factions
issued on May, 20th 2007
The task is simple: Create re-emergent factions similar to those you know from the original MTW. I didn't try to do that myself, yet, so I'm not sure if it's possible. If you have a proposition, simply post it in this here thread.
The best one will be put into the script-o-rama, and I will participate, too.
Solution:
alpaca
Scripting Challenge #2: Attrition
issued on August, 30th 2007
This one is a very open challenge. I think a large part of the community is looking for the best way to simulate the effect that prolonged campaigns and diseases have on an army (especially a medieval one which would certainly live off the land in a very ruinous fashion). So, let's hear your suggestions! The best propositions will be put in here and if it makes sense I'll write a how-to or an article about it, combining them in some way.
From future import content
Read on, nothing to see here
Just one more to go...
just an easy thing to do to crank up the early game difficulty a bit. remove stuff from the descr_strat file like buildings and units and then add them back in the campaign_script but AI only e.g
similarly add some extra rebel garrison units in the nearest cities for the player faction e.g
pretty quick and easy.
edit: just noticed on my test/mod version that adding the ports this way doesn't seem to work. the building is built in the settlement but no port on the map and no trade. i think this used to work in RTW but it must be different in MTW2. the recruitment buildings work though.
Code:
; ---------------------
; start up
freeze_faction_ai aztecs
if not I_LocalFaction spain
console_command create_building Leon, farms+1
console_command create_building Leon, port
console_command create_building Castille, garrison_quarters
console_command create_building Castille, bowyer
create_unit Castille, Peasant Archers, num 2, exp 0, arm 0, wep 0
create_unit Vaasco, Javelinmen, num 2, exp 0, arm 0, wep 0
create_unit Vaasco, Peasant Archers, num 2, exp 0, arm 0, wep 0
console_command add_money spain, 6000
end_if
Code:
if I_LocalFaction spain create_unit Toledo, Peasant Archers, num 2, exp 0, arm 0, wep 0 create_unit Extramaduras, Javelinmen, num 2, exp 0, arm 0, wep 0 end_if
edit: just noticed on my test/mod version that adding the ports this way doesn't seem to work. the building is built in the settlement but no port on the map and no trade. i think this used to work in RTW but it must be different in MTW2. the recruitment buildings work though.
Originally Posted by nikolai1962:
i'll add a bit here that i use a lot when i get home :)
Great, I'll start working on it after I tested 1.2 a bit more thoroughly. Actually primarily wanted to get some comments about the idea while I was doing that ;)i'll add a bit here that i use a lot when i get home :)
This is the classic spawn_army hint, considering the fact that the docudemon explanation always stumps newbies:
What's changed is that there is a comma after every unit name. This comma is absent in docudemon example of spawn_army, thus causing endless crashes and headaches for those starting out.
Great idea Alpaca, I should have a few more examples soon.
Code:
spawn_army
faction romans_julii
character Foedus Chaerea, general, command 0, influence 0, management 0, subterfuge 0, age 20, , x 54, y 124
unit roman generals guard cavalry, soldiers 20 exp 9 armour 1 weapon_lvl 0
unit roman legionary first cohort ii, soldiers 40 exp 0 armour 0 weapon_lvl 0
unit roman legionary cohort ii, soldiers 60 exp 0 armour 0 weapon_lvl 0
unit roman praetorian cohort i, soldiers 60 exp 0 armour 0 weapon_lvl 0
end
Great idea Alpaca, I should have a few more examples soon.
Well spawn_army works like this now:
Not sure if the soldiers thing still works, the attributes are handled through traits now.
Code:
spawn_army
faction slave
character Primus, named character, age 18, x 147, y 379
traits GoodCommander 1
unit NE Catapult exp 1 armour 0 weapon_lvl 0
end
Ok right, that's better syntax. But you forgot the comma, after unit name :)
Nope, it's a working code example.
Hmm ok well I'll test it out soon enough, this is puzzling for me. Meanwhile, I dug up Epistolary Richard's two scripting threads, which are frankly worth gold. I really think you should make a prominent link to them, or else incorporate them somehow: Beginner's and Intermediate Guide to scripting.
There are some fascinating tidbits from the Intermediate Guide. For instance, say you want your script to automatically automerge all units for you, but there's only one problem -- there is no scripting command to automerge. No worries, because TW scripting allows you to call shortcuts! Thus, you can create a script to automerge, or to automatically call Ctrl+S to periodically save your campaign, or any other shortcut like that. Here's the code, from the Intermediate Guide:
One interesting thing from there is that you can have your script order a "order_halt" shortcut (Backspace), and trigger it whenever an enemy character becomes visible. Without this feature, normally your issued movement orders will be continued to full, even if enemies become visible in the meanwhile; else, you need to carefully watch all your characters' movements and quickly press backspace, not a pleasant alternative. Of course this script would need to be balanced, because you don't want it preventing your characters from movement altogether, when within sight of enemies. So you'd have the script disable itself after it first triggers.
There are some fascinating tidbits from the Intermediate Guide. For instance, say you want your script to automatically automerge all units for you, but there's only one problem -- there is no scripting command to automerge. No worries, because TW scripting allows you to call shortcuts! Thus, you can create a script to automerge, or to automatically call Ctrl+S to periodically save your campaign, or any other shortcut like that. Here's the code, from the Intermediate Guide:
Originally Posted by Stuie:
or if you want your script to speed things up,Code:
monitor_event CharacterSelected FactionType romans_brutii
and FactionIsLocal
call_object_shortcut campaign_hud automerge_units
end_monitor
monitor_event SettlementSelected FactionType romans_brutii
and FactionIsLocal
call_object_shortcut campaign_hud automerge_units
end_monitor
monitor_event CharacterSelected FactionType gauls
and FactionIsLocal
call_object_shortcut campaign_hud automerge_units
end_monitor
Originally Posted by Myrddraal:
Here's a list of all ui_elements that can be called: https://forums.totalwar.org/vb/showp...25&postcount=5Code:
here is a neat scripting command which I found whilst working on the MP campaign: call_object_shortcut Here is an example of the syntax: call_object_shortcut strat_ui speedup_ai the strat_ui bit is the category of the shortcut. If you open data\text\descr_shortcuts.txt and scroll to the bottom end, you'll find a list of the shortcuts with their categories to the right.
One interesting thing from there is that you can have your script order a "order_halt" shortcut (Backspace), and trigger it whenever an enemy character becomes visible. Without this feature, normally your issued movement orders will be continued to full, even if enemies become visible in the meanwhile; else, you need to carefully watch all your characters' movements and quickly press backspace, not a pleasant alternative. Of course this script would need to be balanced, because you don't want it preventing your characters from movement altogether, when within sight of enemies. So you'd have the script disable itself after it first triggers.
Yep I was planning to go through these again to see what I can incorporate here.
Would be cool if you could explain a bit about the scripts you mentioned so I can copy&paste them into one of my above posts as examples, or about the call_shortcut as a concept (that was actually one I had planned but I am not at all averse to somebody else doing the work
)
Would be cool if you could explain a bit about the scripts you mentioned so I can copy&paste them into one of my above posts as examples, or about the call_shortcut as a concept (that was actually one I had planned but I am not at all averse to somebody else doing the work
)I think it's the create_unit command that doesn't work if you leave out the comma after the unit name.
Originally Posted by alpaca:
Yep I was planning to go through these again to see what I can incorporate here.
Would be cool if you could explain a bit about the scripts you mentioned so I can copy&paste them into one of my above posts as examples, or about the call_shortcut as a concept (that was actually one I had planned but I am not at all averse to somebody else doing the work )
Sure, no problem. I'll do it in a little bit, when I get everything straightened out over here.Yep I was planning to go through these again to see what I can incorporate here.
Would be cool if you could explain a bit about the scripts you mentioned so I can copy&paste them into one of my above posts as examples, or about the call_shortcut as a concept (that was actually one I had planned but I am not at all averse to somebody else doing the work
)PHP Code:
; Campaign script
;
script
; ---------------------
; counters
declare_counter Opened_Faction_Overview_Scroll
declare_counter Opened_Settlement_Scroll
declare_counter mongols_Volograd
declare_counter mongols_Ani
declare_counter mongols_Baghdad
declare_counter timurids_Volograd
declare_counter timurids_Ani
declare_counter timurids_Baghdad
; ---------------------
; start up
freeze_faction_ai aztecs
restrict_strat_radar false
;----------------------
; monitors
;-- Mongols invasions --
monitor_event EventCounter EventCounterType mongols_invasion_warn 1
and EventCounter > 0
; ADD SCOUTING INVASION
add_events
event counter mongols_invasion
date 4 8
end_add_events
if I_EventCounter mongols_invasion_warn == 2
terminate_monitor
end_if
end_monitor
monitor_event EventCounter EventCounterType mongols_invasion
and EventCounter > 0
if I_EventCounter mongols_invasion == 1
add_events
;;; SCOUTING INVASION
events emergent_faction mongols
date 0
; region Ani_Province
region Volograd_Province
region Baghdad_Province
movie event/mongols_invade.bik
;ADD MONGOL INVASION 1
events counter mongols_invasion
date 2
end_add_events
i traced the problem to this
00:50:00.781 [game.script.exec] [trace] exec <if> at line 42 in Europa/data/world/maps/campaign/imperial_campaign/campaign_script.txt
00:50:00.781 [game.script.exec] [trace] exec <add_events> at line 44 in Europa/data/world/maps/campaign/imperial_campaign/campaign_script.txt
00:50:01.546 [system.rpt] [error] Medieval 2: Total War encountered an unspecified error and will now exit.
Originally Posted by nikolai1962:
I think it's the create_unit command that doesn't work if you leave out the comma after the unit name.
As I said earlier, it's a freaking working example I think it's the create_unit command that doesn't work if you leave out the comma after the unit name.
@lordyu:
Code:
monitor_event EventCounter EventCounterType mongols_invasion_warn 1
and EventCounter > 0
Should be
monitor_event EventCounter EventCounterType mongols_invasion_warn
and EventCounter > 0
Originally Posted by :
As I said earlier, it's a freaking working example
yes but there's two ways to spawn units, spawn_army and create_unit. create_unit needs the comma.As I said earlier, it's a freaking working example
Originally Posted by nikolai1962:
yes but there's two ways to spawn units, spawn_army and create_unit. create_unit needs the comma.
Ah my apologies, I didn't read your post correctly yes but there's two ways to spawn units, spawn_army and create_unit. create_unit needs the comma.
lordyu, the actual problem in your code (aside from the "1" typo in the event handler) is that you use == in your if statements. You need to use =. The error log was helpful in tracing down that one.
In my experience you can use == as a logic token, it's the same as =
The original campaign script uses ==, too
The original campaign script uses ==, too
Ok, I resumed to work on this by adding a bit more to the tutorial. Will have a look at adding more stuff, too. Kick me a bit in the backside from time to time so I don't let this slip
Could You maybe make a list of new/changed features from RTW scripting?
That would be really helpful. I love that You can triger events from script, storing trigers in save files is pericles and IsSettlementBesige (Dont know exact frase) event is so great.
What else M2TW holds?
Links for CA docudemon files would also be great.
That would be really helpful. I love that You can triger events from script, storing trigers in save files is pericles and IsSettlementBesige (Dont know exact frase) event is so great.
What else M2TW holds?
Links for CA docudemon files would also be great.
Well I actually don't remember much about what has changed from RTW.
One of the things is that map-related stuff often doesn't work in show-me scripts (because the map isn't loaded at game start anymore but at campaign start).
The state of the campaign script is saved now though so that's no huge problem because we can use that for almost everything.
Another important change in 1.2 is the set_event_counter command which allows you to interact between different scripts, the edb and all files requiring triggers, and the ability to dynamically change leader AI personalities by script.
Anyways, I'll see what I can get together. A link to the docudemons will be added to the tutorial prerequisites.
One of the things is that map-related stuff often doesn't work in show-me scripts (because the map isn't loaded at game start anymore but at campaign start).
The state of the campaign script is saved now though so that's no huge problem because we can use that for almost everything.
Another important change in 1.2 is the set_event_counter command which allows you to interact between different scripts, the edb and all files requiring triggers, and the ability to dynamically change leader AI personalities by script.
Anyways, I'll see what I can get together. A link to the docudemons will be added to the tutorial prerequisites.
Added a how-to about spawning armies and characters.
Hi!
Does not work with a patch 1.2
Why? Here my command:
monitor_conditions I_TurnNumber = 1
spawn_army
faction turks
character Bel_Kermek, named character, age 30, x 279, y 138
traits GoodCommander 2
unit ME Bodyguard exp 1 armour 0 weapon_lvl 0
unit Turkomans exp 0 armour 0 weapon_lvl 0
unit Turkish Archers exp 0 armour 0 weapon_lvl 0
end
terminate_monitor
end_monitor
And in a patch 1.1 works.
Does not work with a patch 1.2
Why? Here my command:
monitor_conditions I_TurnNumber = 1
spawn_army
faction turks
character Bel_Kermek, named character, age 30, x 279, y 138
traits GoodCommander 2
unit ME Bodyguard exp 1 armour 0 weapon_lvl 0
unit Turkomans exp 0 armour 0 weapon_lvl 0
unit Turkish Archers exp 0 armour 0 weapon_lvl 0
end
terminate_monitor
end_monitor
And in a patch 1.1 works.
Originally Posted by grif:
Hi!
Does not work with a patch 1.2
Why? Here my command:
monitor_conditions I_TurnNumber = 1
spawn_army
faction turks
character Bel_Kermek, named character, age 30, x 279, y 138
traits GoodCommander 2
unit ME Bodyguard exp 1 armour 0 weapon_lvl 0
unit Turkomans exp 0 armour 0 weapon_lvl 0
unit Turkish Archers exp 0 armour 0 weapon_lvl 0
end
terminate_monitor
end_monitor
And in a patch 1.1 works.
Hmm it still works with that syntax for me, maybe you didn't add the name to the Turks' list of names?Hi!
Does not work with a patch 1.2
Why? Here my command:
monitor_conditions I_TurnNumber = 1
spawn_army
faction turks
character Bel_Kermek, named character, age 30, x 279, y 138
traits GoodCommander 2
unit ME Bodyguard exp 1 armour 0 weapon_lvl 0
unit Turkomans exp 0 armour 0 weapon_lvl 0
unit Turkish Archers exp 0 armour 0 weapon_lvl 0
end
terminate_monitor
end_monitor
And in a patch 1.1 works.
Originally Posted by alpaca:
Hmm it still works with that syntax for me, maybe you didn't add the name to the Turks' list of names?
Has added names.Hmm it still works with that syntax for me, maybe you didn't add the name to the Turks' list of names?
With this command the army does not appear also other commands cease to work.
P.S. I ask a pardon for bad English, I work with the program the translator.
If other commands stop working you made a mistake or used a command that disables them somewhere. Some commands aren't safe to use, so try just putting spawn_army into your script and nothing else (and be sure to put it into a monitor because the script can't spawn armies on game start)
Originally Posted by alpaca:
If other commands stop working you made a mistake or used a command that disables them somewhere. Some commands aren't safe to use, so try just putting spawn_army into your script and nothing else (and be sure to put it into a monitor because the script can't spawn armies on game start)
And how it is better to make? If other commands stop working you made a mistake or used a command that disables them somewhere. Some commands aren't safe to use, so try just putting spawn_army into your script and nothing else (and be sure to put it into a monitor because the script can't spawn armies on game start)
Write please that there was an army.
Single Sign On provided by vBSSO