Author Topic: C# Aurora Changes List  (Read 35952 times)

0 Members and 3 Guests are viewing this topic.

Offline Steve Walmsley

  • Moderator
  • Admiral of the Fleet
  • *****
  • Posts: 6659
  • Thanked: 1055 times
    • View Profile
    • http://www.starfireassistant.com
Re: C# Aurora Changes List
« Reply #45 on: September 05, 2017, 06:58:38 PM »
Academy Commandants

Commanders can be assigned as an Academy Commandant on any population with at least one military academy. Any type of commander can be assigned with the following restrictions:

1) A civilian administrator must have an Admin Rating equal or greater than the number of military academies at the population
2) A scientist must have a Research Administration rating (new bonus for C# which is the max number of labs) at least five times the number of military academies at the population
3) A naval or ground forces officer must have a rank (with 1 being the lowest rank) at least equal to the number of military academies

The normal distribution of new commander types from the academy is 60% Naval, 25% ground, 8% Admin, 7% Scientist. While a Commandant is assigned, a check is made to see if an commander of the same type as the Commandant is generated. If the check fails, the normal distribution is followed. The chance is 14% for a Scientist Commandant to generate a Scientist, 16% for an Administrator Commandant to generate an Administrator, 40% for a Ground Forces Commandant to generate a ground forces officer and 80% for a Naval Commandant to generate a naval officer.

When a new commander is generated, a check is made to see which bonuses he receives. If the Commandant has at least 20% in any percentage-based bonus or 150 for crew training / ground unit training, all commanders graduating from the academy at that population will take two rolls for each qualifying bonus, and use the higher of the two results. If the Commandant is a scientist, there is a 25% chance any scientist from that academy will have the same research specialisation. If that check fails, the research specialisation will be chosen randomly (as normal).

This new rule should allow specialisation of academies on different worlds. Don't forget that you can set up a military academy on any colony, not just those with a population.
 
The following users thanked this post: Ayeshteni, Noble713, DIT_grue, Tristitan, serger, Steven Wargames, Rye123, Detros

Offline Steve Walmsley

  • Moderator
  • Admiral of the Fleet
  • *****
  • Posts: 6659
  • Thanked: 1055 times
    • View Profile
    • http://www.starfireassistant.com
Re: C# Aurora Changes List
« Reply #46 on: September 17, 2017, 09:30:13 AM »
Ordnance Transfer Mechanics

In C# Aurora, transferring ordnance is no longer instant and ships without specialised equipment cannot exchange ordnance in space. A ship can only receive ordnance at a Spaceport, an Ordnance Transfer Station, a ship with a Ordnance Transfer System, a base with a Ordnance Transfer Hub or in a military hangar bay.

A new technology line - Ordnance Transfer Systems - provides the basis of the rate of ordnance transfer and allows ships to mount systems to transfer ordnance to or from other ships. The baseline system (Ordnance Transfer System: 40 MSP per Hour) sets the racial ordnance transfer rate at 40 MSP per hour and allows the use of the first ship-mounted Ordnance Transfer System. There are ten further steps in the tech progression with the highest tech system allowing ordnance transfer at 400 MSP per hour.

Spaceports, Ordnance Transfer Stations or Ordnance Transfer Hubs will always use the highest tech ordnance transfer rate and can transfer ordnance to or from an unlimited number of ships simultaneously. However, the ships involved must be stationary. Hangar Bays also use the highest tech ordnance transfer rate (mainly to avoid multiple hangar bay types).

Spaceports have increased in cost to 3600 BP but can now be moved by freighters. They are equal to four research facilities for transport purposes (or 80 factories). They retain their existing bonuses to loading and unloading cargo.

Ordnance Transfer Stations are a new installation with a cost of 1200 BP. They do not require workers and can be moved by freighters. They have a transport size equal to 10 factories. Essentially, they are a cut-down version of a spaceport intended to facilitate ordnance transfer in forward areas, transferring ordnance between the surface of a planet and ships in orbit. They have no bonuses for loading or unloading cargo.

An Ordnance Transfer Hub can be mounted on a ship. It is a commercial system with a research cost of 10,000 RP, build cost of 2400 BP and a size of 100,000 tons. In practical terms, this is likely to form part of a large, deep-space station, due to the size and cost, rather than being deployed on ammunition colliers that will accompany fleets.

A Ordnance Transfer System is 500 tons and has a cost ranging from 20 BP to 200 BP, depending on the tech level. A ship with an Ordnance Transfer System can transfer ordnance to or from a single ship at once, so it will take some time to replenish a whole fleet, although this will improve with higher technology. At the early tech levels, the Ordnance Transfer System can only be used if both ships (collier and target ship) are both stationary. Underway Replenishment allows the transfer to take place while both ships are in the same fleet and underway. Priorities can be set for the ordnance transfer order when multiple ships are involved. The first Underway Replenishment tech allows ordnance transfer at 20% of the normal rate (2500 RP), rising to 100% with the highest tech (40,000 RP).

Ordnance transfer order types will be adjusted to deal with the new requirements (which I will list in a separate post). Ordnance will be transferred during each movement increment as time passes until the target ship has full magazines.
 
The following users thanked this post: Bremen, sublight, 83athom, Tristitan, serger, xhunterx, Rye123

Offline Steve Walmsley

  • Moderator
  • Admiral of the Fleet
  • *****
  • Posts: 6659
  • Thanked: 1055 times
    • View Profile
    • http://www.starfireassistant.com
Re: C# Aurora Changes List
« Reply #47 on: September 17, 2017, 12:12:11 PM »
 
The following users thanked this post: waresky, MarcAFK, Alfapiomega, Tristitan, Rye123

Offline Steve Walmsley

  • Moderator
  • Admiral of the Fleet
  • *****
  • Posts: 6659
  • Thanked: 1055 times
    • View Profile
    • http://www.starfireassistant.com
Re: C# Aurora Changes List
« Reply #48 on: September 23, 2017, 05:29:39 AM »
Logistics and Ground Combat Research

Due to the increase in Logistics techs for C# Aurora and the planned revamp of ground combat design, the Logistics / Ground Combat research field will be split into two separate fields. There are now nine research fields in total.
 
The following users thanked this post: MagusXIX, NihilRex, DIT_grue, misora, Tristitan, SimonS3

Offline Steve Walmsley

  • Moderator
  • Admiral of the Fleet
  • *****
  • Posts: 6659
  • Thanked: 1055 times
    • View Profile
    • http://www.starfireassistant.com
Re: C# Aurora Changes List
« Reply #49 on: November 05, 2017, 12:14:00 PM »
Planetary Terrain

As part of the ground combat changes, each planet will have a dominant terrain type. In many cases, for most asteroids, comets or small moons, that type will simply be Barren. Within certain environmental tolerances, other terrain types are possible.

Any system body with temperature lower than -100C or higher than 200C or with no atmosphere or atmosphere greater than 10 atm will be Barren, unless it has platelet or extreme tectonics, in which case it will be Mountain.

All other system bodies will check the following table to determine which terrain types are eligible based on the environmental conditions. One of the eligible terrain types will be selected randomly. Barren, Mountain and Rift Valley (which are base types available without any atmospheric, temperature or water requirements) will only be selected if no other terrain types are eligible. The tectonic numbers are internal to Aurora and have the following values: Dead = 1, Hot Spot = 2, Plastic = 3, Plate Tectonics = 4, Platelet Tectonic = 5, Extreme = 6.

Terraforming will change the terrain under two circumstances:
1) A planet with a base type (Barren, Mountain and Rift Valley) becomes eligible for another terrain of a similar type. Mountain can move to any other Mountain type, Rift Valley to any other Rift Valley Type and Barren to any non-Mountain, non-Rift Valley type.
2) The terrain type is no longer possible with the current environmental conditions. A new terrain type is generated with the same base type.

I am happy to add additional types or modify the environmental parameters if there is general consensus on any changes.

The fortification modifier is a modifier for the max fortification level, rather than an automatic defence increase. It means you can dig in much deeper (given sufficient time) in Mountains than you can in Steppe or Swamp. The to hit modifier is a reduction in the chance to hit in that terrain (for other ground units and any supporting ships in orbit). In effect, fortification is a benefit to the defender, while to hit is a penalty to both sides. Within the new ground combat rules, you can assign ground units 'capabilities', such as Jungle Warfare, Mountain Warfare, etc. which will double their chance to hit in those types of terrain. Ground units of species with certain types of home world may gain capabilities for free (if you are from a desert planet, you would gain Desert Warfare for free, for example). There are additional capability options to avoid penalties for ground units fighting on worlds that are outside their species tolerance for gravity, temperature and pressure.

An important factor to bear in mind is that when ships are engaging ground units with surface-to-orbit capability, the main defence of the ground unit will be its fortification level. The ship-based weapons are assumed to hit 100% of the time divided by the fortification level. On a planet with Steppe as the dominant terrain type, the maximum fortification of a static ground unit will be 6 with no penalty for the ship to hit. On a Jungle Mountain world, the maximum fortification level will be 18 for that same ground unit and any shots against it by the ships will be modified by 0.125, giving the ground unit an effective fortification level of 144. In other words, the ship in orbit is going to hit once every 144 shots. So trying to use orbital bombardment against surface to orbit units buried in jungle-covered mountains is going to be a Bad Idea. It would be far more effective to send in ground forces (which can't be hit by STO units) to dig them out. That is an extreme example, but there should be many more situations where there are some serious decisions for the attacker.

« Last Edit: November 05, 2017, 06:19:53 PM by Steve Walmsley »
 
The following users thanked this post: waresky, Ayeshteni, MagusXIX, Kytuzian, Prapor, Tristitan, madgabz, PartyAlias, Rye123

Offline Steve Walmsley

  • Moderator
  • Admiral of the Fleet
  • *****
  • Posts: 6659
  • Thanked: 1055 times
    • View Profile
    • http://www.starfireassistant.com
Re: C# Aurora Changes List
« Reply #50 on: December 10, 2017, 01:32:33 PM »
Cargo Shuttle Bays

Part of the background in C# Aurora will be that large TN ships function only in space and cannot move any closer to planetary bodies than low orbit. Small craft below a limit of 500 tons, such as fighters and shuttles, are capable of landing on planets. Ship are built in orbit and habitats are assembled in orbit. Only fighters can be built on the ground.

As part of this change, Cargo Handling Systems have been replaced by Cargo Shuttle Bays. They function in a similar way, although they are larger (10 HS) and more expensive.

Because large ships cannot land on planets, a freighter or colony ship cannot load / unload unless it has at least one Cargo Shuttle Bay, or the target population has either a Spaceport or a Cargo Shuttle Station (new installation, 1200 BP). Spaceports and Cargo Shuttle Stations can service any number of ships simultaneously but they do not stack. In effect they count as a single Cargo Shuttle Bay for any ship at the population.

All races start with conventional shuttles available for their cargo shuttle bays and stations. Conventional shuttles do not reduce loading time but do enable cargo deliveries to planets without Spaceports or Cargo Shuttle Stations. Three levels of advancement in shuttle technology are available:

1) TN Shuttles (5000 RP): This reduces loading time by 2 per bay (so two bays means speed reduced by 4, three bays means speed reduced by 6).
2) Improved Shuttles (15,000 RP): Reduces loading time by 3 per bay.
3) Advanced Shuttles (40,000 RP): Reduces loading time by 5 per bay.

All bays and stations use the new shuttles once they are available.

Base cargo load times have been reduced by about 45% for all situations (36s per cargo point to 20s per cargo point and 18s to 10s per colonist), which means a ship with a standard cargo bay and a single Cargo Shuttle Bay with TN Shuttle tech will take slightly longer than the same ship with a cargo handling system in VB6.

This will affect troop transport in a different way and that will be covered in a separate post.
 

Offline Steve Walmsley

  • Moderator
  • Admiral of the Fleet
  • *****
  • Posts: 6659
  • Thanked: 1055 times
    • View Profile
    • http://www.starfireassistant.com
Re: C# Aurora Changes List
« Reply #51 on: December 19, 2017, 01:34:50 PM »
Forced Labour Camps
 
As part of the ground combat overhaul, Forced Labour ground units will be removed. They will be replaced by two new installations; the Forced Labour Construction Camp and the Forced Labour Mining Camp. These each cost 40 BP to build and have the same output as a construction factory and a mine respectively. Transport size is 100,000 cargo points, or 4x that of a construction factory.
 
Forced Labour Camps can be built at any population, not just occupied ones. However, they consume 100,000 population and instantly cause 5 points of unrest. Once built they only require 5000 population to man them (serving as overseers), as the bulk of the workers, plus associated basic survival-level infrastructure, is provided during construction.
 
This installation has a few different uses. Making an conquered population productive is one, as you can build three of these for a single construction factory or mine cost, offsetting much of the production modifier penalty for occupation status. You can achieve more overall production in one of your own colonies for lower cost, if you are prepared to accept the unrest penalty, or you can build these in occupied populations and ship them to your own colonies.

Finally, because they have a minimal requirement for a supporting population, you can move them to a hostile world using only a small amount of infrastructure for the overseers. In effect, you can create the Dilithium mines of Rura Penthe if you wish. There are role-playing consequences, as you may not want to play the type of empire that convert its citizens into slaves and sends them to mine asteroids.

Labour Camps are affected by all the production modifiers that affect construction factories and mines (such as radiation, unrest, economic and political modifiers, etc.), although their cheap build cost allows you to offsets these modifiers with triple production. The transport requirement take into account the number of integral workers and supporting infrastructure. However, you could ship the potential workers as colonists (in a quarter of the tonnage) and create the Forced Labour Camp at the desired location.

While Labour Camps might seem low cost and tempting, they do have drawbacks. The large transport size means you could use the same freighter lift for 4x as many mines or construction factories. In addition, the 100,000 population cost is actually much higher in reality as you lose all the potential future growth & wealth provided by that population. They will be suitable in certain situations though; where you need to ramp up production and have excess population to support it, if you don't want to wait for a conquered population to improve its political status or you need a fast way of producing an equivalent to automated mines.
 
The unrest penalty for creation might be a little low so I will see how that works in play-test.

NOTE: Edited to include the 5000 pop requirement after a suggestion in the comments thread.
« Last Edit: December 19, 2017, 06:23:21 PM by Steve Walmsley »
 
The following users thanked this post: Alfapiomega, Tristitan, madgabz, Rye123

Offline Steve Walmsley

  • Moderator
  • Admiral of the Fleet
  • *****
  • Posts: 6659
  • Thanked: 1055 times
    • View Profile
    • http://www.starfireassistant.com
Re: C# Aurora Changes List
« Reply #52 on: December 26, 2017, 01:11:29 PM »
Removal of Planetary Defence Centres

Planetary Defence Centres (essentially a ground-based ship) will not exist in C# Aurora. They will be replaced by a much more detailed ground-combat system, including ground units capable of engaging ships within energy range of the planet.

There is a lengthy discussion of this change and the new ground combat system in the following thread. I will begin posting the new ground combat rules in the next week or two.

http://aurora2.pentarch.org/index.php?topic=9679.0
 
The following users thanked this post: SgtVennamo, Zincat, Alfapiomega, Tristitan, madgabz, Rye123

Offline Steve Walmsley

  • Moderator
  • Admiral of the Fleet
  • *****
  • Posts: 6659
  • Thanked: 1055 times
    • View Profile
    • http://www.starfireassistant.com
Re: C# Aurora Changes List
« Reply #53 on: January 02, 2018, 10:11:41 AM »
« Last Edit: January 02, 2018, 07:15:06 PM by Steve Walmsley »
 
The following users thanked this post: Laurence, waresky, Demonides, MarcAFK, Noble713, Hydrofoil, Viridia, Tristitan, madgabz, xhunterx

Offline Steve Walmsley

  • Moderator
  • Admiral of the Fleet
  • *****
  • Posts: 6659
  • Thanked: 1055 times
    • View Profile
    • http://www.starfireassistant.com
Re: C# Aurora Changes List
« Reply #54 on: January 02, 2018, 01:55:51 PM »
« Last Edit: January 02, 2018, 02:01:08 PM by Steve Walmsley »
 
The following users thanked this post: Laurence, waresky, Demonides, MarcAFK, Noble713, Viridia, Prapor, Tristitan, madgabz, serger, xhunterx, Rye123

Offline Steve Walmsley

  • Moderator
  • Admiral of the Fleet
  • *****
  • Posts: 6659
  • Thanked: 1055 times
    • View Profile
    • http://www.starfireassistant.com
Re: C# Aurora Changes List
« Reply #55 on: January 23, 2018, 04:50:21 PM »
Sol System Changes

This is a placeholder for Sol System changes as I make them

1) Salacia and 2007 OR10 upgraded to dwarf planet status. They are large enough and I am sure this will be confirmed at some point.
 
The following users thanked this post: Laurence, waresky, Prapor, Tristitan, madgabz, serger, Rye123

Offline Steve Walmsley

  • Moderator
  • Admiral of the Fleet
  • *****
  • Posts: 6659
  • Thanked: 1055 times
    • View Profile
    • http://www.starfireassistant.com
Re: C# Aurora Changes List
« Reply #56 on: January 28, 2018, 04:33:32 AM »
New Game Settings

This is a placeholder for Game-level modifiers

1) Percentage modifier for Research Speed (for all races)
2) Percentage modifier for Terraforming Speed (for all races)
3) Percentage modifier for starting minerals on Sol.
4) Flag for Active Civilian Shipping Lines. When this is disabled, shipping lines will not produce ships.
5) Flag for recovering tech due to conquest. You can disable this so no new tech is gained via conquest.

You can specify a number of Earth-based player races on the Game Setup window. You will cycle through a number of Race Creation windows equal to the number of races selected. You will still need to create any non-Earth-based races after the main game creation process.
 

Offline Steve Walmsley

  • Moderator
  • Admiral of the Fleet
  • *****
  • Posts: 6659
  • Thanked: 1055 times
    • View Profile
    • http://www.starfireassistant.com
Re: C# Aurora Changes List
« Reply #57 on: February 12, 2018, 02:58:27 PM »
Starting Build Points

A new player race in Aurora receives a number of Starting Build Points equal to two years wealth. These can be spent on instant build for Ships and Ground Formations.

If the available Instant Build Point total is greater than zero, the Instant Build section will be shown on the Miscellaneous tab of the Class window, including the current Instant Build Point total, plus selection options for destination fleet and number of ships to be built. This section will also appear if SM Mode is active, so additional ships can be instantly built if required by the game setup.

If the available Instant Build Point total is greater than zero, that total, plus the Instant Build button, will be shown on the GU Training tab of the Economics window. When the Instant Build button is clicked, a popup box will allow entry of the number of formations to be built. This button will also appear if SM Mode is active, so additional formations can be instantly built if required by the game setup.

If you choose to have automatically constructed ground formations at game start, their cost will be deducted from the starting build points.

The ship options replace the VB6 Fast OOB window, while the ground options are new for C# Aurora.
« Last Edit: February 12, 2018, 03:07:52 PM by Steve Walmsley »
 
The following users thanked this post: Viridia, Tristitan, Rye123

Offline Steve Walmsley

  • Moderator
  • Admiral of the Fleet
  • *****
  • Posts: 6659
  • Thanked: 1055 times
    • View Profile
    • http://www.starfireassistant.com
Re: C# Aurora Changes List
« Reply #58 on: Today at 07:40:50 AM »
Default Order for Unload Colonists

I've completely rewritten the default order for unloading colonists (used by shipping lines, NPRs and your own ships if desired). The process is as follows:

1) Colony fleet looks for a suitable population with less than 25m pop and no other colony fleets inbound, checking its current system first and then using the path finding algorithm to search everywhere else in the empire.
2) Same as 1) but without the check for inbound colony ships.
3) Searches for any suitable population with a status of Colonist Destination (which you can set for any pop of at least 25m).

When determining if a population is a suitable destination, the fleet checks the following:

1) How many colonists it is carrying.
2) If the species is the same as the colonists.
3) The available capacity of the system body on which the population is situated, taking into account other populations.
4) The available capacity of the infrastructure (normal or LG depending on the gravity), taking into account the current population size.
5) The lesser of 2) and 3) is used as the base capacity of the population to accept new colonists.
6) Any available space in orbital habitats is added to that capacity.
7) The total number of colonists on ships already inbound to the colony is deducted from that capacity.
8) if the capacity exceeds the number of colonists in the checking fleet and the species match, the colony is suitable.

This should prevent the current problem of many colony ships delivering to a colony without the capacity to support them all. As soon as a fleet determines a colony is suitable, the orders are issued, which means other fleets checking in the same increment will be aware of the extra inbound colonists.

Because of these changes, Passenger Liners will no longer search their current system for a potential destination (otherwise they could load and unload at the same population).
« Last Edit: Today at 08:07:43 AM by Steve Walmsley »
 

Offline Steve Walmsley

  • Moderator
  • Admiral of the Fleet
  • *****
  • Posts: 6659
  • Thanked: 1055 times
    • View Profile
    • http://www.starfireassistant.com
Re: C# Aurora Changes List
« Reply #59 on: Today at 08:23:46 AM »
Shipping Line Construction

A Shipping Line will start building freighters and colony ships when the parent race has two colonies (including the capital) with populations greater than zero.

A Shipping Line will start building passengers liners when the parent race has two colonies (including the capital) with populations greater than zero in two different systems.

A Shipping Line will start building harvesters when the parent race has two colonies with populations greater than zero and there is Sorium present at any gas giant or superjovian in a system with a parent race population of at least ten million (including the capital).

The number of civilian freighters and colony ships will be kept relatively even.
 

 

Sitemap 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52