AOD general dev suggestion

[unmerged(200423)]

Ok, i know the thread "list of wishes" in AOD general section but i would like to write a general dev suggestion from my point of view, so read my post filled with a lot of IMHO. (i'm not an expert in any way!)

As someone suggested in hoi3 forum, is acceptable that a dev team needs more money after some huge/good patches and long time passed (1+ year?) since the release of the game. Often this way is covered by an expansion release.

Anyway, i have no problem to pay for a "future patch package" (i.e. pay 10€ for patches package from 1.10 to 1.20) without new expansion.

Ok, so this is my idea (simplified) about economical problem.

Let's talk about game.
The idea, since i have read about the lack of manpower in bl-logic team:
main objective - remove more bugs as possible from the game and improve (as possible) the executing performance (speed). In other words: make aod more stable and faster.

second objective (for a major patch like 1.10, with the economical options illustrated above): add features to the game. But, i know, new features means new bugs (or instability) or performance drops.
For example (i use: http://forum.paradoxplaza.com/forum/showthread.php?464113-List-of-Wishes-for-AoD/page1 ):
Because the game allows you to store up to 999999 resources of anything, I was thinking maybe that should be capped based on 3-5x the resources needed to run at full IC for a year.
isn't a new feature, because i guess that it's a relatively simple change in the code.

instead http://forum.paradoxplaza.com/forum...es-for-AoD&p=12341065&viewfull=1#post12341065 i guess that it is a complex feature to add.

So add a lot of minor features is not so good for stability and performance. I think that AOD is a great game just now (1), and the main source for new challenges and games, given the game mechanics, are scenarios (or mods). Then the main feature to add is: better API for scenarios/modding.
More specifically a more complete script language (because scenarios are only script, AFAIK).
I mean, the major blocks like
event {..}
province {..}
country {..}
and son on are ok, but , mostly for events that fire dinamically during the game, more keyword and other things will be appreciated.
Keyword such as {if then elseif else control block keywords}, {for/while loop keywords}, etc..;
access to game variables like "year", "country.manpower()", "contry.tag", etc...
set variables of some primitive tipes, such as "int money=2000;"
This because triggers and command can do a lot of things but are limited or not compact.

for example secede russian provinces:
is a ugly list of:
secede to Slovakia a lot of f*ck*g russian provinces
secede to FIN a lot of f*ck*g russian provinces
...
eventually secede to GER a lot of f*ck*g russian provinces
It's quite hard to maintain or modify!

Instead:

//other code that assert some conditions or ghater information
//like
string list gerAllies;
  //type [list] varName
  //no init with declaration, for example.
for each gA in (alliesOf("GER"))
do
  gerAllies.append(gA); //few operations on list, such as first (with remove), last (with remove), append (to last) and maybe some others
done

string list gerAlliesTemp;
gerAlliesTemp = gerAllies; //it's a copy, there aren't pointers!

int maxIc;
maxIc=0;
int temp;
temp=maxIc;
string majorNat;
for each gA in gerAllies
do
  temp=ics(gA);
  if (temp>max)
  then
    max=temp;
    majorNat=gA
  fi  
done

//secede russian provinces

int enum russianProv = {pid1, pid2, ...., pidn} //enum only of basic types

for each rusP in russianProv
do
  secede(rusP,majorNat);
  //or
  removecontrol(rusP,SOV);
  addcontrol(rusP,majorNat); 
done

There are a lot of open source parsers that can be adapted for this work and this change will be a major features with easier scenario modding and maintaining . Of course a new feature like this needs a major patch release like 1.10 or so.

(1) but, obviously i agree with a lot of feature request, so AOD is not perfect.

PS: my english sucks.