Perfect Dark (ryandwyer/perfect-dark decompilation, ntsc-final)

The Perfect Dark decompilation builds six ROMs and defaults to ntsc-final, which its README describes as "NTSC 8.7 final" beside ntsc-1.0, "the initial, buggy release"; the Makefile sets VERSION = 2 for it. perfect-dark/source-version

Value: ntsc-final

Every other claim here reads the code the ntsc-final build compiles. The #if VERSION branches for the PAL and Japanese ROMs differ in places these claims name (PAL's 50 Hz constants, the Japanese autoaim scales).

Cited by: Perfect Dark

Perfect Dark's standard autoaim, for a gun whose autoaim is on, scores each character on screen and takes the highest score. It skips teammates, the dead and dying, and anyone not holding a gun (unless flagged CHRCFLAG_FORCEAUTOAIM). A candidate needs a clear line from the player, its screen center in the middle half of the screen's width, and its height reaching into the band from 17.5% to 82.5% of the screen's height; the screen's center must lie within 1.5 of its screen widths of its middle, times a solo scale (perfect-dark/autoaim-scale). The score is 1 when the screen's center x lies between the target's left and right screen edges, and otherwise falls off with the gap over that margin. The walk runs from the end of a list props_sort orders by prop->z, largest first, which the decompilers' comment calls "furthest first"; since a score of 1 ends the walk, the nearest such target wins on that reading. Doom traces ahead and 5.625° to each side for a target, and Duke Nukem 3D's aim takes the target within 8.4° of the facing that is nearest along it. perfect-dark/autoaim

About: Perfect Dark Autoaim

Value: 1.5 target widths

sp8c and sp84 are the target's left and right edges on screen, spa0 its center, and sp48 the margin; the names are the decompilers' placeholders. The score is 1 within the target's width and falls linearly by the gap over the margin outside it. The window is the whole screen for a weapon bgun_allows_fullscreen_autoaim allows. A melee function skips the standard branch, and the CMP150's secondary function (target lock) has its own. The multiplayer margin is unscaled. Duke's cone is an angle around the facing; Perfect Dark's window is a share of the screen and scales with the target's size on it.

Cited by: Perfect Dark

In solo Perfect Dark the autoaim margin (perfect-dark/autoaim) is multiplied by g_AutoAimScale, which lv_update_solo_handicaps sets by difficulty: 1.5 on Agent, 0.75 on Special Agent, 0.2 on Perfect Agent, and 1 on the Perfect Dark difficulty; the ntsc-final build takes the non-Japanese values (g_Jpn is false). Co-op and Counter-Operative use their own values. perfect-dark/autoaim-scale

About: Perfect Dark Autoaim

{
 "agent": 1.5,
 "special-agent": 0.75,
 "perfect-agent": 0.2,
 "perfect-dark": 1
}

The function runs every tick of a level (lv.c L2297). Perfect Dark is the custom difficulty unlocked by finishing the game, and its autoaim margin is five times Perfect Agent's. In the Japanese build Special Agent and Perfect Agent take 1.1 and 0.75 when g_Jpn is set.

Cited by: Autoaim, Difficulty level, Perfect Dark

Perfect Dark's autoaim moves the crosshair, not the view: once a target is picked, bmove_update_autoaim_x_prop and _y_prop set the aim point to the target's screen center (clamped to the window), and a new target replaces the old only after a 30/60 s hold; bgun_swivel then eases the crosshair toward the point, keeping a fraction crossdamp of the gap each 1/240 s (a unit the decompilers' comments give). On NTSC that fraction, autoaimdamp, falls by 0.00032 a 60th of a second while autoaim holds a target, from at most 0.979 (it climbs back there while none is held) to 0.963, so the pull strengthens over up to 50/60 s (computed); at 0.963 the crosshair closes 14% of the gap each 60th of a second (1 − 0.963⁴, computed). The shot leaves through the crosshair's position plus a random spread. Doom's bullet keeps the player's facing and takes only a vertical slope, and Duke Nukem 3D turns the shot itself to the target's angle in the call that fires it. perfect-dark/autoaim-pull

About: Perfect Dark Autoaim

Value: 0.963 kept per 1/240 s

The swivel branch also needs movedata.canautoaim, both props set, and the weapon's INVAIMFLAG_AUTOAIM aim flag (bondmove.c L1754-L1760). PAL uses 0.955 and 0.974 with a larger step. The x and y holds run on separate timers. Holding the aim button switches to manual aiming, which moves the crosshair with the stick instead. The CMP150's target lock swivels with a fixed 0.915.

Cited by: Autoaim, Perfect Dark

Perfect Dark's chr_damage scales a hit by the body part (hitpart) it struck: a head hit is multiplied by 4 and a torso hit doubled, the limbs and pelvis keep the damage, and a hit on the held gun or a hat deals none. Outside normal multiplayer a gun shot fired by a player multiplies a head hit by a further 25 (headshotdamagescale), 100 in all, unless a shield took it; a Skedar's head is only doubled, and its tail takes 10 times. A hit with no part (HITPART_GENERAL, as when a guard's bullet hits the player) is halved and then doubled as the torso, so it keeps its damage. Doom's P_LineAttack passes a bullet's damage to the thing it hits with no body part. perfect-dark/hit-location

About: Perfect Dark Locational damage

{
 "head": 4,
 "head-player-shot": 100,
 "torso": 2,
 "limbs": 1,
 "gun": 0
}

The player's own shots get their hitpart from the model part the trace struck (model_test_for_hit in chr.c, then chr_hit). Counter-Operative applies the 25 to shots by the Bond player. A thrown combat knife's head hit doubles again. The pelvis counts as body in the shot statistics but takes no multiplier. Melee hits (isshoot false) take the 4 but not the 25.

Cited by: Perfect Dark

The Falcon 2's single shot in Perfect Dark carries a damage of 1 (invfunc_falcon2_singleshot), read by gset_get_damage. A guard adds each hit to its damage against a maxdamage that chr_allocate sets to 4 (a level's AI script can set another), and chr_react_to_damage starts its death once damage reaches it; so on Perfect Agent a default guard takes 4 Falcon 2 shots to a limb, 2 to the torso, or 1 to the head (computed). The player's health starts at 1, and a hit takes damage × 0.125 from it, so a guard's Falcon 2 bullet takes an eighth on Perfect Agent (computed). Each Doom pistol bullet deals 5, 10, or 15 against a zombieman's 20. perfect-dark/falcon2-damage

About: Perfect Dark Damage formula

Value: 1 damage

The counts leave out armour (a negative starting damage) and shields. gset_get_damage doubles the damage while the current player is firing both hands; it reads the player's hands even when a guard's shot asks, so in the code a guard's bullet is doubled too while the player fires two guns at once. Not checked in play. The player's healthscale and armour are 1 unless a level changes them.

Cited by: Perfect Dark

Solo Perfect Dark scales damage by difficulty in lv_update_solo_handicaps, which runs every tick: a guard's hit on the player is multiplied by 0.5 on Agent, 0.6 on Special Agent, and 1 on Perfect Agent (and on the Perfect Dark difficulty, times its own enemy-damage setting); the player's shots are doubled on Agent; and explosions hurt the player 0.25 times on Agent and 0.75 times on Special Agent. On Agent the scales for the damage the player takes, from guards and from explosions, shrink further once health plus shield is at or below 0.6, falling linearly to half at 0.125, so 0.25 for a guard's hit (computed); the player's ×2 on its own shots stays fixed. Doom halves all damage to the player on its easiest skill, sk_baby. perfect-dark/difficulty-damage

About: Perfect Dark Difficulty level

{
 "agent": 0.5,
 "special-agent": 0.6,
 "perfect-agent": 1
}

lv_update_solo_handicaps also sets enemy accuracy (0.6, 0.8, 1.175, 1.1), ammo pickups (2, 1.5, 1, 1), and autogun and CCTV scales per difficulty; co-op and Counter-Operative read their own rows. The Perfect Dark difficulty's enemy health divides the player's damage to guards (pdmode_get_enemy_health). Health and shield are fractions of 1.

Cited by: Difficulty level, Perfect Dark

A Perfect Dark combat simulant keeps a shootdelaytimer60 per target: it resets to 0 when the simulant picks a new target, counts up in 60ths of a second while the target is in sight, and counts back down to 0 while it isn't. Unless a burst or the Cyclone's secondary discharge is already under way (burstsdone above 0 or cyclonedischarging), which keeps it firing without the test, the simulant opens fire only once the timer reaches its difficulty's shootdelay60: 90 (1.5 s) for Meat, 60 for Easy, 30 for Normal, 15 for Hard, and 0 for Perfect and Dark, on NTSC; the target must also be within 45/256 of a turn (63°, computed) of its facing, unless the simulant is dizzy. Doom gives each monster a reactiontime at spawn (8 for the zombieman, 0 on Nightmare), counted down once per A_Chase call, and refuses a ranged attack until it reaches 0, unless the monster has been hit since it last checked (MF_JUSTHIT). perfect-dark/simulant-shoot-delay

About: Perfect Dark Reaction delay

{
 "meat": 90,
 "easy": 60,
 "normal": 30,
 "hard": 15,
 "perfect": 0,
 "dark": 0
}

Thrown weapons and punches test the same timer (bot.c L3432, L3542). The table's other columns set how fast and how long a simulant takes to zero in its aim (minzerospeed, maxzerospeed, zerotime60), which this claim doesn't cover. PAL's TICKS scales each delay by 50/60. Doom's countdown runs per chase step, not per tic, and its melee check doesn't read reactiontime.

Cited by: Perfect Dark, Reaction delay