Author Topic: C# Aurora Changes Discussion  (Read 441768 times)

0 Members and 2 Guests are viewing this topic.

Offline sloanjh (OP)

  • Global Moderator
  • Admiral of the Fleet
  • *****
  • Posts: 2805
  • Thanked: 112 times
  • 2020 Supporter 2020 Supporter : Donate for 2020
    2021 Supporter 2021 Supporter : Donate for 2021
Re: C# Aurora Changes Discussion
« Reply #2430 on: November 08, 2019, 08:57:37 AM »
Quote from: Bremen link=topic=8497. msg116821#msg116821 date=1573158202
I think the retooling cost does essentially the same thing and is even simpler than that.

I always thought of the retooling costs as the work required to literally modify the equipment at the shipyard to make a new class.   You need to make forms for the hull, jigs for equipment that are unique to classes of ships and supports for the hull before it is complete.   You could include first-of-class costs in that as well, and it might be simpler.
I like this idea, and I think it would be easier to implement.   The same bonus should also apply to construction time.

Historical note:  My recollection is that this (the retooling cost includes first-in-class costs) was exactly the intent when it was introduced.  My (much shakier) recollection is that the first instance was more expensive, although I could be conflating that with StarFire Assistant.

John
 

Offline papent

  • Lieutenant
  • *******
  • Posts: 163
  • Thanked: 45 times
  • Off We Go Into The Wild Blue Yonder
Re: C# Aurora Changes Discussion
« Reply #2431 on: November 08, 2019, 09:40:37 AM »
Quote from: Rabid_Cog link=topic=8497. msg116820#msg116820 date=1573156889
I'd rather just have it as a bonus.  Stacking 1% reduction in build cost per item built, up to a max of 5/10/15/20% limited by a tech as a simple idea.  So the base price IS your first-of-class cost which reduces for each one you build.  Keeps things simpler.  Your first in class cost would be per shipyard or per production run then, though.
.   
I like this idea, and I think it would be easier to implement.   The same bonus should also apply to construction time.   

I concur with this idea, and I think the same bonus should also apply to all serial productions  i.e construction, ordinance, fighters, ships, and maybe ground forces?
In my humble opinion anything that could be considered a balance issue is a moot point unless the AI utilize it against you because otherwise it's an exploit you willing choose to use to game the system. 
Rule 0 Is effect : "The SM is always right/ What SM Says Goes."
 

Offline Garfunkel

  • Registered
  • Admiral of the Fleet
  • ***********
  • Posts: 2781
  • Thanked: 1048 times
Re: C# Aurora Changes Discussion
« Reply #2432 on: November 08, 2019, 11:45:09 AM »
Okay, I'll queue 5000 Research Labs with 1 Construction Factory. Of course I don't have the minerals to build 5000 RL but that's okay, 1 CF won't get them build anytime this millennium so that's not a problem. It WILL get maximum efficiency bonus at which point I can throw as many CF at it as I want to exploit that bonus. And if I need them for something else, I'll just leave that 1 CF there to maintain the serial production bonus.

This sort of system was used in Hearts of Iron 3 (and slightly modified in 4 I believe) and it was nothing but exploit city for multiplayer and yet another way human player was overpowered compared to the AI.

Serial production bonus CAN work with shipyards because you can't move slipways to another shipyard. But with construction/fighter/ordnance factories as well as research, fields where you can move factories and labs freely around, it wouldn't work.

It's not an end of the world issue, because naturally a player can disregard it and not abuse it - like some players do with scientists and the 0 RL project exploit - but I'm little wary of adding clear and obvious exploits to the game when the feature itself isn't really necessary.
 
The following users thanked this post: Scandinavian

Offline Mini

  • Chief Petty Officer
  • ***
  • M
  • Posts: 38
  • Thanked: 1 times
Re: C# Aurora Changes Discussion
« Reply #2433 on: November 08, 2019, 03:32:35 PM »
I think applying a serial production bonus to anything you'll be building for the entire game is a bad idea, since it basically just makes those things cheaper by however much the bonus is. The problem of leaving 0.00001% of production maintaining a serial bonus can be solved by 1) increasing the bonus only by items completed and not time spent building, and 2) having the bonus decay over time. This will mean that under a certain threshold there will be a fluctuating equilibrium reached with the average bonus being lower than the maximum bonus, inversely proportional to how much production you are putting in. Also applying it to the population as a whole instead of a single line of production also makes more sense in Aurora (if we are talking planet-side production and not shipyards), since you won't lose the bonus if you momentarily stop production (even within a single increment) and likely works better with how the game is programmed.

That said I think a serial production mechanic as a whole isn't that good of an idea. As Garfunkel brought up, it's something that strongly encourages trying to find exploits in, and even if you can ignore those exploits having them in the game is still a bad thing. It's also a very opaque mechanic that means that numbers all over the place to do with production start being various degrees of incorrect, and (in the case of shipyards) encourages having a large number of single slipway shipyards, increasing the amount of micromanagement and organisational clutter.
 

Offline Father Tim

  • Vice Admiral
  • **********
  • Posts: 2162
  • Thanked: 531 times
Re: C# Aurora Changes Discussion
« Reply #2434 on: November 08, 2019, 04:51:19 PM »
I miss 'prototype hull' and 'new class' penalties, and would like to see them come back.  I wouldn't want bonuses* for serial production, because now you're altering the established values of things.  I don't want to see unlimited 75% Frigates; I'm happy to see three expensive (say 125%, 120%, & 110%) 'class leaders'.

If you don't want to play with penalties, switch them off and everything costs 100%.  If you do want them, you pay a little extra for new designs.  If we use bonuses, I can't see anyone turning them off and not getting their 'cheap' second dozen ships.

.

*The only bonus I'd like is speed.  I'd be quite happy if production of a design became faster (but definitely not cheaper) as more were completed.

- - - -

Disclaimer:  My empire almost always build one yard for each design.  I read much fiction on here where empires churn out two dozen freighters, retool their (only) commercial yard, build ten colony ships, retool, seven terraformers, retool, a couple tugs, retool, a dozen new-tech freighters, retool, etc.  They end up spending more on retooling than I do on building multiple custom yards.  Now that C# Aurora has ditched the per-yard overhead, it will be even more beneficial.

I build a one-slip terraformer yard and leave it producing one ship every forty-four weeks for decades, occasionaly retooling to an upgraded-tech terraformer design.  Meanwhile, the yard next door is producing one fuel harvester every thirty-five weeks.  The freighter yard has four slips, and the colony transport yard, two.  Having six yards with one slip each that retool much less often is going to beat having one yard with 12 slips that retools every time it finishes a 'flight' of ships.
 

Offline Jorgen_CAB

  • Admiral of the Fleet
  • ***********
  • J
  • Posts: 2822
  • Thanked: 673 times
Re: C# Aurora Changes Discussion
« Reply #2435 on: November 08, 2019, 08:46:42 PM »
Okay, I'll queue 5000 Research Labs with 1 Construction Factory. Of course I don't have the minerals to build 5000 RL but that's okay, 1 CF won't get them build anytime this millennium so that's not a problem. It WILL get maximum efficiency bonus at which point I can throw as many CF at it as I want to exploit that bonus. And if I need them for something else, I'll just leave that 1 CF there to maintain the serial production bonus.

This sort of system was used in Hearts of Iron 3 (and slightly modified in 4 I believe) and it was nothing but exploit city for multiplayer and yet another way human player was overpowered compared to the AI.

Serial production bonus CAN work with shipyards because you can't move slipways to another shipyard. But with construction/fighter/ordnance factories as well as research, fields where you can move factories and labs freely around, it wouldn't work.

It's not an end of the world issue, because naturally a player can disregard it and not abuse it - like some players do with scientists and the 0 RL project exploit - but I'm little wary of adding clear and obvious exploits to the game when the feature itself isn't really necessary.

This is only if it is badly implemented...

If we take factories then you could have a gearing bonus based on some technology and time you spent building something. You just store the gearing bonus of each item line with an amount of factories applied to it. When you add factories you degrade the gearing bonus accordingly and if you remove factories it stays the same. So now you need to be careful when and if you want to really increase the number of factories for that line.

Or in the game it would rather be the number of percent you dedicate for each item and not factories directly.

Stuff would not become cheaper to build, you just build them faster.

As a balance you could just make factories slightly less productive.

I don't mind either way as I already restrict how much industry can shift between lines every year anyway so I already simulate this effect through role-play.
 

Offline xenoscepter

  • Vice Admiral
  • **********
  • Posts: 1154
  • Thanked: 317 times
Re: C# Aurora Changes Discussion
« Reply #2436 on: November 09, 2019, 02:35:04 AM »
Quote
If we take factories then you could have a gearing bonus based on some technology and time you spent building something. You just store the gearing bonus of each item line with an amount of factories applied to it. When you add factories you degrade the gearing bonus accordingly and if you remove factories it stays the same. So now you need to be careful when and if you want to really increase the number of factories for that line.

 --- This is what Hearts of Iron IV did, it works quite well actually. Never played Hearts of Iron III, so I can't say anything about that. In Hearts of Iron IV, however, I have sunk a considerable amount of time into that game and can say this:

 - Production is based on per factory assigned.

 - Time spent on the item being produced increased Production Efficiency.

 - Switching items would remove efficiency, not sure if switching to similar equipment (like Infantry Equipment 1 to Infantry Equipment 2 for example) diminished the penalty or not.

 - There were several techs supporting this, with a few modifiers of note.

 - Cost did NOT decrease with efficiency gain, but rather the number of units produced per line. (Speed)

 --- The modifiers were Production Efficiency, Efficiency Gain Speed (basically how fast you could "tool up" a line), Efficiency Cap, and Efficiency Loss (How much you lost when switching to a different item.)
 

Offline Tikigod

  • Lieutenant
  • *******
  • Posts: 195
  • Thanked: 55 times
Re: C# Aurora Changes Discussion
« Reply #2437 on: November 09, 2019, 09:17:54 AM »
Quote
If we take factories then you could have a gearing bonus based on some technology and time you spent building something. You just store the gearing bonus of each item line with an amount of factories applied to it. When you add factories you degrade the gearing bonus accordingly and if you remove factories it stays the same. So now you need to be careful when and if you want to really increase the number of factories for that line.

 --- This is what Hearts of Iron IV did, it works quite well actually. Never played Hearts of Iron III, so I can't say anything about that. In Hearts of Iron IV, however, I have sunk a considerable amount of time into that game and can say this:

 - Production is based on per factory assigned.

 - Time spent on the item being produced increased Production Efficiency.

 - Switching items would remove efficiency, not sure if switching to similar equipment (like Infantry Equipment 1 to Infantry Equipment 2 for example) diminished the penalty or not.

 - There were several techs supporting this, with a few modifiers of note.

 - Cost did NOT decrease with efficiency gain, but rather the number of units produced per line. (Speed)

 --- The modifiers were Production Efficiency, Efficiency Gain Speed (basically how fast you could "tool up" a line), Efficiency Cap, and Efficiency Loss (How much you lost when switching to a different item.)

Indeed, the way Hearts of Iron 4 approaches production could actually be applied very well to ship production considering how the game actually goes about producing ships on a per module basis.

A shipyard could be made to track a history of what components it has produced overtime (with perhaps a production history reset after a very large retooling procedure, or after some years of inactivity), and then using variables such as module complexity (construction cost), shipyard building rate and number of production iterations come up with a efficiency scale and ceiling cap in that shipyard for each type of module in its production history.

Retooling could be approached by essentially comparing the component lists needed for the new target design against the current design, retaining those modules that are shared across both designs in the shipyards production history (and reduce the existing efficiency gain by some factor) and then clear the rest of that shipyards production history once retooling is completed.

I am not sure how retooling is approached in the VB/C# versions but doing that kind of approach would also make it more natural to calculate retooling costs based on component differences of the two designs, rather than based on overall build cost/size differences.

This could also be applied in a more basic way to ordnance, PDC, orbital structures, fighters and so forth. Though in such cases it would probably be best to approach production history in a much more crude manner, essentially just doing a linear efficiency gain in that area with each component built and then do a efficiency wipe when producing a new design of that object type.
« Last Edit: November 09, 2019, 09:21:55 AM by Tikigod »
The popular stereotype of the researcher is that of a skeptic and a pessimist.  Nothing could be further from the truth! Scientists must be optimists at heart, in order to block out the incessant chorus of those who say "It cannot be done. "

- Academician Prokhor Zakharov, University Commencement
 

Offline papent

  • Lieutenant
  • *******
  • Posts: 163
  • Thanked: 45 times
  • Off We Go Into The Wild Blue Yonder
Re: C# Aurora Changes Discussion
« Reply #2438 on: November 09, 2019, 09:24:52 AM »
i imagined as working just as xenoscepter, Jorgen_CAB, and Father Tim implied.

A: it only decrease production time not price/resources required.
B: there's Efficiency/gearing bonus as stated by previous posters.
In my humble opinion anything that could be considered a balance issue is a moot point unless the AI utilize it against you because otherwise it's an exploit you willing choose to use to game the system. 
Rule 0 Is effect : "The SM is always right/ What SM Says Goes."
 

Offline Dawa1147

  • Chief Petty Officer
  • ***
  • D
  • Posts: 49
  • Thanked: 11 times
Re: C# Aurora Changes Discussion
« Reply #2439 on: November 09, 2019, 05:43:42 PM »
I agree with the faster (but not cheaper) approach, with an option to turn it on or off similar to Fleet Maintenance. 
 

Offline Garfunkel

  • Registered
  • Admiral of the Fleet
  • ***********
  • Posts: 2781
  • Thanked: 1048 times
Re: C# Aurora Changes Discussion
« Reply #2440 on: November 10, 2019, 07:11:35 PM »
It can only affect shipyards because individual factories are not tracked and I'm assuming Steve doesn't want to put in that level of fidelity. If you don't track individual factories, you leave the system open for the sort of abuse I described above.

What's the deviation between classes so that they still qualify for faster construction? Same as for construction in general, ie 20% BP difference? Or was it 10%, can't remember now. Should it be something else? Will this lead into container/bulk type ships, ie you design a template ship that never gets built that has generic engines and sensors etc and then you build the 3-5 different varieties of it that are only different from the template by the allowed 10-20% BP. Which can lead to a situation where not only (most) of your shipyards can build (most) of your ships, but they do it (possibly much) faster.

I'm sure other people can think of more pitfalls in such a system. I don't mean that a feature needs to be balanced to boredom, but that we as a community think things through as much as possible, to make things easier for Steve.
 

Offline Rabid_Cog

  • Commander
  • *********
  • Posts: 306
  • Thanked: 28 times
Re: C# Aurora Changes Discussion
« Reply #2441 on: November 11, 2019, 04:10:31 AM »
It can only affect shipyards because individual factories are not tracked and I'm assuming Steve doesn't want to put in that level of fidelity. If you don't track individual factories, you leave the system open for the sort of abuse I described above.

What's the deviation between classes so that they still qualify for faster construction? Same as for construction in general, ie 20% BP difference? Or was it 10%, can't remember now. Should it be something else? Will this lead into container/bulk type ships, ie you design a template ship that never gets built that has generic engines and sensors etc and then you build the 3-5 different varieties of it that are only different from the template by the allowed 10-20% BP. Which can lead to a situation where not only (most) of your shipyards can build (most) of your ships, but they do it (possibly much) faster.

I'm sure other people can think of more pitfalls in such a system. I don't mean that a feature needs to be balanced to boredom, but that we as a community think things through as much as possible, to make things easier for Steve.

If you can manage to design your ships in this manner, you deserve every scrap of benefit you get. I've tried to do that before and it is extremely difficult to get all your ships to fit the same mold. Remember, size differences have a huge impact so you have to fill in the space with something on the base ship.
I have my own subforum now!
Shameless plug for my own Aurora story game:
5.6 part: http://aurora2.pentarch.org/index.php/topic,4988.0.html
6.2 part: http://aurora2.pentarch.org/index.php/topic,5906.0.html

Feel free to post comments!
http://aurora2.pentarch.org/index.php/topic,5452.0.html
 

Offline chrislocke2000

  • Captain
  • **********
  • c
  • Posts: 544
  • Thanked: 39 times
Re: C# Aurora Changes Discussion
« Reply #2442 on: November 11, 2019, 07:12:13 AM »
I agree with the faster (but not cheaper) approach, with an option to turn it on or off similar to Fleet Maintenance.

We do already get a cheaper average ship with repeated runs once you factor in the retooling costs as every ship off the line then spreads that retooling cost. Personally I think that is enough benefit already.

 
 
The following users thanked this post: Bremen, Cinnius

Offline Tikigod

  • Lieutenant
  • *******
  • Posts: 195
  • Thanked: 55 times
Re: C# Aurora Changes Discussion
« Reply #2443 on: November 14, 2019, 02:56:37 PM »
I agree with the faster (but not cheaper) approach, with an option to turn it on or off similar to Fleet Maintenance.

We do already get a cheaper average ship with repeated runs once you factor in the retooling costs as every ship off the line then spreads that retooling cost. Personally I think that is enough benefit already.

If you stage your ship components well so that your modules are suitable for a multiple ship designs I believe you can get around a fair bit of the added retooling time cost by stockpiling the modules you will need ahead of time as the shipyard will use pre-existing modules it needs in local stockpiles before actually attempting to construct the modules itself which I've always been led to believe takes longer.

So whilst you're retooling you can actually be producing (Or salvaging old ships) to get a stockpile for most of the modules you'll need.
« Last Edit: November 14, 2019, 02:58:38 PM by Tikigod »
The popular stereotype of the researcher is that of a skeptic and a pessimist.  Nothing could be further from the truth! Scientists must be optimists at heart, in order to block out the incessant chorus of those who say "It cannot be done. "

- Academician Prokhor Zakharov, University Commencement
 

Offline TMaekler

  • Vice Admiral
  • **********
  • Posts: 1112
  • Thanked: 298 times
Re: C# Aurora Changes Discussion
« Reply #2444 on: November 15, 2019, 02:17:20 AM »
Maybe the production efficiency bonus should not be added to the planetary production site, or the shipyard, but to a person? Widening the use of personnel for those installations, the installation foreman receives the production experience. Then when later another unit of the experience he gained is produced he can construct them quicker. Only for his project of course. Or if you want to build in parallel his experience is „split up“. And if he dies a new guy has to be trained... .
 
The following users thanked this post: Nori