De modo que el tema guerras es de momento el fallo mas clamoroso. Viene bien saberlo para tomar nota
Trencavel said:¿Y para cuando era la salida definitiva del 1.05? Es que no lo recuerdo...
Condottiere said:Sí, lo mejor sería que, en vez de sustituir rasgos por otros, mantuvieran los anteriores y crearan los nuevos. Pero como eso exige cambios de código profundos se dejará para próximos parches.
Jacme said:¡después de la 1.05 no habrá nada más!![]()
It should be noted that while, from time to time, new features or enhancements may be added to a game at no additional cost to the customer, these should be viewed purely as a "special bonus" rather than being expected as an integral component of our standard support and patching policy.
Jacme said:lo de "presión sobre el reino" no me acaba de convencer, pero me parece mejor que "estado de sitio".. y "tensiones en el reino"?
¿El territorio que atacas es propiedad de un infiel o pagano? Si es así, el comandante al cargo del regimiento asediante se queda con la provincia. Absurdo, sí, pues ello te obliga a tener al rey constantemente asediando TODOS los territorios (o en su defecto, a comandantes desconocidos) para quedárselo y luego repartirlos. Lo suyo sería que pasasen directamente al señor y que luego él los repartiese al gusto, como cuando conquistas provincias a los reyes cristianos. La diferencia es que las provincias que conquistas a cristianos te las quedas porque tienes reclamación sobre ellas.lukiskywalker said:Con la C me está sucediendo una cosa que antes no y me fastidia muchísimo. Cuando con mis tropas (no las de mis vasallos) ataco un territorio y lo conquisto muchas veces ese territorio pasa a ser un condado con uno de mis cortesanos como conde (con lo que si ese cortesano tenía un puesto en la corte ya me he quedado sin él) y para colmo algunas veces el condado ese aparece independiente. ¿os ha sucedido a vosotros?
-=]Travis[=- said:¿El territorio que atacas es propiedad de un infiel o pagano? Si es así, el comandante al cargo del regimiento asediante se queda con la provincia. Absurdo, sí, pues ello te obliga a tener al rey constantemente asediando TODOS los territorios (o en su defecto, a comandantes desconocidos) para quedárselo y luego repartirlos. Lo suyo sería que pasasen directamente al señor y que luego él los repartiese al gusto, como cuando conquistas provincias a los reyes cristianos. La diferencia es que las provincias que conquistas a cristianos te las quedas porque tienes reclamación sobre ellas.
El problema es que no los atacan tus vasallos, si no tú con tus propias tropas sacadas de los territorios controlados por tí directamente.tommassi said:No es tan absurdo. La Reconquista en la Península Ibérica muchas veces se llevó adelante por iniciativa privada de los nobles, que conquistaban las tierras para sí mismos. La cuestión es que, al ser ellos vasallos de un rey, los territorios conquistados se incorporaban a la Corona. O sea que, al menos para mí, tiene lógica.
Visto así, sí. Pero es que eso te limita mucho la estrategia a usar contra enemigos religiosos. Y ya que eres tú el comandante del regimiento (es decir, tú como jugador que da las órdenes a los diversos regimientos), lo suyo es que conquistasen para su rey. Eso al menos con los regimientos de las provincias propias. Los regimientos manejados por tí y propiedad de un conde o un duque vasallos si veo bien que se los queden ellos.tommassi said:No es tan absurdo. La Reconquista en la Península Ibérica muchas veces se llevó adelante por iniciativa privada de los nobles, que conquistaban las tierras para sí mismos. La cuestión es que, al ser ellos vasallos de un rey, los territorios conquistados se incorporaban a la Corona. O sea que, al menos para mí, tiene lógica.
Bien, habrá que probarla... A desinstalar y reinstalar y reempezar de cero... Qué pereza me da eso con Leinster, os lo juroMrT said:1.05 RELEASE CANDIDATE D
Change Log
- After discovering that Chris (MrT) had forgotten that leper was hardcoded to disallow a character to lead a regiment, there was a very messy and brutal execution, followed by the leper and stutter traits being swapped...so NOW leper = parental upbringing (since character is <16 and can't lead a regiment anyway) and stutter = realm duress.
- Tweaked the realm duress to give less intrigue loss and more diplomacy loss to liege
- The correct duke of Braganza now starts 1066 with "Spanish-level" coffers (500 gold) and his flunky does not.
- Primary heir is now allowed to become rebellious, but he is alot less likely to than other characters and he is also less likely to spark a civil war.
- A rebelious vassal may resort to assassination rather than outright rebelion -- particularly primary heirs (and even moreso if elective and/or BYZA). (Still require French and Italian translations of the new text for this please)
- Tweaked mtth values and some modifiers to reduce the threat of civil war (as opposed to limited war) somewhat and made it quicker for liege to lose realm duress trait when at peace.
- Counts are somewhat less likely to get involved in civil wars than before
- Extremely high vassal prestige (in the 4000+ range) will now make civil wars slightly more likely
- Extremely high liege pretige (in the 2000+ range) now has greater effect on dissuading vassals to rebel
- Fixed the missing text string for the end of the childhood events if raising your child yourself.
- Added in a few translations missing from the previous candidate. A very special thanks to all the members who took time to help me with these (and all previous translations too)!
- Illness should be slightly less prevalent
- It now costs less gold to have your child raised (childhood trait events), but now you lose a bit of prestige as well.
- Some claims and whatnot were added to the Seljuks vs areas in Anatolia in 1066. In theory, that war should be abit more in line with what we're shooting for now.
- A few of the more remove HRE vassals are now inclined to be rebellious in 1066. Might need a bit of toning down if it makes early break up of HRE too likely.
IMPORTANT REMINDERS:
If you gain a new title that is a higher rank than any title you own then you must pause the game, save, and then reload in order for it to take effect. So if you're a count and become a duke or king, or if you're a duke and become a king, then you should save and reload. Failure to do so will cause all sorts of possible bugs or crashes.
This patch should be applied over a clean 1.04a installation or on top of the previous release candidate patch.[/b] It will crash on a new installation that hasn't been patched to 1.04a since the official patch contains necessary files that are not included in this public beta patch (to help keep file size down).
If you’ve edited any of your own files or are using any mods, please remove them and revert to a vanilla copy if you want to give feedback (else your feedback will be either worthless or potentially detrimental to the process).
SUPER-IMPORTANT!
If you haven't done so already, please make sure that you read THIS POST which contains vital information about using and reporting about this beta patch. If you followed the instructions for Candidate A, you may simply install this on top of your existing installation. If you haven't followed the instructions, please do so but install this patch instead of the Candidate A patch.
THIS CANDIDATE IS NOT COMPATIBLE WITH ANY SAVE GAMES MADE PRIOR TO THIS REALEASE!!!
Any save games made with Release Candidate C or earlier ARE NOT compatible with this release candidate due to Chris' idiotic blunder with the leper trait. Sorry about that.
AND A SPECIAL REQUEST...
Because we've responded to your concerns and have made a rather massive revision to some event sets as well as added more than 6300 lines of new event script, we very urgently need to balance them ASAP (we have less than 10 days to finish this!). This candidate will not be compatible with any existing save games so you'll need to start a new game to test it. We BEG anyone who is testing to PLEASE START YOUR NEW GAME USING NORMAL/NORMAL GAME SETTINGs and do your testing at those difficulty/aggresiveness settings until advised otherwise. This is our target for balancing and is the most crucial of all for us to achieve. Once we are comfortable with the normal;/normal performance, we can then tweak the balance for other settings.
Thank you.
NOW POSTED