Hey Pjank.
I would say to start implementing theese comands for now.
This way I can recreate a full range of aircrafts buyable for the AI defined by a date.
The routes I would like to leave for now until I come up with something different to give the AI some liberty to work with the routes.
So, here are the comands to program for the AI to understand:
The "x" is always an integer from '0' to '9'.
1. buyfrom="xxxx" - Specifies the year from when the AI can buy/lease the specific airliner.
2. buytill="xxxx" - Specifies a year until the selected airliner type must be purchased/leased by the AI, maxing out the required amount (now 'late=', later 'mid=').
3. sellfrom="xxxx" - Specifies the year from when the AI can start selling the specific airliner.
4. selltill="xxxx" - Specifies the year till when the airline company must sell all the the specific airliners (reaching the value of 'late=').
5. forcebuyin="xxxx" - Instructs the AI to buy/lease all specified airliners the same year (maxing them out as specified by 'late=', later 'mid=').
6. forcesellin="xxxx" - Instructs the AI to sell all the specified airliners the same year (reaching the value of 'late=').
7. replacewith="name" - Instructs the AI to replace an airliner model with an another specified model (for example a Boeing 737-500 with an Airbus A320-200).
8. replacecount="x" - Instructs the AI how many replacements should be done (for example replacecount="7" means that the game must replace 7x737-500 with 7xA320-200 airliners). The count can not be more than the predefined count of 'mid=' (now 'late=') for the replacement airliner model (!only lower or equal!) and can not be more then the 'mid=' (now 'late=') count for the replaceable airliner type (!only lower or equal!).
9. replacefrom="xxxx" - The year since the replacement should be held.
10. replacetill="xxxx" - The year the replacement should be finished.
11. forcereplace="xxxx" - Replaces the specific airliners the specified year (only can be done if replacecount is="1" to avoid glitching and breaking).
Important lines!
12. mid="x" - Specifies the Maximum amount of a specific aircraft type buyable by the AI company. If the game sells them, the value will decrease and will become "0" again, specified as 'late=' from now on.
13. leaseable="true/false" - Instructs the AI to Lease or not to Lease the specific airliner type.
14. replaceable="true/false/input" - Lets the game replace models based on it's own choice.
- If set to True, no specific input will be needed, the game would read from the <prefereds>xxxx</prefereds> poll and would choose randomly.
- If set to False, the game can only sell the airliners.
- If set to Input, the game would read the data from the specified <airliner></airliner> section and would follow the instructions.
15. forceuse="true" - Avoids not using the aircrafts by the AI on routes (I presume that the game would buy them, would create routes, but some of the aircrafts may not be set to run. With this comand the game would force to add the purchased or leased aircrafts to it's lines, either they are new or already existing ones). It's necessary to add to every entry.
If missing, the AI may crash or not work properly.
16. ignoreinput="true" - With this comand the AI would completely ignore the specific airliner inputs defined in the, <airliner></airliner> field if needed. What I mean, it would not purchase the airliner type if he decides to not to do it (for example when it's not profitable, the AI is in debt, etc...)
Optional Inputs to avoid confusion for the AI:
17. usefrom="xxxx" - Specifies the year when the AI should start using the specific airliner type.
18. usetill="xxxx" - Specifies the year when the AI should retire the specific airliner type.
These two inputs should be added as optional inputs, becouse I'm not sure if the game would only buy the airliners and then leave them there without doing anything, so for security I added these params too, regardless of the 'forceuse="true"' comand.
I have started adding these params to the .xml's from now on.
You can start programming these features whenever you like to do so. In the .xml's the params will be there, hopefully the game will not crash becouse of them.
Have a nice day!
I would say to start implementing theese comands for now.
This way I can recreate a full range of aircrafts buyable for the AI defined by a date.
The routes I would like to leave for now until I come up with something different to give the AI some liberty to work with the routes.
So, here are the comands to program for the AI to understand:
The "x" is always an integer from '0' to '9'.
1. buyfrom="xxxx" - Specifies the year from when the AI can buy/lease the specific airliner.
2. buytill="xxxx" - Specifies a year until the selected airliner type must be purchased/leased by the AI, maxing out the required amount (now 'late=', later 'mid=').
3. sellfrom="xxxx" - Specifies the year from when the AI can start selling the specific airliner.
4. selltill="xxxx" - Specifies the year till when the airline company must sell all the the specific airliners (reaching the value of 'late=').
5. forcebuyin="xxxx" - Instructs the AI to buy/lease all specified airliners the same year (maxing them out as specified by 'late=', later 'mid=').
6. forcesellin="xxxx" - Instructs the AI to sell all the specified airliners the same year (reaching the value of 'late=').
7. replacewith="name" - Instructs the AI to replace an airliner model with an another specified model (for example a Boeing 737-500 with an Airbus A320-200).
8. replacecount="x" - Instructs the AI how many replacements should be done (for example replacecount="7" means that the game must replace 7x737-500 with 7xA320-200 airliners). The count can not be more than the predefined count of 'mid=' (now 'late=') for the replacement airliner model (!only lower or equal!) and can not be more then the 'mid=' (now 'late=') count for the replaceable airliner type (!only lower or equal!).
9. replacefrom="xxxx" - The year since the replacement should be held.
10. replacetill="xxxx" - The year the replacement should be finished.
11. forcereplace="xxxx" - Replaces the specific airliners the specified year (only can be done if replacecount is="1" to avoid glitching and breaking).
Important lines!
12. mid="x" - Specifies the Maximum amount of a specific aircraft type buyable by the AI company. If the game sells them, the value will decrease and will become "0" again, specified as 'late=' from now on.
13. leaseable="true/false" - Instructs the AI to Lease or not to Lease the specific airliner type.
14. replaceable="true/false/input" - Lets the game replace models based on it's own choice.
- If set to True, no specific input will be needed, the game would read from the <prefereds>xxxx</prefereds> poll and would choose randomly.
- If set to False, the game can only sell the airliners.
- If set to Input, the game would read the data from the specified <airliner></airliner> section and would follow the instructions.
15. forceuse="true" - Avoids not using the aircrafts by the AI on routes (I presume that the game would buy them, would create routes, but some of the aircrafts may not be set to run. With this comand the game would force to add the purchased or leased aircrafts to it's lines, either they are new or already existing ones). It's necessary to add to every entry.
If missing, the AI may crash or not work properly.
16. ignoreinput="true" - With this comand the AI would completely ignore the specific airliner inputs defined in the, <airliner></airliner> field if needed. What I mean, it would not purchase the airliner type if he decides to not to do it (for example when it's not profitable, the AI is in debt, etc...)
Optional Inputs to avoid confusion for the AI:
17. usefrom="xxxx" - Specifies the year when the AI should start using the specific airliner type.
18. usetill="xxxx" - Specifies the year when the AI should retire the specific airliner type.
These two inputs should be added as optional inputs, becouse I'm not sure if the game would only buy the airliners and then leave them there without doing anything, so for security I added these params too, regardless of the 'forceuse="true"' comand.
I have started adding these params to the .xml's from now on.
You can start programming these features whenever you like to do so. In the .xml's the params will be there, hopefully the game will not crash becouse of them.
Have a nice day!