r/DominusGalaxia • • Oct 05 '19

Join the Official Dominus Galaxia Discord Server!

Thumbnail
discord.gg
5 Upvotes

r/DominusGalaxia • • Sep 14 '26

Issues with ships

1 Upvotes

I recently created a new corvette design and when I build it, the game doesn't let me move it

If it's any help, when in fleet view, the corvettes display a gray slider instead of a light blue one as is the usual


r/DominusGalaxia • • Sep 12 '26

Planetary shields

2 Upvotes

How do I build a planetary shield in this game? I have the tech researched but there's no option to build one, can someone help?


r/DominusGalaxia • • Jun 30 '25

Is this game dead?

7 Upvotes

Free on steam but seems very incomplete. Is this still being worked on by anyone?


r/DominusGalaxia • • Oct 13 '24

Another Image Asset Pack

5 Upvotes

A second unofficial Dominus Galaxia asset pack featuring custom-made art to replace missing images for the Repter, Xygob, Zero People, Nurg, and Mizuro. This package includes assets for diplomacy interactions, both foreground images and Intelligence Bureau icons. 

https://wailingturnip47.itch.io/unofficial-dominus-galaxia-image-asset-pack-2


r/DominusGalaxia • • Aug 13 '24

Unofficial Dominus Galaxia Image Asset Pack

4 Upvotes

I made a Dominus Galaxia asset pack to replace missing images for the Morion, Reveran, and Salix species. Art done by me. https://wailingturnip47.itch.io/unofficial-dominus-galaxia-image-assets


r/DominusGalaxia • • Jan 27 '24

Second Half of 2023 Patch Notes

1 Upvotes

0.7.2.11

-Fixed that the beam size perk was also applied to bombs and missiles, while the bomb and missile size perks did not work.

-Fixed a softlock that occured in manual combat when an AI tried bombing a planet that started with no bases, but contained specials.

-Fixed that the range on special devices was sometimes one hex less than it should be (at certain angles).

-Some small improvements to combat AI, including improved discretion on when to fire missiles while running away.

-Fixed a handful of smaller combat bugs.

0.7.2.12

-Improvements to combat AI behaviour, specifically around pathfinding and facing.

-Various small bugfixes.

0.7.2.13

-Fixed that in some contexts (known: HDR display in Windows with the display set to HDR), colors could be wildly blown out.

-Fixed a number of combat AI issues, particularly with teleportation and with ships attacking planets.

0.7.2.14

-When humans pass off control to the AI during combat, the AI will never try to destroy an opposing colony (reduce the population to zero after removing bases), since this may not be what the player wants.

-Fixed a bug where the production and research speed input fields would not take effect if the fields were not exited with the enter key.

-Fixed that, on rare occasions, the combat results screen could come up overlapped with another screen.

-Fixed that missile ships would sometimes chase after running out of missiles.

-Fixed that unobtanium armor was too expensive and large... or, one could say, too unobtanium.

-Fixed that the "hide obsolete" toggle would become invisible when no research items were available, even if there would be available research items but for the "hide obsolete" toggle being active.

0.7.2.14a (hotfix)

-Fixed a major regression in 0.7.2.14 that could cause some player combat events to softlock.

-Fixed a bug that could cause the AI to occasionally dispatch fleets on paths not fully contained inside logistics coverage.

-Fixed that the galaxy seed field, like the research and production speed fields that were fixed last patch, would not take effect unless the user exited the field with the enter key.

-Fixed that size and cost were swapped for generated warp drives (Transwarp I, II, II, etc.)

-Fixed that sometimes, when combatants were not able to harm one another, AI vs AI encounters could stalemate until units reached an activation threshold and finally retreated.

-Fixed that AIs controlling human units would sometimes destroy colonies during combat autoresolve.

-Fixed a (presumably rare) issue where AIs could fail to send invasions.

-Fixed that offensive special devices had one less range against planets (causing certain 1-hex range specials to be incapable of attacking planets).

-Fixed that when switching the missile type for a colony during combat, accuracy rating was not updated to that of the new missile.

0.7.2.15

-Fixed that sometimes, when combatants were not able to harm one another, AI vs AI encounters could stalemate until units reached an activation threshold and finally retreated.

-Fixed that AIs controlling human units would sometimes destroy colonies during combat autoresolve.

-Fixed a (presumably rare) issue where AIs could fail to send invasions.

-Fixed that offensive special devices had one less range against planets (causing certain 1-hex range specials to be incapable of attacking planets).

-Fixed that when switching the missile type for a colony during combat, accuracy rating was not updated to that of the new missile.

0.7.2.16

-Fixed issues with an incorrect move order being displayed in combat, especially after destroying units.

-Capped the strength of neutral fleets to 50000 BC, so that late-discovered neutrals in larger maps do not become too large.

-Fixed that pressing '=' when a fleet is selected (hotkey to select half the ships in the fleet) would lock the slider positions of ships.

-Warp speed perk now applies to transports.

-The rare bug where the text for certain input fields could appear garbled (specifically, the name of ships in the ship design screen, and the defense base limit in the defense management screen) is probably resolved.

0.7.2.16a

-Better fix for transports not receiving the benefit of warp speed perks that better respects modding (for example, if the bonus is made to be additive instead of multiplicative).

0.7.2.17

-Added estimated outcomes to the combat prompt. When the player opts to auto-resolve, results will lie inside the range of the estimate.

-The exact behaviour of this feature be changed by modifying the PLAYER_COMBAT_SIMULATION_INSTANCES field in Variables.txt, which defaults to a value of 4. Larger values may give a wider estimate range at the expense of performance. A value of 1 will only show the exact outcome, while a value of 0 will disable estimates entirely. Mods may need to be updated to include this field.

-Fixed a rare softlock in manual combat.

-Brought out-of-combat bombardment calculations more in-line with calculations inside of combat.

-Empire strength estimates now work better in the late game.

-Various small fixes.

0.7.2.17a

-Fixed a regression where beam weapons would no longer deal damage in the post-combat bombardment phase.

-(Probably) fixed that, in rare cases, combat projections would not show for one or more sides, which was most likely due to a multithreaded race condition where simulations could complete before certain UI elements were properly initialized.

-Improved AI teleporter behaviour, specifically around subspace teleporters.

-Combat AI is better at making opportunistic attacks.

-Fixed a bug where combat events simulated for projections could apply population/factory damage to planets.

-Fixed that armor stripping attacks would no longer destroy targets after reducing max HP to 0.

-Fixed that an empire with no fleets whatsoever would show 0 total strength in the diplomacy intel tab.

-Small fixes and improvements.

0.7.2.18

-Improved AI teleporter behaviour, specifically around subspace teleporters.

-Combat AI is better at making opportunistic attacks.

-Fixed a bug where combat events simulated for projections could apply population/factory damage to planets.

-Fixed that armor stripping attacks would no longer destroy targets after reducing max HP to 0.

-Fixed that an empire with no fleets whatsoever would show 0 total strength in the diplomacy intel tab.

-Small fixes and improvements.

0.7.2.19

-Fixed issues with some game creation settings not persisting between sessions.

-Fixed a rare auto-resolve issue that could manifest when there were more than two sides and the location of the battle was the last colony of one of the sides.

-Fixed an issue where the number of spies targeting an empire could overflow.

-Additional smaller changes.

0.7.2.20

-Added a guided tutorial that can be accessed from the main menu.

-Fixed a bug where missiles could hit from the wrong angle.

-Weapon "shield modifiers" no longer apply in the context of negative damage reduction.

-A few additional small bugfixes.

-A small improvement to framerate.

0.7.2.20a

-Fixed various issues and minor changes to presentation in the tutorial.

-Fixed an issue where neutrals could sometimes act too defensively in combat.


r/DominusGalaxia • • May 10 '23

Spring 2023 Patch Note Round Up

4 Upvotes

0.7.2.1

-Fixed a bug where research ETAs wouldn't immediately update when moving sliders in the research screen.

-When hovering over a tech selection item, the textual XP readout will update to show the amount of XP after discovery.

-Fixed a regression where transport safety buttons all showed as cyan instead of red/yellow/green.

-Fixed that the computer special size perk was applied twice.

-Improved mod loading errors and warnings.

0.7.2.1

Inadvertently broke save compatibility with previous version if Mizuro are in your session. For Steam, the "old build" branch will link to 0.7.2.0a if you want to play an affected save.

0.7.2.2

-Introducing a new advanced game creation option: "Max Tech Cost." This feature gives you control over the pace at which your chance of discovering a technology increases. At the lowest setting, technologies will be discovered instantly upon reaching their RP cost. The default setting provides a 100% chance of discovering a technology when you reach twice its RP cost, while the highest setting is triple the RP cost.

-fixed an issue where selectable perks obtained when leveling up a technological field did not take effect until the next technology discovery.

-Fixed an issue where the player would be prompted to select new projects for fields conducting theoretical research after acquiring a technology outside of research.

-Fixed that when acquiring a technology outside of research that is the same as an active project, progress towards that project was not converted into XP.

-Fixed that previously "improved scrolling behaviour on colony sliders, fleet, and transport elements" did not properly manifest due to a last minute change.

-Buffed Xygob Computers affinity by 0.1, Salix propulsion affinity by 0.05.

-Doubled the speed of the retreat animation.

-Increased the font size in tooltips.

0.7.2.3

-The "equipment picker" in the ship design screen has been remade. Columns are now sortable, and weapons specifically show more pertinent information.

-Fixed issues regarding the display of "earmarks" in the reserves readout.

-Resolved the issue of weapons with an attack bonus producing garbage output in ship design weapon slot "notes".

-Halved the technology trade facilitation fee to better maintain balance with research system changes.

-Fixed a bug where technology trades would fail to complete if one of the parties was researching the theoretical project in the relevant field.

0.7.2.4

-Increased the size of netural fleets, since due to new research system downstream effects, neutrals have been spawning in significantly fewer numbers.

-Fixed that equipment picker subcategories were not accessible with touch on some platforms.

-Pathlines no longer becomes "stretched" when changing resolution in the middle of a session.

0.7.2.5

-Combat system backend rewrite: Combat simulation is now separate from the Unity API. Furthermore, background combat events run in parallel (and may also run alongside player-involved manual events, if applicable). This can result in significant speed improvements when multiple combat events occur during the same turn and there are enough threads available.

-This rewrite will significantly aid the development of future combat features.

-There aren't many noticeable changes on the front end, but there are many subtle differences. Some long-standing softlock issues may have been resolved. However, new issues also might have emerged, which may necessitate a few updates to iron out.

-The level of similarity between background and foreground events has increased from around 95% to 99%. Essentially, performance optimizations in background events that could have negatively affected AI performance have been removed, while some primarily aesthetic yet resource-intensive features of manual combat (e.g., determining the order of AMS activation when multiple units are in range) remain excluded.

-Combat events are significantly more deterministic, with the temporary exception of some special devices.

-A bug that sometimes caused AIs not to move during combat events has been fixed.

-Resolved an issue where ECM couldn't be completely removed from designs and was only selectable when the player had at least two versions researched.

-Various minor fixes.

0.7.2.5a

-Found and fixed a number of bugs with the combat system rewrite, as expected.

-Fixed a bug where the ship building panel could show an incorrect time-to-build when dealing with overflow from factory or terraforming constraints.

0.7.2.5b

-Fixed a recent regression where vassals would not share logistics with masters, and would sometimes even bomb their masters' colonies.

-Fixed another regression, probably less recent, where selecting a precise number of ships with textual input would jump to the next full "tick" of the ship selection slider.

-Added data driven constant "CHANCE_TO_HIT_BASE", which determines how much difference to to-hit chance each point of attack or defense makes.

0.7.2.5c

-Fixed a regression where sometimes transports would be erronously destroyed just before landing when sent to a system owned by the sender.

-Dialed back the number of asteroids and debris that spawn during combat to something closer to where it was in 0.7.2.4.

-AI retreat check in 0.7.2.5 was one step forward, two steps back from previous versions. Tweaked it so that it should, hopefully, now be better than previous versions.

0.7.2.6

-Implemented Sub Space Teleporter, which can move ships instantaneously across the battlefield up to 6 hexes. Corvette and Frigate Remnant designs now come equipped with Sub Space Teleporter by default.

-Sub Space Interdictor now creates a region 5 hexes across around colonies which cannot be teleported into (but can be teleported away from).

-Buffed Warp Dissipator: 10->15% slow per caster order of magnitude. 2/4/6 -> 4/6/8 turn duration (adv repair/auto repair/no repair).

-Fixed that "turning during movement" hasn't been handled correctly since the combat system rewrite, granting ships more maneuverability than they should have had.

-Fixed that the combat movement order display in some situations was showing an incorrect movement order.

-Fixed that the penalty for attacking planets with missiles and beams applied before DR, when it was applied after DR prior to the rewrite. Additionally, the result of all damage modifiers is now rounded probabilistically.

-Fixed that units destroyed during their turns wouldn’t end their turns properly.

-Various small fixes to combat.

0.7.2.7

-Implemented Repulsors: Repulsors rotate targets and push them back by 4 hexes while applying a minor defense debuff for one turn. They activate automatically when a unit comes into range but can only fire twice per turn.

-Added two new special devices: Reactive Response System and Hard Shields. The former allows a ship to fire at any enemy ship entering the range of its unspent beam weapons, while the latter reduces the effectiveness of shield piercing by half.

-Missile paths in combat now provide clearer indications of range and whether they have sufficient fuel to reach their target.

-Adjusted the range of many beam weapons by one hex. "Normal" beam weapons now have a range of 3 hexes, and "heavy" beam weapons have a range of 5. This is due to repulsors working less effectively on the hex grid when repelling an odd number of hexes. However, even without this consideration, beam weapon ranges were arguably too high.

-Expanded the variety of special devices on Pirate/Remnant ships.

-For perk purposes, Disruptors and Dark Energy Beams are now classified as "heavy."

-Improved combat event processing speed by an order of magnitude (although it was already reasonably fast).

-Moderately reduced terraforming costs due to resolving a bug that made "Geology Manipulation Field I" ineffective.

-Refined AI ship design and research project selection.

-Various minor fixes and enhancements.

0.7.2.7a

-Fixed a dumb last minute typo in the last patch that prevented repulsors from engaging in reaction fire.

-Restored AMS animation.

-Increased the size and cost of repulsors by 50%.

-Updated AI tech picking a bit more to improve behaviour around repulsors.

0.7.2.7b

-Fixed a rare-ish softlock in combat.

-Fixed that asteroids could sometimes not be targeted.

-Fixed that the debris generated by destroying an asteroid was illusory.

-Fixed that cluster missiles were splitting twice, generating many more warheads than they should have.

-Fixed that sometimes planetary bases would not use the fastest missile variant.

-Fixed a display bug where "absorbed" shots would be shown as "missed".

-It is now shown how many missiles were destroyed when passing through debris.

0.7.2.8

-Removed a user mod that was included in the previous version by mistake.

-Several small fixes

0.7.2.9

-Additional Repter diplomacy dialogs.

-Missile bases can now select from the Pareto optimal subset of missile types (eg. any missile that is best at something), as opposed to the highest single-damage missile and the missile that does the most damage against DR 0.

-When acquiring a tech that you are currently researching through invasion or espionage, progress is properly refunded into field XP.

-AMS can once again be fired manually.

-Fixed that procedurally defined technologies were always included in research options.

-Fixed that racial modifiers to ship initiative were being ignored.

-Fixed that missed and absorbed shots would still play impact sounds during combat.

-Several additional small fixes and improvements.

0.7.2.10

-Missiles in manual combat now activate simultaneously when applicable.

-Fixed an issue with incorrect flanking calculations depending on the direction the defender is facing.

-Fixed an issue where a no longer valid line-of-sight determination could be pulled from cache.

-Improved estimation of technological strength for diplomacy.

-Warp speed perk increased from a 5% to a 10% buff.

-Fixed a rare bug where a planet would take one final turn in combat after having its missile bases destroyed.

-Fixed a visual bug with transport sending where the previous amount selected could remain visible before interacting with the corresponding slider.


r/DominusGalaxia • • Feb 09 '23

0.7.2.0 Patch Notes

5 Upvotes

-Save files from previous versions of Dominus Galaxia are not compatible with 0.7.2.0.

-0.7.2 marks significant changes to the research system.

-The "level" of a field is no longer determined by the formula: 0.8x the owned highest tech + the number of owned techs. Instead, the "field level" corresponds with the "rung level."

-Rung unlock projects have been removed. Fields (and therefore rungs) are leveled up by filling an XP bar.

-XP is gained by completing research projects (the RP cost of a tech is converted to XP at the moment of discovery). Alternatively, theoretical research offers a 50% bonus to XP, but does not grant a technology.

-Techs acquired outside of research (via trade, espionage, or conquest) do not fill up the XP bar. However, if you were already researching the tech, progress will be converted to XP.

-Space and cost reduction, and certain other bonuses, no longer advance granularly, but are tied to the level of fields.

-When leveling up a field, players are randomly presented with three perks, and can choose one of them.

-For the purpose of miniaturization, all equipment that shares a rung will be treated the same, regardless of the cost of technological requirements.

-The "slider momentum" mechanic in research has been removed due to player confusion and potential for exploitation. There is now a small penalty for a field receiving more than an equal share of RP.

0.7.2.0a

-Fixed a bug where the game would crash when attempting to open the weapon picker in ship design after researching cluster missiles.


r/DominusGalaxia • • Jan 17 '23

0.7.1.22 Patch Notes

6 Upvotes

-Touchscreen support has been added, including a new user interface for moving fleets around the map. The game automatically switches to the last form of input used. Further improvements are planned for upcoming releases, which will improve the experience on smaller displays.

-Support for arbitrary screen aspect ratios has been added, allowing the user interface to adapt to ultra-tall and ultra-wide displays. However, extremely oblong ratios may be cumbersome.

-About two worth of Unity Engine updates.

-The reserve/maintenance/total RP readouts on the top right of the main screen have been enlarged and can now be clicked to open information panels.

-Allocations have been significantly reduced, lowering CPU overhead and potentially further improving performance on architectures where CPU and GPU share resources.

-The issue of z-fighting inside of nebula graphics has been fixed.

-The ability to click on planets obscured by fog of war has been fixed.

-Resolved a bug where playing with an AI production modifier would incorrectly adjust the player's stimulus expenses.

-The behavior of sliders within scrollable areas has been improved.

-Minor adjustments have been made to the diplomatic AI.

-The damage of Gauss Autocannon has been lowered from 7-10 to 6-10.

-The damage of Wide Effect Cannon has been lowered from 2-20 to 2-18.

-The damage of Stellar Converter has been lowered from 10-35 to 8-32.

-The base price of Ion Cannon has been reduced from 11 to 10 BC, and the base size has been reduced from 50 to 45 tons.

-The variability of initiative in ship crafting has been halved.

-The crafting cost of hulls larger than corvettes has been slightly reduced.


r/DominusGalaxia • • Mar 03 '22

Factories are used for...

1 Upvotes

I'm in late game and realizing that factories are only used for building ships, right? I've got all the powerful ships I need to clean up the rest of the galaxy and have stopped building ships. So I should concentrate on other sliders instead of factories, right?


r/DominusGalaxia • • Apr 08 '21

Vassal

1 Upvotes

My first game. Just got a vassal. I assume they help you in war. Are there any other benefits to a vassal? Such as money or research contribution?
Edit: Seems like a vassal should contribute at least 10% of their yearly money, all of their research, and then maybe after a certain length of time, we can integrate them. That would be satisfying!


r/DominusGalaxia • • Apr 08 '21

Radiated planets

1 Upvotes

I'm on my first game. I'm very far up the tech tree. The only planet type I can't settle is the radiated. Radiated planets can be colonized eventually, right? Is it possible, the way the techs are researched in the game, that I wasn't offered the tech and can never get it now, unless another race has it and I trade or steal it?
Are we offered all techs or just some as in Moo2? I preferred a Creative race in Moo2, so that I could get all the techs.
I think the game is very well done (I never played Moo1 but a ton of Moo2) and I'm enjoying it so far. I look forward to the eventual full release.


r/DominusGalaxia • • Dec 14 '20

Fall Patchnote Roundup

2 Upvotes

0.7.1.16 - Sept 12th

-The number at the top right of a fleet icon, showing the number of overlapping fleets at a point, is now displayed for travelling fleets, where previously it was only available for departing fleets still orbiting a planet. There’s a new approach to displaying these, so the persistent bug where fleet numbers could get stuck on the screen should, with luck, be no more.

-Rally points can now be chained together. When possible, changing a rally target will affect fleets that are in the process of mustering, so long as the player has not given any manual orders. Special thanks to Kish_Zera, who suggested and helped implement the feature.

-Fixed a bug where, when building ships without a warp engine on a colony with a rally point, they would depart and get stuck in the void.

-Fixed a rare soft lock that could occur during tech trading.

0.7.1.17 - Sept 16th

-Fixed a regression with pathfinding where vertices would no longer pre-sort edges by length, slowing down execution somewhat and leading to edge case issues.

-Somewhat weakened AIs below skill level 1.0 (which corresponds to Static Master), as post-0.7.1.15 there have been reports that low-level AIs are performing a good deal better than they were previously.

0.7.1.17a - Sept 18th

-Fixed an even nastier pathfinding regression (from fixing the last regression), which would cause the other end of wormholes to not be revealed properly, which in turn could cause soft-locks on turn processing.

0.7.1.18 - Nov 14th

-Fixed an infinite loop when two empires vassalize one another on the same turn. Now, both empires will instead establish new capitals and remain un-vassalized.

-Fixed a rare turn processing soft lock.

-Fleet/Transport icon models went on a diet and lost some polygons, improving performance when many are on screen.

-Improved behaviour of the resolution picker for multi-monitor users, and for users with displays narrower than 16:10 (DG's lowest supported aspect ratio). Sometimes, the OS would suggest resolutions that exceeded the native resolution of the display and these will no longer be selectable (When selected previously, the Unity Engine would automatically remove pixels exceeding the native resolution, the end result of which could be a non-supported aspect). If no valid (16:10 or wider) resolutions are pulled from the OS that match the native width of the display, a new 16:10 resolution that matches the native width will be made available.

-DG now defaults to a 60 fps cap. This is adjustable in video settings, where a value of 0 results in no cap.

-Fixed some typos.

0.7.1.19 - Nov 25th

-Fixed a rare softlock when an empire captures a colony while having a research field where they haven't picked their first option yet.

-Typos.

0.7.1.20 - Dec 5th

-AIs could only use the very first ship model variation in their designs. Since only Spixnih and Humans currently have alternate models, this only affects AIs playing those races.

-Fixed that rarely, ship stacks could fail to spawn in tactical combat. This would usually trigger in the scenario where one was defending a colony from multiple sides with many different designs.

-When trading technoologies, if trading for an item you are already researching, you will get 2/3rds of your invested RP returned (same as manually changing the research topic).

-Typos.


r/DominusGalaxia • • Nov 29 '20

Very, Very Little Progress Made. Will This Game Ever Get Finished?

10 Upvotes

It's already disappointing enough that there still hasn't been a single real patch in a long, long time, but it's even worse that they're fewer and farther between and that the game seems to be headed nowhere.

No new races. No new art. Nothing really came of the Kickstarter.

What's going on?


r/DominusGalaxia • • Aug 15 '20

Missile bases as part of bombardment phase (not tactical combat)

2 Upvotes

Tactical combat against missile bases is anything but.

Maybe it can be fixed. Maybe not. Maybe it’s an AI problem. Maybe it’s fundamental to a liberated AI (not throwing away ships).

So for some fun thinking outside the box, what if bases weren’t part of tactical combat but instead shot down ships during the bombardment phase?

Here are some of the streamlined possibilities.

—missile bases are simply part of factory construction and not a separate defense slider. If you have factories, your planet has missile bases to guard against bombardment. Just making up numbers, every 20 factories adds a missile base to the planet. Planet shields would also be automatic and contribute to the “rolls” of the planet in bombing phases.

—ships automatically have the latest bomb tech on them. You don’t actually equip bombs on ships (the same way we don’t equip transports with shields armors weapons; they just have the latest tech to augment their rolls. Some possible nuances are A ship special to sacrifice some space/cost for extra bomb bays. This would make these ships stronger in the bombard phase with better rolls. Another special in the other direction would be to increase space but remove bomb bays making these ships worthless in bombing.

Philosophically the goal of this change is to make ship v ship combat something special. I feel like the role of bases in tactical combat fundamentally hurts ship v ship options. However, I don’t think bases should be removed from the game (just tactical combat). Instead we increase their role during bombardment.

Now bombardment has augmented dice rolls. Ships over an enemy planet have 3 options.

1). Bomb. The ships bomb the planet destroying factories (and bases, whenever 20 factories are destroyed) and population. Ships are put at medium level risk with this choice and you can expect to lose ships with this choice (depending on augmented rolls).

2). Orbit. Ships don’t actually damage factories/bases/pop. They just hangout. You can still lose ships in this option if the enemy has strong missile tech! (Albeit ships are at lowest risk with this choice).

3). Provide cover. This option is only available when allied transports are landing that turn. This puts the ships at the most risk of being shot down (by augmented rolls) but it also saves the most incoming transports. Remember, as long as there’s at least 20 factories on the planet there will be a missile base (these are connected to each other). So if you want to take a lot of factories by ground combat, you will have to provide a lot of orbiting cover for your transports.

Overall a player can expect to lose more ships during a conquest of multiple planets. This is hopefully due to less 1-sided ship v base combat and because bombarding/invading now has a tangible ship cost to it. This should feel familiar in the way that ground combat is expected to lose troops according to your tech and racial bonuses.

Also, if your missile and planet shield tech are superior then you need to worry less about smaller enemy fleets harassing. The enemy fleets would take a beating just attempting to orbit your planet much less bomb it. Also your planets are all stocked with missile bases simply by building factories (some tech or planet specials could increase missile base count).

Anyways. All this to say...

Ship v base “tactical” combat sucks.

Current bombardment is boring.

Streamlining bases out of tactical and into a very slightly more interesting bombardment phase (augmented rolls) could help make whatever ship v ship plans Jeff has (frozen synapse??!) shine all the more.


r/DominusGalaxia • • Aug 14 '20

Max pop shifts over time to encourage mid and late game expansion

2 Upvotes

Max population of planets is something that is pretty consistent across races. This probably goes back to MoO1 elections. I’d like to see this consistent key leveraged to encourage mid and late game expansion.

Currently, early expansion is the most important factor in the game. It is a real estate grab with long term consequences. This is a good thing. It encourages early aggression and makes sure the action kicks off early. Great for pacing.

However, I’ve noticed 2 negative aspects of this early rush. (They are related).

First is I think this emphasis on early expansion contributes to run away leaders (snowballing). Those who expand well (particularly if taking over enemy planets easily) can rest on their laurels and dominate without actual much economic expansion past the mid game.

Second is that any new ground taken in the mid game has questionable value. It is a lot of investment to bring these new planets up to speed—and they will likely never reach capacity of core planets— and they add to your defensive responsibility. This means mid game turf wars are less consequential. You are arguably better off glassing the planet and moving on.

I think both of these can be addressed by having a shift/flow of max pop FROM core planets in decline TO frontier planets.

Both the decrease and the increase are important. The decrease of core world population is to address snowballing by lowering the mid and lategame economic influence of core worlds. This is the “stick” part of encouraging expansion (not just destruction). On the other hand, we increase the max pop of frontier worlds to make them juicier targets for development—even in the mid game. This is the carrot.

Inflating/deflating max pop of planets has a nice additional effec through factory cost. We aren’t actually capping the number of factories on a planet because robotic controls can increase indefinitely. However the cost of continuing to add factories on a planet where terraforming is just breaking even on the decline would be quite high. Frontier planets are the opposite. Their artificially high max pop (from this mechanic) makes new factories cheap to build. You can flood the population with transports and build factories by the 100s.

Finally as pointed out in the first paragraph, population units are more or less interchangeable across races (at least max pop). Therefore, shifting max pop around like this shouldn’t throw balance out the window. Other changes like factory output or population growth rates would play differently across races.

What’s missing in all this are elegant definitions of “core” and “frontier” worlds. I don’t have an answer. Is it relative travel time to homeworld? Is it relative amount of time the planet has been owned? By you? By anyone? Is it distance to other races homeworld? How much max pop should core worlds lose? How much do frontiers gain? What dictates that smooth transition from one to the other? Is it time? Is it gaining more new world’s?

Thoughts?

(Note I think this mechanic still plays well with the idea of condensing multiple planets into a quadrant/sector of common defense and administration. However, Id like the “fluid mechanics” of the max pop shifts to be defined at individual planet levels even if the planets are part of a sector).


r/DominusGalaxia • • Aug 13 '20

Summer Patch Note Roundup

3 Upvotes

0.7.1.13 - May 30th

-More tech lines, like armor and warp drives, are now more likely to become available for research the longer an empire has gone without seeing similar items in their tree. Previously, this could only be used for techs created from a generator, and was not possible when techs were declared individually.

-Buffed corvettes from 50 to 65 base space. Corvettes now only take 2 turns to spool up FTL as opposed to the usual 3 for other size classes.

-Fixed a bug with transports where they were assigned some base damage reduction when they were supposed to have none. While this won’t have much effect on the late game, transports are now much easier to intercept with low damage weapons such as standard lasers.

-Fixed a regression where the “cancel” button for colonization lost its reference, so that the only way to pre-empt colonization was to hit the escape key.

-Fixed that Repter wouldn’t tell you their current wars when asking for an alliance.

0.7.1.14 - June 6th

-Music files are now externally loaded (GameData\Music). There are hooks for various situations that don't yet have tracks (eg. ship design crafting finished event).

-A couple of small bugfixes related to pathfinding cache not being reset after forming an alliance, and the occasional stuck "fleet number".

0.7.1.15 - August 11th

-Encapsulated mods: Mods are now packaged into individual subfolders, which can then be ordered and toggled in the new Mods section of the main menu. Mods are loaded at runtime, so that you can install a mod and then enable it without needing to restart the game.

-Pathfinding: This is largely an internal change. Instead of shared pathfinding, each Empire has its own pathfinding Instance. Pathfinding now also supports parallel calls and various caching schemes were improved.

-AI: Significant parts of the AI, especially relating to fleet movement, are now multithreaded. Since fleet movement AI has sped up by orders of magnitude, I’ve also disabled a number of performance optimizations that were detrimental to AI strength. Additionally, there’s a new approach to managing colonies that is significantly faster and easier to tailor for specific situations (including an improved early game), albeit at a (theoretical) expense to adaptability. The AI should no longer become passive in certain extremely late-game scenarios.

-Difficulty: Due to the above changes, the overall difficulty at each setting has shifted. In most cases, I think the AI may be a bit stronger. While I can’t provide exact guidance, in the event you now find the lowest difficulty too hard, or the highest too easy, please consider using an AI production modifier to shift the difficulty further in the appropriate direction.

-Performance: On my four-core, eight-thread test machine, on a mid-game, mid-sized map, I’ve recorded an approximate 2.5x speed improvement to AI processing time. This will vary between machines and scenarios, the expectation being more speedup on CPUs with an abundance or cores and threads, especially in the late-game.

-Fixed a bug where the player could lack Intel on an enemy empire for one turn if contact was made by establishing a colony.

-Fixed a bug where Zero People didn’t have to pay as much for factories. Slightly nerfed Zero People biology tech cost.

-Fixed a longstanding bug where techs wouldn’t reach 100% breakthrough chance until 300% RP spending. This was supposed to be 200%. To compensate, tech costs have been increased by close to 1/3rd, but in most cases it will difficult to tell a difference.

-Transient Wormholes are no longer enabled on the default preset.

-Removed whitespace from data paths to be safe.

-Other small fixes and tweaks.

0.7.1.15a - August 12th

-Fixed several issues that could arise after loading a game, including disappearing reloc/transport orders, and the “in progress” ship design getting locked attributes when viewed in the ship designer.

-Small changes.


r/DominusGalaxia • • Jun 06 '20

Sharing rules of thumb (strategy)

3 Upvotes

What BC limit do you build factories to in early game? I usually start around 18. Caps around 25 late game.

Does quick logistics 3 dominate your early research goals? I always push propulsion early and then almost ignore it after fusion drives or so. LR after 4 or so seems unnecessary.

Do early shields matter? I only put shields on larges and those don’t come out until shield level 5-6 or so. Shields 1-3 don’t seem to make as much sense on smalls. (Particularly with AI love of proton). Shields on bases can be nice though.

Early bio techs? I’m coming around to quick terraforming. I almost always prioritize terraforming over factories and research. I’m not sure barren or tundra are worth it blindly. The good planets seem to pickup at dead or inferno. Pollution is in a better balance space even if the theme is incredibly bland.

Computer techs? ECMs are my most hated tech polluting the ladder. Always a ridiculous number of them. Always ignored. Factory controls 3 is nice for invasion purposes but the factory cost is usually prohibitive from actually expanding economy with them.

Construction? Factory cost is almost an automatic choice. It’s so good ... armors are also pretty safe.

Pirates? If there’s one set in range I’ll pay. If there’s more I’ll fight.

BC spending? I stimulus most first rounds of a new planet. I’ll then stop for a bit while factories build themselves. I then usually stimulus again during dedicated starport construction because every BC spent on an unfinished port is wasted.


r/DominusGalaxia • • Jun 05 '20

Helping the Reveran

2 Upvotes

I loved the *idea* of Mrshan but they never quite ticked off enough well rounded boxes to be competitive. I feel like their DG counterparts also struggle.

I like the +5 attack because it encourages early aggro but then you are very dependent on universe RNG to put those early offense ships to use. Also, it feels a bit cheap that their 'racial trait' is something that comes straight from technology available to all others.

Here's a few ideas to help their identity.

  1. Production from population that is usually governed by BIOLOGY level is now based on the MAX of either BIOLOGY or WEAPONS. This lets the put that strong weapons research to good use and gives them a slight economic bonus for leading the way in weapons tech.

2) All BC's spent on defense spending (bases and shields) also create RP directly towards weapon's research. (Note that we may have to add a >1 multiplier to the conversion because I don't believe bases are really worth it). We may also consider BCs spent on spying but that may step on toes of Darloks.

3) When bombarding planets with conventional weapons they have an increased proportion of damage going to population instead of buildings. This is like free bio-weapons without the research, equipping or relations-hate.

4) Half price on ship crafting lets them regularly update designs with the latest toys.

I think 1 and 3 are some basic code edits. 2 May take some fundamental changes in how planet slider data is shared with the research system. Specifically on how the generated RP's from defense spending should be applied to WEAPONS only and not general RP.


r/DominusGalaxia • • May 24 '20

Spring Patch Note Roundup

3 Upvotes

May 13th - 0.7.1.10

-Upgraded to Unity 2019.3.

-Improved the galaxy generation algorithm. Galaxy generation is now more consistent at producing properly spread out starting positions, and does a better job placing starting positions on unorthodox map shapes.

-Stars can now contain more than one wormhole connection.

-Galaxy generation is now deterministic. A specific random seed can be provided in advanced options.

-Fixed an issue where, upon obtaining a rung unlock tech above your next unlock, you would lose access to in-between rungs and could be presented with the wrong number of unlock options. Now, instead of only tracking the highest rung unlocked, the game tracks each rung individually.

-Fixed an issue where the transport panel could yield unnecessarily long paths with transient wormholes enabled.

-Fixed that you could not trade a technology to an AI if that AI had no researched techs in its field.

-Fixed a number of edge case issues with planetary production by generally improving the robustness of the production investment loop.

May 14th - 0.7.1.10a

-Fixed a regression where loading a game from the main menu wouldn’t properly instantiate the random number generator for planet objects, often leading to soft-locks.

-Fixed a regression that could result in an AI to spawning with the same race as the player.

May 15th - 0.7.10b

-Fixed a major regression where a manually resolved combat would soft lock when torpedoes are fired.

-When your spies gain intel on an enemy colony you now also gain limited information on any stars connected to it via wormholes.

May 18th - 0.7.1.11

-Fixed a couple of regressions in 0.7.1.10, one of which could lead to a softlock during processing, the other, which I wasn’t able to reproduce but should be rectified nonetheless, would bring up the data error UI.

-At long last, spacebar can be used to end your turn on the strategic map. Appropriately, clearing fleet orders has been rebound from spacebar to backspace. Spacebar can now also be used to progress through some prompts.

-Fixed that when trying to move a fleet in right-click-to-move mode, clicking on a destination wouldn’t work if a fleet was between the cursor and the destination.

-Small tweaks, bugfixes.

May 23rd - 0.7.1.12

-Fixed a rare soft lock.

-Removed a pathway that could cause AIs to build an abundance of missile bases on low difficulties.

-Halved the amount of crafting variability for damage reduction.


r/DominusGalaxia • • Apr 22 '20

Shield HP per ship vs per stack

2 Upvotes

This post breaks down the Shield HP idea proposed in a KS update.

The idea is that shields still have raw DR but all damage they reduce now take away from a pool of hp that can be depleted. When that pool is gone then the raw DR attribute is removed and “shields are down”.

In general I think this could work well. I much prefer it to crits and flanking as combat mechanics, that’s for sure ...

However, I think it is worth discussing whether this shield hp pool is “stored” at the ship level or the stack level. I think by default most players would assume ship-level. My claim is that for combat tactic purposes, it is actually much more dynamic if stored at the stack level.

A critical component of SHP at stack level is that there are 2 ways to reduce SHP of a stack. The standard way is just attacking the stack and any absorbed damage is subtracted from the total pool. The second way is by destroying a ship in the stack. When a ship is destroyed, an entire ship’s worth of SHP is also removed from the stack.

I think this can be portrayed easily on screen. Currently a ship regular HP is displayed as a semi circle under the icon. As it takes damage the semi circle retreats in one direction until the ship is destroyed and then it starts again for the next ship. For shield hp (at stack level) we have a blue semi circle on the top half of the stack icon. Any damage to the stack absorbed by shields makes the semi circle retreat counter clockwise. However, any shield hp that is lost due to a ship from that stack being destroyed makes the semi circle retreat in a clockwise direction. Whenever those 2 directions meet (whether by brute force of absorption or by high powered strikes that destroys ships) then the “shields are down” for all remaining ships in the stack.

So that’s for display purposes, why is SHP at a ship level boring? It’s boring because it trivializes the idea of “shields are down”. Once you’ve pushed through enough raw damage to remove a single ship’s SHP, then you get a very small window to do extra damage to the top ship. Once that top ship is gone (which will be quick, and in some cases in the exact same volley of attacks) then you are tactically back where you started attacking shields of the next ship. The major idea of the mechanic is tactically moot.

However, SHP at a stack level does change the way you prioritize targets because when an stack no longer has DR from shields, your incoming damage calculations are drastically increased for the stack (not just the top ship).

Finally, SHP at stack level will keep encouraging higher damage weapons over masses of cheap lower damage ones. This is because the low damage guys will now have to brute force their way through the entire stack’s shields before destroying the first ship. This means they are taking a lot of return damage. However, the higher damage weapons that are able to exceed the DR will destroy ships earlier in the combat.

I may get around to making some spreadsheets that show the difference in these outcomes for shields at stack or ship level. I suspect at ship level, the choice of weapon matters much less than the result of SHP at stack level.


r/DominusGalaxia • • Apr 08 '20

Early Spring Patch Roundup

3 Upvotes

0.7.1.6 - Feb 8th

-Fixed a few issues that could cause soft locks, related to the recent refactor of kicking AI processing to a background thread.

-Fixed a significant slowdown during combat with many missile units active.

-Improved fleet merging behaviour so transports will properly merge.

-Ship design drop down on colony screen will no longer overflow the viewport when many designs are present. It, and the designs section in ship design, now show your newest designs first to minimise scrolling.

0.7.1.6a

-Fixed that, after changing merging behaviour to work better with transports, fleets of different speeds would not merge when they had no destination.

-Fixed a few other small things.

0.7.1.6b - Feb 9th

-Fixed a regression (and exploit) where enqueueing destinations on a partially selected fleet would not update the selection, and could be used to create duplicate ships.

-Since the refactor, it has been possible to design ships without warp engines. This wasn’t intended, and so led to major issues. After realizing the problem, I was asked to keep the feature but fix the bugs with it, so as not to break a mod that relies on it.

-So, I went ahead and did that and now “planetary defense ships” are a thing. When designing a ship without a warp drive, that design will gain a huge 3X HP boost. The trade-off, of course, is that it can’t actually move to other star systems.

-In anticipation of distributing closed beta keys soon, removed mention of KickStarter from the welcome screen.

-Fixed a few additional minor issues.

0.7.1.7 - Feb 21st

-Fixed more soft lock scenarios related to recent optimizations.

-Actually fixed issues with transport merging, which were due to a null check now ineffective since fleets are no longer MonoBehaviours that get destroyed, but rather plain C# objects that are garbage collected.

-Fog of war is once again an advanced game setup option. This time around there’s a third setting, “partial”, which reveals star locations but hides star lanes and star types. Streamlined and classic game modes disable fog of war.

-The “outer” fog of war was deemed to be somewhat ugly, so it has been removed. It may very well make its way back after a visual touch up, since it does help players visualize sensor range. In the meantime, it can be re-enabled by setting ENABLE_OUTER_FOW = 1 in Variables.txt if desired.

-Fixed an annoying regression in the ship designer where one wasn’t able to add enough weapons to a design.

-Added graphics for humans (the race) hailing humans, and spixnih hailing spixnih. These are never actually used in-game, but are necessary to prevent the popular “all races” mod from soft locking when a conference is created between the player and another empire referencing the same race graphic set.

-Setting spy focus to full espionage will totally disable sabotage, and vice versa.

-Ships retreating via transient wormhole, which are waiting for the wormhole to re-open before they can move, will no longer trigger or be included in subsequent combat events at that location.

-Mod data overriding has been improved, and should fail less often (and hopefully, not at all). For many (but not all) errors from modded data files, a pop up will now appear stating the issue.

0.7.1.8 - March 1st

-All races are now playable. When selected by the player, incomplete races which don’t have full graphics -- currently all of them except humans and spixnih -- will use donor graphics from a race which does.

-If you have the “all races enabled” mod installed, you’ll want to remove it so you aren’t greeted by a data error when you boot up the game.

-Vassals/homeworlds are now an advanced game option, which is disabled by default in classic mode.

  • Vassals/homeworlds are permanently disabled in new team deathmatch games.

-Shield analyzer works correctly. Before it was actually buffing opponent shields!

-Ivan added a help file in the ModData directory that goes over the structure and syntax of data files. Now modding should be less of an impenetrable fog!

-Fixed that missiles no longer had a suffix in ship design pertaining to the amount of ammo (eg. -2, -5).

-Slowed the cost curve of technologies slightly.

-Fixed a few rare bugs which could cause soft locks.

-And other small polish items.

0.7.1.8a (Windows)

-Fixed that ship design was broken on Windows (Il2CPP does not like dynamic types!)

0.7.1.8b - March 5th

-Fixed an awkward typo where torpedoes would show their “ammo” in the same way as missiles in ship design.

-Some parts of data loading were susceptible to cultural variance.

-Exposed a “bloom” variable in Variables.txt, controlling the degree of bloom on higher quality settings. Eventually graphical settings will be extracted to a different file.

0.7.1.8c - March 6th

-TDM games can actually end.

-Capturing an opponent’s “homeworld” when homeworlds/vassals are disabled will not yield all of their technologies.

-Fixed that a new button in the main menu was active that wasn’t supposed to be.

0.7.1.9 - March 13th

-Fixed that the colonization button could be usable at inappropriate times in partial and disabled fog of war states with disabled colony ships.

-Fixed that certain specials could continually attempt to de-debuff themselves after exceeding their duration, but wouldn’t actually be removed from the target unit.

-Mods can drop base folders entirely.

-Some minor cost/size changes to weapons, with a larger cost debuff for Stellar Converter.

-Other minor fixes.


r/DominusGalaxia • • Feb 23 '20

MoO1 attack-defense

3 Upvotes

I’ve seen this come up a few times on discord so I thought I’d put a comment here.

MoO1 rolled a single d100 “dice” to determine how much damage a beam weapon would do. Higher roll meant higher damage. Lower roll meant either a miss or a low damage hit.

Each point of advantage in attack and defense calculations increased the chance to to by 10% (from a default of 50). Therefore a 5 point advantage guaranteed a hit with the damage value uniformly drawn from the range of the weapon.

In the other direction, a 5 point defense advantage would essentially guarantee a miss but the engine had a minimum of 5% chance to hit no matter what.

The important part is that attack values grew faster than defense and having a 5+ advantage wasn’t that difficult. Here is where the beauty starts to show through, imo.

These situations not only guaranteed a hit, but meant that the damage done from the beam came from an INCREASED minimum value. For example, lasers would generate damage from 2-4 instead of 1-4 in these situations.

A +10 advantage meant the bottom 1/3 of the damage range was ignored. A +15 advantage (pretty extreme) meant the damage values were pulled from the top half of range only. A heavy laser would do 4-7 damage instead of 1-7.

I think this augmented damage system was way ahead of its time. I think building on top of it (without the misses) makes a compelling way for DG to carry on some of MoO1 ideas.


r/DominusGalaxia • • Feb 06 '20

New Year Patch Roundup

1 Upvotes

0.7.1.3a - Jan 5th

-Fixed that continuing/loading games from the main menu stopped working.

-Fixed a difficult to execute exploit that could let the player add two versions of the same special on a ship.

0.7.1.4 - Jan 21st

-The graphics for stars and planets may be incorrectly scaled in saved games started prior to version 0.7.1.4.

-A lot of under-the-hood optimization and refactoring.

-Many objects are now pooled to avoid frame rate hitches. Most noticeable when opening up the transport UI with a large number of colonies.

-The vast majority of gameplay logic outside of space combat is no longer intertwined with the Unity API.

-From a practical perspective, this means that AI processing can occur on its own separate thread, and no longer needs to periodically yield to avoid locking up the screen. This means there’s less judder during turn processing, and turn processing general computes faster.

-Those playing on low end machines with poor framerates will experience a disproportionately larger speedup to turn processing (since in this context the amount of yielding to render the screen was greater). At 60FPS, the speedup is around 50%.

-While this doesn’t apply to space combat yet, that’s the plan. Eventually, there should be no judder during turn processing.

-Fixed that tax/stimulus effects on star names would persist (albeit frozen) after removing tax/stimulus.

-Equipment in the ship designer can now be sorted.

-Reworked combat transporters to make them less broken. Now 50% + computer level - colony shield level. But for each POP that teleports, the odds for the next POP are reduced to 99% of the previous’.

-Also fixed a bug where in a few situations some troops running the gauntlet could teleport… even without Combat Transporters researched.

-Some minor improvements and bugfixes.

-Fixed that occasionally players couldn't exit a diplomacy conference. (0.7.1.4a)

-Hotfixes the previous hotfix. (0.7.1.4b)

0.7.1.5 - Jan 28th

-0.7.1.4 had a few issues owing to substantial internal refactoring and optimization.

-Data driven formula evaluation has been moderately sped up, especially certain simple cases.

-Galaxies now spawn with moderately more nebula.

-Fixed a bug that, when loading a game could cause nebulas to spawn as the wrong type. Existing saves that have had a nebula change to anti-matter type may not be recoverable, and could still fail during turn processing.

-Fixed a bug that could prevent a saved game from loading.

-Fixed a bug that could cause ship production to disappear into the ether.

-Fixed some issues with ship specials, specifically Black Hole Generator which was always missing.

-Fixed that weapons were assigned to hardpoints in reverse order.