• We have updated our Community Code of Conduct. Please read through the new rules for the forum that are an integral part of Paradox Interactive’s User Agreement.
Showing developer posts only. Show all posts in this thread.

Wizzington

Game Director (Victoria 3)
Paradox Staff
41 Badges
Nov 15, 2007
12.853
152.474
  • Hearts of Iron II: Armageddon
  • Rome: Vae Victis
  • Victoria 2: Heart of Darkness
  • Victoria 2: A House Divided
  • Sword of the Stars II
  • Sengoku
  • Europa Universalis: Rome
  • Victoria: Revolutions
  • Europa Universalis III Complete
  • March of the Eagles
  • Majesty 2
  • Magicka
  • Heir to the Throne
  • Arsenal of Democracy
  • Crusader Kings II
  • Darkest Hour
  • Europa Universalis III Complete
  • Deus Vult
  • East India Company
  • Europa Universalis III
  • Divine Wind
  • For The Glory
  • Hearts of Iron III: Their Finest Hour
  • Hearts of Iron III Collection
  • Prison Architect
  • Shadowrun: Hong Kong
  • Shadowrun: Dragonfall
  • Shadowrun Returns
  • Stellaris: Humanoids Species Pack
  • Stellaris: Synthetic Dawn
  • Stellaris - Path to Destruction bundle
  • Stellaris: Leviathans Story Pack
  • Stellaris Sign-up
  • Stellaris: Galaxy Edition
  • Stellaris: Galaxy Edition
  • Stellaris: Galaxy Edition
  • Mount & Blade: Warband
  • Magicka: Wizard Wars Founder Wizard
  • Crusader Kings II: Holy Knight (pre-order)
  • 500k Club
  • Victoria 2
Hello everyone and welcome to another Stellaris development diary. As mentioned in last dev diary, we are still in full post-release support mode and until we are ready to get back to regular feature dev diaries, we're not going to have full-length dev diaries. Instead, we'll use the dev diaries to highlight certain fixes or tweaks coming in the rolling 2.0.2 beta update that we feel need highlighting. All the changes listed below will be coming in the next 2.0.2 update, which we expect to have with you soon.

Species Rights Changes
Both in order to fix some bugs caused by traits that alter species identity (such as Psionic ascension path traits), and to expand player freedom, we've made some changes to species rights. There are no longer any traits that cause a species to be considered entirely distinct from its parent species, so a Psionic or Hive-Minded Human pop is still considered to be a subspecies of Human. As it would then no longer make sense for all Human subspecies to share the same rights, we've added the ability to set rights for subspecies, so you can have, for example, different levels of military service and living standards for different subspecies of the same species living in your empire. However, there will still be certain restrictions for subspecies of your primary species, so if your empire is Human, you will not be able to purge a Human subspecies unless that subspecies has been majorly altered (such as being turned into Hive-Minded humans)
2018_03_22_3.png


Food Trading & Negative Food Spirals
We've had a bunch of feedback on AI and player problems with ending up in negative food spirals where a lack of food would cause starvation, reducing happiness and causing unrest, which would reduce food production, making starvation worse and creating a vicious cycle. To address this we've made a couple of changes. First of all, unrest and low happiness no longer reduce food production (they still reduce food from processing/livestock, as that represents the pops fighting back against being eaten). Secondly, we've improved the AI's understanding of food trading, so that it should heavily prioritize trading for food when in starvation. Finally, for those with Leviathans, we've added the ability to trade Minerals/Energy for Food and vice versa with the Trader Enclaves.
2018_03_21_1.png


New Marauder Events
In order to make it less of a pure loss prospect to start near Marauders, we've added some positive events that can only fire if your empire is bordering Marauders. These benefits might include gaining resources, pops, free ships and leaders, or temporary buffs to the effectiveness of your fleets.
2018_03_22_1.png


Occupation Armies
Since the army rework in 2.0, it's become significantly easier to snipe back planets that were recently taken by the enemy, as these planets lack a garrison to defend them. For this reason, we've implemented a new type of army type called Occupation Armies. When a planet is occupied, the occupier now spawns a garrison force of these Occupation Armies (the exact type varying depending on species just as with defense armies). Unless destroyed by battle or bombardment, the garrison force remains until the planet is either annexed or reverts to the owner's control.

Weapon Range Modifier
Since this is a topic that keeps coming up (because the way weapon range is implemented in the code is extremely complex and there is no one single weapon range modifier bug to fix, but a bunch of different places where it has to be hooked in correctly), I just wanted to mention that we've done some additional fixes, and believe that the modifier should now be fully functional. We've also implemented a separate ship_modifier entry for ship sizes that can be used to apply certain modifiers (such as firing rate and weapon range) that do not work in the regular ship_size modifier (as that modifier is applied to the ship design, and not the ship itself).

That's all for now! Remember that these are just a selection of tweaks/fixes, and there are many more that were not listed here but will be included in the patch notes when we next update 2.0.2. See you next week!
 
Dev diary thread was accidentally deleted somehow while being scheduled for posting. This reply is to bump it back to the top.
 
Could you give some insight to how weapon range functions? If I have BBs with X weapons and L weapons, do they stop as soon as the enemy is within range of the X weapons or do they continue in to a predetermined distance that ignores any weapon ranges you might have?

Seems to me having superiour weapon range allows you to fire a second before your enemy, and then it's all the same as it all just boils down to a brawl.

The combat computer decides the distance they stop at (unless they have Swarm behavior). This distance is modified by weapon range modifier, so a ship with a longer range will stop further away (for example, Artillery ships normally stop at range 100, but will stop at range 150 if they have +50% weapon range).
 
Will there be changes to achieve a 'limited victory' in liberation/subjugation wars. This was mentioned in last weeks dev diary but it wasn't clear if it will come.

Not in the next 2.0.2 version. Might be coming after that, but it depends on how complex it is and whether our ideas work out in practice.
 
Does the combat computer counts for individual weapon range when stopping the ship?

For example, if a BB has a 150 range XL weapon and a short range Medium weapon, will the BB stop when all weapons are within firing distance? or will it stop the moment one of the weapons is within firing range but disregarding the others (some weapons will be unable to fire).

The range it stops at is decided by what computer you pick, not by what weapons you pick.
 
Is the AI freezing / stopping building ships fixed, or was that most likely an issue caused by 2.0.2 updating mid-game?
 
So can using the Artillery and Line computers go badly wrong if you equip your ship with insufficiently long-range weapons and the enemy also have a move-to-fixed-range computer? Thanks for clarifying, but maybe the actual ranges should be in the description so the player can take them into account.

I will update the combat computer descriptions to include range numbers.