JOKTWWEJK at 14:42, 28 December 2025

2025-12-28T14:42:23Z

← Older revision		Revision as of 14:42, 28 December 2025
Line 13:		Line 13:
	Where other systems abstract all the variables of combat into things like "base attack bonus plus weapon modifier versus armour," Phoenix Command dives '''deep''' into the minutiae. Before you can roll the dice to fire a single bullet, you have to find the distance to your target, its size, its movement, visibility conditions, what firing stance you're in, how long you want to aim, cross-reference all of those on their respective tables, add the corresponding modifiers, and then consult the Odds of Hitting chart to see what you need to roll on d100 to actually hit the target. If you do hit, you now have to roll on the Hit Location table to see where among 39 locations you've hit, subtract your weapon's Penetration from the Protection Factors of your target's armour and cover to find your Effective Penetration, which affects how much net damage you finally do, and then determine if the shot knocked down the target and/or incapacitated him in some fashion. And that's before going into how burst and automatic fire add even more modifiers into this mix.		Where other systems abstract all the variables of combat into things like "base attack bonus plus weapon modifier versus armour," Phoenix Command dives '''deep''' into the minutiae. Before you can roll the dice to fire a single bullet, you have to find the distance to your target, its size, its movement, visibility conditions, what firing stance you're in, how long you want to aim, cross-reference all of those on their respective tables, add the corresponding modifiers, and then consult the Odds of Hitting chart to see what you need to roll on d100 to actually hit the target. If you do hit, you now have to roll on the Hit Location table to see where among 39 locations you've hit, subtract your weapon's Penetration from the Protection Factors of your target's armour and cover to find your Effective Penetration, which affects how much net damage you finally do, and then determine if the shot knocked down the target and/or incapacitated him in some fashion. And that's before going into how burst and automatic fire add even more modifiers into this mix.

	PC is the type of system that really needs automation to run at a meaningful pace, especially when you start using the Advanced combat mechanics. Yes, that mess above is from the ''Basic'' rules. The Advanced Damage Tables have ''53'' ~~hit~~ locations and ''40'' damage tables that can account for how the shot glances off or shatters bones on impact and what direction the bullet enters the body (front, side, oblique).		PC is the type of system that really needs automation to run at a meaningful pace, especially when you start using the Advanced combat mechanics. Yes, that mess above is from the ''Basic'' rules. The Advanced Damage Tables have ''53'' ht locations and ''40'' damage tables that can account for how the shot glances off or shatters bones on impact and what direction the bullet enters the body (front, side, oblique).

			One of the flaws of the system is it's inability to model literally anything other than "human baseliner infantryman on foot". Game has no stats for land vehicles - like cars, tanks or APCs, despite game having stats for anti-tank weapons and [[fail\|including cars in some pre-built encounters]]. Game also has no stats for [[robot]]s, [[cyborg]]s, or [[Transhumanism\|human subspecies]]; a glaring flaw for it's high-tech expansion. There's also no stats for animals or fantastical creatures. And while there are some rules for aircraft or artillery support, it's off-the-map support.

	[[Category:Roleplaying]]		[[Category:Roleplaying]]
	[[Category:Wargames]]		[[Category:Wargames]]

Sdhjk: Created page with "{{Game Infobox |name = Phoenix Command |type = RPG |picture = |publisher = Leading Edge Games |system = Percentile |authors = Barry Nakazono and David McKenzie |year = 1986 (1st edition), 1987 (2nd), 1989 (3rd), 1991 (4th) }} '''Phoenix Command''' is a legendarily-complicated RPG tabletop combat simulator with RPG elements developed and first published by Leading Edge Games in 1986. It exists because its writers, Barry Nakazono and David McKenzie, wanted to..."

2025-09-25T16:10:19Z

Created page with "{{Game Infobox |name = Phoenix Command |type = RPG |picture = |publisher = Leading Edge Games |system = Percentile |authors = Barry Nakazono and David McKenzie |year = 1986 (1st edition), 1987 (2nd), 1989 (3rd), 1991 (4th) }} '''Phoenix Command''' is a legendarily-complicated <s>RPG</s> tabletop combat simulator with RPG elements developed and first published by Leading Edge Games in 1986. It exists because its writers, Barry Nakazono and David McKenzie, wanted to..."

New page

{{Game Infobox
|name = Phoenix Command
|type = [[RPG]]
|picture =
|publisher = Leading Edge Games
|system = Percentile
|authors = Barry Nakazono and David McKenzie
|year = 1986 (1st edition), 1987 (2nd), 1989 (3rd), 1991 (4th)
}}

'''Phoenix Command''' is a legendarily-complicated <s>RPG</s> tabletop combat simulator with RPG elements developed and first published by Leading Edge Games in 1986. It exists because its writers, Barry Nakazono and David McKenzie, wanted to answer the question of "what happens to your character when he gets shot?" with something other than "he loses 2d6 hit points" and solved it by making a bajillion cross-referenced charts and tables to create the most authentic to real life experience they could (little surprise that Nakazono went on to become an actual rocket scientist). [https://forum.rpg.net/index.php?threads/phoenix-command-its-awesome.534963/ This RPG.net thread] says it all.

Where other systems abstract all the variables of combat into things like "base attack bonus plus weapon modifier versus armour," Phoenix Command dives '''deep''' into the minutiae. Before you can roll the dice to fire a single bullet, you have to find the distance to your target, its size, its movement, visibility conditions, what firing stance you're in, how long you want to aim, cross-reference all of those on their respective tables, add the corresponding modifiers, and then consult the Odds of Hitting chart to see what you need to roll on d100 to actually hit the target. If you do hit, you now have to roll on the Hit Location table to see where among 39 locations you've hit, subtract your weapon's Penetration from the Protection Factors of your target's armour and cover to find your Effective Penetration, which affects how much net damage you finally do, and then determine if the shot knocked down the target and/or incapacitated him in some fashion. And that's before going into how burst and automatic fire add even more modifiers into this mix.

PC is the type of system that really needs automation to run at a meaningful pace, especially when you start using the Advanced combat mechanics. Yes, that mess above is from the ''Basic'' rules. The Advanced Damage Tables have ''53'' hit locations and ''40'' damage tables that can account for how the shot glances off or shatters bones on impact and what direction the bullet enters the body (front, side, oblique).

[[Category:Roleplaying]]
[[Category:Wargames]]

Phoenix Command - Revision history

JOKTWWEJK at 14:42, 28 December 2025