Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
May be make each defence building behave like 1 interceptor? If submenu is impossible, then just use the same Interception menu used by craft. Sure it might get cluttered, but I think people who desire such option can handle some micromanagement in exchange for new strategic options.
Does this mechanic make base defences easier?
Like, a Battleship is fired at twice - first on the Geoscape and then on the defence screen. Or is the base artillery defence part disabled?
I don't think it would be a problem if it is attacked twice, I just would like to know.
From the Interception screen I can see each defensive building is represented by a separate weapon. What if a base has more than 2 types of defensive buildings?
# X-COM 1 (UFO: Enemy Unknown) ruleset
defense:
rechargeTime: 10 # minutes. If value == 0 then active defense will be disabled permanently.
retaliationChance: 30 # 0..100 %. Chance to uncover the base by aliens after air battle.
#-----------------------------------
crafts:
- type: STR_BASE
requires:
- STR_BASE_DEF
sprite: 1 #26 # I need new icon
damageMax: 100 # should be > 0. Actually not used.
weapons: 2
#-----------------------------------
craftWeapons:
- type: STR_MISSILE_DEFENSES
sprite: 1
sound: 5
damage: 100 # the same as for launcher
range: 40 # range in pixels: (range for facility)/4; i.e. 160/4 = 40
accuracy: 50 # the same as for facility
# reloadCautious: 96 # not used
reloadStandard: 72
# reloadAggressive: 48 # not used
ammoMax: 100 # in fact, maximum is 6x6-1 = 35
launcher: STR_AVALANCHE_LAUNCHER
projectileType: 1
projectileSpeed: 8
- type: STR_LASER_DEFENSES
sprite: 4
sound: 8
damage: 70
range: 50 # 200/4 = 50
accuracy: 60
# reloadCautious: 24
reloadStandard: 24
# reloadAggressive: 24
ammoMax: 100
launcher: STR_LASER_CANNON
projectileType: 4
- type: STR_PLASMA_DEFENSES
sprite: 5
sound: 9
damage: 140
range: 60 # 240/4 = 60
accuracy: 70
# reloadCautious: 24
reloadStandard: 24
# reloadAggressive: 24
ammoMax: 100
launcher: STR_PLASMA_BEAM
projectileType: 5
- type: STR_FUSION_BALL_DEFENSES
sprite: 3
sound: 7
damage: 230
range: 70 # 280/4 = 70
accuracy: 80
# reloadCautious: 64
reloadStandard: 48
# reloadAggressive: 32
ammoMax: 100
launcher: STR_FUSION_BALL_LAUNCHER
projectileType: 3
projectileSpeed: 8
#-----------------------------------
facilities:
- type: STR_MISSILE_DEFENSES
defenseRange: 160 # maximum range is 280 miles (70*4 = 280)
- type: STR_LASER_DEFENSES
defenseRange: 200
- type: STR_PLASMA_DEFENSES
defenseRange: 240
- type: STR_FUSION_BALL_DEFENSES
defenseRange: 280
#-----------------------------------
#extraSprites:
# - type: INTICON.PCK
# width: 352
# height: 80
# subX: 32
# subY: 40
# files:
# 26: Resources/Base_Defense/bd_geoscape.png
#-----------------------------------
extraStrings:
- type: en-US
strings:
STR_ACTIVATE_DEFENSE: Activate Base Defense
- type: en-GB
strings:
strings:
STR_ACTIVATE_DEFENSE: Activate Base Defence
good catch!int ManufactureInfoState::getMonthlyNetProfit()
{
const int HOURS_PER_MONTH = 365 * 24 / 12; https:// Also you can use HOURS_PER_CURRENT_MONTH instead
const RuleManufacture *item = _production->getRules();
int numEngineers = _production->getAssignedEngineers();
https:// how many manHours will be consumed for this task per average month
int manHoursPerMonth = HOURS_PER_MONTH * numEngineers;
if (!_production->getInfiniteAmount())
{
int manHoursRemainig = item->getManufactureTime() * (_production->getAmountTotal() - _production->getAmountProduced());
manHoursPerMonth = std::min(manHoursPerMonth, manHoursRemainig);
}
https:// how many items will be manufactured in this month
float itemsPerMonth = (float)manHoursPerMonth / (float)item->getManufactureTime();
https:// for how many items will be consumed resources in this month
https:// (because resources consumed always before the beginning of production;
https:// and because possible situation when production task cannot be finished in one month)
float consumedPerMonth = itemsPerMonth;
if (manHoursPerMonth == HOURS_PER_MONTH * numEngineers)
{
consumedPerMonth += 1.0f;
}
https:// final calculation
int saleValue = _btnSell->getPressed() ? _producedItemsValue : 0;
int consumedValue = item->getManufactureCost() + _usedItemsValue;
int salaryCost = _game->getRuleset()->getEngineerCost() * numEngineers;
float livingCost = ((float)_totalLivingQuartersMaintenance * numEngineers) / _totalLivingSpace;
float workshopCost = ((float)_totalWorkshopMaintenance * (numEngineers + item->getRequiredSpace()) / _totalWorkshopSpace;
return saleValue * itemsPerMonth - consumedValue * consumedPerMonth - (salaryCost + livingCost + workshopCost);
}
@redv: I like your version of the algorithm -- very clean. But what does the final number mean to the player? What are they supposed to do with a value that is scaled by workshop utilization? That number is not directly related to the actual change in funds the player will see due to manufacturing at the end of the month.
I think the the net change of funds due to all manufacturing-related costs and profits at the current base is what the player really needs to know. Say you have one living quarters, one workshop, and 10 engineers and are manufacturing (infinite) motion scanners for sale. In the scaled algorithm you have above, we'd show the profit as $123K. However, the change in funds due to manufacturing at this base would really be $97K due to the unused workshop space. Things get worse if you aren't actually allocating all your engineers, or have some engineers assigned to other projects. If you have 50 engineers but only allocate 10 for this job, the scaled algorithm would still calculate $123K but the actual change in funds at the end of the month (due to manufacturing) would be -$910K! I think it is important to consider *all* manufacturing resources and liabilities at the base when calculating profit since it really does affect the final result.
int ManufactureInfoState::getMonthlyNetProfit()
{
static const int HOURS_PER_MONTH = 365 * 24 / 12; https:// Also you can use HOURS_PER_CURRENT_MONTH instead
const RuleManufacture *item = _production->getRules();
int numEngineers = _production->getAssignedEngineers();
https:// how many manHours will be consumed for this task per average month
int manHoursPerMonth = HOURS_PER_MONTH * numEngineers;
if (!_production->getInfiniteAmount())
{
int manHoursRemainig = item->getManufactureTime() * (_production->getAmountTotal() - _production->getAmountProduced());
manHoursPerMonth = std::min(manHoursPerMonth, manHoursRemainig);
}
https:// how many items will be manufactured in this month
float itemsPerMonth = (float)manHoursPerMonth / (float)item->getManufactureTime();
if (itemsPerMonth < 1.0f) itemsPerMonth = 1.0f;
https:// final calculation
int saleValue = _btnSell->getPressed() ? _producedItemsValue : 0;
int consumedValue = item->getManufactureCost() + _usedItemsValue;
int salaryCost = _game->getRuleset()->getEngineerCost() * numEngineers;
float livingCost = ((float)_totalLivingQuartersMaintenance * numEngineers) / _totalLivingSpace;
float workshopCost = ((float)_totalWorkshopMaintenance * (numEngineers + item->getRequiredSpace()) / _totalWorkshopSpace;
return (saleValue - consumedValue) * itemsPerMonth - (salaryCost + livingCost + workshopCost);
}