@frostion does this map have a train? I love the train that sneakingcoward has in the waw variant vxxx. And from the technical standpoint of view. The invasion of poland was caused by the refusal of Warsaw to allow the construction of a railroad that goes from germany to easter prussia (also called koeningsber).
Thanks in advance for your attention.
Kind regards.
@sneakingcoward I received an e-mail from you, and I already replied it to you, but I don´t know if I had better luck in reaching you.
Thanks in advance for your attention.
Kind regars.
@general_zod I thank you a lot that you take a look into my request. I really apreciate that effort. As I stated before in other post, it is an historical fact that recruits are used to defend the home territory. Hence, it makes sense to have the ability to defend at a roll die of 1, but are uncapable of attack. I just imagine that they can be involved in the offensive side as cannon fodder. Another way of see them is like the LHT rules of original A&A regarding the involvment of transports in naval battles. If the are in the attacker side, they can be used as cannon fodder, but they can´t attack. If they are in the opposite side, they can defend at a roll die of 1. If it is impossible for yo to make the change, it´s ok. I really appreciate your time.
Thank you very much.
Kind regards
I have just installed the engine version1.9.0.09687. And I deleted and downloaded all maps again. Unfortunately I still have the following pop up windows.
TripleA engine version 1.9.0.0.9687
SAXParseException: game: Test1, line: 190, column: 26, error: El tipo de elemento "attatchmentList" debe declararse.
SAXParseException: game: Test1, line: 191, column: 155, error: El tipo de elemento "attatchment" debe declararse.
SAXParseException: game: Test1, line: 205, column: 154, error: El tipo de elemento "attatchment" debe declararse.
SAXParseException: game: Test1, line: 220, column: 157, error: El tipo de elemento "attatchment" debe declararse.
SAXParseException: game: Test1, line: 228, column: 158, error: El tipo de elemento "attatchment" debe declararse.
SAXParseException: game: Test1, line: 235, column: 155, error: El tipo de elemento "attatchment" debe declararse.
SAXParseException: game: Test1, line: 242, column: 156, error: El tipo de elemento "attatchment" debe declararse.
SAXParseException: game: Test1, line: 249, column: 155, error: El tipo de elemento "attatchment" debe declararse.
SAXParseException: game: Test1, line: 257, column: 158, error: El tipo de elemento "attatchment" debe declararse.
SAXParseException: game: Test1, line: 264, column: 158, error: El tipo de elemento "attatchment" debe declararse.
SAXParseException: game: Test1, line: 271, column: 158, error: El tipo de elemento "attatchment" debe declararse.
SAXParseException: game: Test1, line: 278, column: 156, error: El tipo de elemento "attatchment" debe declararse.
SAXParseException: game: Test1, line: 286, column: 156, error: El tipo de elemento "attatchment" debe declararse.
SAXParseException: game: Test1, line: 293, column: 159, error: El tipo de elemento "attatchment" debe declararse.
SAXParseException: game: Test1, line: 301, column: 156, error: El tipo de elemento "attatchment" debe declararse.
SAXParseException: game: Test1, line: 304, column: 154, error: El tipo de elemento "attatchment" debe declararse.
SAXParseException: game: Test1, line: 310, column: 164, error: El tipo de elemento "attatchment" debe declararse.
SAXParseException: game: Test1, line: 313, column: 166, error: El tipo de elemento "attatchment" debe declararse.
SAXParseException: game: Test1, line: 318, column: 168, error: El tipo de elemento "attatchment" debe declararse.
SAXParseException: game: Test1, line: 321, column: 164, error: El tipo de elemento "attatchment" debe declararse.
SAXParseException: game: Test1, line: 324, column: 166, error: El tipo de elemento "attatchment" debe declararse.
SAXParseException: game: Test1, line: 329, column: 166, error: El tipo de elemento "attatchment" debe declararse.
SAXParseException: game: Test1, line: 333, column: 168, error: El tipo de elemento "attatchment" debe declararse.
SAXParseException: game: Test1, line: 531, column: 8, error: El contenido del tipo de elemento "game" debe coincidir con "(info,loader,triplea?,diceSides?,map,resourceList?,playerList,unitList?,relationshipTypes?,territoryEffectList?,gamePlay,production?,technology?,attachmentList?,initialize?,propertyList?)".
@sneakingcoward I already tried to reach you at the mail that you gave me. Unfortunately the server return it to me. I love this map, but I dislike the fact that recruits can´t defend at a roll die of 1, because if we attend to historical facts and common sense. All countries, when are invaded, use their recruits to defend their territory. I tryed to modify the xml file, but I have no luck with the change. Thanks in advance for your attention.
Kind regards.
A tech development option should be available. Thanks in advance for your attention.
Kind regards.
Recruits should have the ability to get involved into combat. They should attack at a roll die of 0 and defend at a roll die of 1.
Thanks in advance for your attention.
Kind regards.
It would be a great idea to have the option of a "historical start" or "do politics panel option" in order to enhance realism as it is in the big world 2: Raise of the axis map. Thanks in advance for your attention.
Kind regards.
@general_zod I don´t know if you are involved in the development of the Big World 3, but if you are, i suggest you to take a look into my other posts, (specially the one related to german wolfpack national advantages).
I am very pleased with the posibility of produce trains in the WAW vXXX v1.7.5, because (if we constrain to historical facts) the main reason from germany to be in war with poland was the refusal of this country to construct a railroad from germany to estern prusia (called Koeningsberg) in the WAW map. I would like to see trains in the big world 3.
Thanks in advance for your attention.
Kind regards.