|
Daniel Amieiro -> RE: 1812 scenario (5/2/2018 11:07:42 PM)
|
Hi!
I'm trying a patcher and i am pretty near of one.
I think i can try a 1812 scenario as a test.
Could you give me the data? (oobs, countries, etc). I have the 1812 scenario of EIA (the scenario in 13.0 section of rules).
I do not know if there are some major challenges to code, but
The main doubt is what would happen when i assign bernadotte to swedem and make a new pic for it. I can think all the rest is possible to patch.
Could you tell me what are the main challenges? Perhaps some can be patched, and leave the rest for you ;).
In my tests, my main issue are with kingdoms. I can do all kingdoms, but if a province belongs to two kingdoms (type 2 countries in .ged) the program behaviour is erratic (taking provinces randomly, not taking the minimun required provinces well and offering the kingdom with lowest country id first). So to work well, a province can only belong to one kingdom formation unless other behaviour being coded. (for example asking which kingdom to create, and if the province are belonging to a actual kingdom, check it, and if this kingdom is still possible, take the province, if not, then ask for destroy old kingdom (returning exceeding provinces as conq unless native) and form another... -> needed for westphalia improvement to C Rhin or to Bavaria going to C Rhin).
Other behaviour not coded are poland ampliation (can be done for any country). This could be most simpler to code. if a province is clicked for kingdom creation, and the kingdom is already created (it's checked already because shows the message "it can't create the kingdom" when it is not created it allows it) instead the program should ask to include it. Even better if kingdowm has more than minimum provinces and a kingdom province is clicked to ask to leave the kindom and return to a conq status (with 1 pp penalty)... It is specially useful for natal provinces that in many scenarios can be excluded for creating a kingdom.
So in 1812, it can be done C of the Rhine or Westphalia, but not both, unless excluding provinces of westphalia from c of rhine. Same for Bavaria kingdom if optional is used. (the EIA 1812 scenario has Westphalia, C Rhine and Bavaria created, i could recreate them, but as a tweak, these can't share commom provinces unless above corrected).
The Bernadotte going to sweden is not needed, because it should be on sweden and removed from france.
There is no automatic corp/general removal. There is an arrival field in the unit struct at 242 offset as a 16 bit signed integer. If this data is less than 1000 it counts the months to arrival from 1805 (or data of campaing), so a february of 1806 arrival is a -1013 value. -7 if unused unit. The 244 offset are the readyness (-5 if not ready like some feudal without provinces, -7 for unused corps). The 246 offset is unused. It could be coded there a go out date, for example. Unit fields has a lot of space (are a 640 bytes struct with 242 bytes used, perhaps 256). I recommend to code in unit the moral of each type of corp in these bytes (256 & up) instead of being a country based morale on tpj file (it could give a lot of special units, for example units with guard cavalry with 5.0 cavalry morale like EIH or a young and old guard units for france). For example, movement is coded in a unit basis (so it could be done a 4 movement corps, and a 3 movement corps whithin the same country)
|
|
|
|
