Command & Conquer (the Remastered Collection's TiberianDawn.dll source, 2020)

Command & Conquer came out on 31 August 1995. cnc/release

Value: 1995-08-31

Wikidata gives one publication date at day precision, with one reference and no platform qualifier.

Cited by: Command & Conquer

The atlas reads Command & Conquer through the source of TiberianDawn.dll, the game's code in the 2020 Remastered Collection, which Electronic Arts released under the GPL version 3 with additional terms. The files keep Westwood's 1995 headers beside dated comments and guards for the remaster's changes, so a claim here describes the remaster's code and names any remaster change it rests on. cnc/source-version

The repository holds no game data, so values the 1995 game read from its data files at start (if any override the code's tables) aren't covered here.

Cited by: Command & Conquer

In the remaster's code, a harvester carries at most 28 steps of Tiberium (STEP_COUNT). Each time its harvest timer runs out while it stands on Tiberium short of a full load, it lifts (the cell's OverlayData mod 6) + 1 steps from the cell, no more than the room left, and the timer restarts at TICKS_PER_SECOND, 15 game ticks; the code's comment calls this lifting a complete "level" of 6 steps or a partial one. Dune II's harvester instead fills to 100 units by a random 0 or 1 per harvest call. cnc/harvest

About: Command & Conquer Resource harvesting

{
 "capacity": 28,
 "perHarvest": [
  1,
  6
 ],
 "harvestTicks": 15
}

CellClass::Reduce_Tiberium (CELL.CPP, lines 1483–1500) takes the requested steps when the cell's OverlayData is larger, and otherwise clears the cell and returns its OverlayData, so the last lift from a cell yields one step less than its level number suggests, and a cell at 0 yields nothing. How fast game ticks pass depends on the game speed setting, which the atlas hasn't read.

Cited by: Command & Conquer, Resource harvesting

In the remaster's code, a refinery empties a docked harvester one step at a time, and each step pays its house 25 credits if the house is human: computed, 700 for a full load of 28, which matches Dune II's 100 units at 7 credits. A computer house gets 708 credits a step in a normal (single-player) game, from a formula the remaster's comment calls "wrong" but kept "to not break missions", and 33 in multiplayer, a correction the comment dates to the remaster (14 May 2020). Credits above the house's storage capacity are lost. cnc/refine

About: Command & Conquer Resource harvesting

{
 "creditsPerStep": 25,
 "fullLoadCredits": 700,
 "aiCreditsPerStepCampaign": 708,
 "aiCreditsPerStepMultiplayer": 33
}

The "original" formula's operator precedence divides only the bonus third by 28, so a computer harvester's full load is worth 28 × 708 = 19,824 credits in a single-player mission (computed), before the storage cap. The comment's word "Original" is the remaster programmer's; the atlas hasn't seen the 1995 executable. Dune II's computer house gets 6 to 9 credits a unit (dune2/refine).

Cited by: Command & Conquer

In the remaster's code, a factory splits every build into 108 steps and pays in installments: each step costs the unpaid balance ÷ the steps left, and when the house can't pay it, the step is undone and the factory tries again at the next one. The build time in game ticks starts as the item's cost in credits, grows when the house's power fraction is below full (× 256/171), below half (× 256/103), or zero (× 4), and is divided by 108 into ticks per step (1 to 255). A human player's factory runs its step timer once per factory of that kind the house owns each tick; the code's comment says this acceleration "applies only to human players". Computed: for a human player's structure from one factory at full power, an item costing C credits takes 108 × ⌊C ÷ 108⌋ ticks, at least 108 and at most 27,540. Dune II also pays as it builds, but each tick costs cost ÷ build time, and a player's build goes on hold when the money runs out. cnc/build-progress

About: Command & Conquer Construction

{
 "steps": 108,
 "ticksPerCredit": 1,
 "powerScale": {
  "belowFull": 1.497,
  "belowHalf": 2.485,
  "none": 4
 }
}

Time_To_Build also slows the computer's structures on easy and normal difficulty, speeds units only Nod can own by a quarter (the comment says they arrive by airfield), and scales the computer's time by its IQ through RULES.H, a file headed 1996 and Red Alert's; this claim covers a human player's build of a structure, which none of those touch. Cost_Of returns the type's cost; CostBias, the house's cost multiplier, is set elsewhere. When the last step completes, the factory pays whatever balance is left (FACTORY.CPP line 294). Abandoning a build refunds what was paid (lines 588–589).

Cited by: Command & Conquer

In the remaster's code, a structure can be placed where every cell of its footprint, its bib included, is clear: no object, no wall, no owned bib, and ground marked buildable (clear land or road; not Tiberium, beach, rock, or water). For a human house, one of the eight cells around some footprint cell, corners included, must also hold one of the house's buildings or be a cell the house owns, which its walls and bibs are; a computer house's placement skips that check. Dune II's rule is also adjacency with corners counted and also skipped for the computer, but on rock, concrete slab, or destroyed wall, with the construction yard exempt. cnc/placement

About: Command & Conquer Structure placement

The remaster client's Place call (DLLInterface.cpp) and the game's PLACE event both run Place_Object. The placement cursor and the client's placement map run their own copies of the adjacency test (DisplayClass::Passes_Proximity_Check, behind the remaster's USE_RA_AI guard, and DLLExportClass's placement distances); the check that decides is the one Place_Object runs. A construction yard deployed from an MCV doesn't go through Place_Object, and the atlas hasn't read that path. The 1995 concrete-slab check in Legal_Placement sits in an #ifdef NEVER block; whether a missing slab costs health, as in Dune II, the atlas hasn't checked.

Cited by: Command & Conquer

In the remaster's code, Tiberium grows and spreads on its own. Each map logic pass scans 30 of the 64 × 64 cells, starting at the cell where the last pass stopped (so 29 new ones), and collects up to 50 Tiberium cells below level (OverlayData) 11 and up to 50 spread sources: Tiberium cells above level 6, and blossom trees whatever their level, each entered three times. After each full sweep, computed as 142 passes, a random collected cell grows one level, and one heavy cell seeds level-1 Tiberium on a random empty neighbor of clear land; with fast growth on, as by default, or in any multiplayer game, each happens twice, and in the remaster's own multiplayer (GAME_GLYPHX_MULTIPLAYER) a change its comment dates to 1 July 2020 adds (Tiberium setting − 1) × 2 more. A cell harvested to empty is cleared and holds Tiberium again only if a neighbor seeds it. Dune II's spice doesn't grow: during play OpenDUNE's code adds spice only where a spice bloom bursts, filling a circle of radius 5, or where a harvester carrying 32 or more units is destroyed, filling a circle of radius load ÷ 32. cnc/tiberium-growth

About: Command & Conquer Resource harvesting

{
 "cellsPerPass": 30,
 "newCellsPerPass": 29,
 "mapCells": 4096,
 "passesPerSweep": 142,
 "maxLevel": 11,
 "spreadAbove": 6
}

The remaster's multiplayer tries depend on its Tiberium setting (MPlayerTiberium), which the atlas hasn't traced to the client's options; a setting of 1 or less adds nothing. A full collection array replaces a random entry, so later cells in a sweep can displace earlier ones. By C operator precedence, the spread test's IsTSpread && binds only to the Tiberium half, so blossom trees are collected even with spread off, and at any Tiberium level. The pass count assumes Map.Logic runs once per game logic tick; how fast ticks pass depends on the game speed.

Cited by: Command & Conquer