=Overview=
The player setting gives account of how many players are present in one game. It has impact on monsters' hit points, experience gained and drops. The default player setting is 1. However, with every player joining a multiplayer game the player setting is increased by one up till a maximum of 8 (i.e. the maximum number of players in one game). In Single Player mode, open battle.net and non battle.net Multiplayer mode the player setting can be changed by the [[#PlayersX|Players X Command]].

Common abbreveations are "pX" or "/pX", e.g. "I cleared the whole Throne Room on p8", meaning that all of Baal's minion waves were defeated on a player setting of 8 players.

=Influence on game mechanics=
In general one could say: the higher the player setting, the higher the monsters' hit points, the amount of experience gained and the frequency/amount of drops. Basically that means:
*You'll level faster
*You'll need more time for killing monsters
*You'll find more items
'''Note:''' The player setting does '''not''' influence the quality of the dropped items! There's an entirely different algorithm for that.

To make things a bit more difficult: there is a distinction between near players in a party with you and unpartied players. That will be of importance for some game aspects.

===Monsters' Hit Points===
Each monster's Hit Points are multiplied by the number of players in the game according to a certain formula, which differs from version to version:

1.00-1.08: '''Hit Points = X * n''' 
1.09: '''see list below''' 
1.10+ (any): '''Hit Points = X * (n + 1) / 2'''

where
X = base Hit Points
n = # of players in game

Assorted in a table it looks like this:
{|
!Player setting
!HP 1.08
!HP 1.09
!HP 1.10+
|-
|1
|100%
|100%
|100%
|-
|2
|200%
|200%
|150%
|-
|3
|300%
|300%
|200%
|-
|4
|400%
|400%
|250%
|-
|5
|500%
|450%
|300%
|-
|6
|600%
|520%
|350%
|-
|7
|700%
|570%
|400%
|-
|8
|800%
|620%
|450%
|-
|10
|
|700%
|
|-
|20
|
|1200%
|
|-
|40
|
|2200%
|
|-
|64
|
|3400%
|
|-
|colspan="4" |(HPs increase by 50% per player past 10 in 1.09a/b)
|}

===Experience===
With increasing player settings the amount of Experience gained also increases according to a certain formula, which differs from version to version:

1.00-1.08: '''Experience = X * (2n + 1) / 3''' 
1.09 (any): '''see list below''' 
1.10+ (any): '''Experience = X * (n + 1) / 2'''

where
X = base experience
n = # of players in the game

So it's basically the same numbers as for the Hit Points calculations.

Here's the table:
{|
!Player setting
!XP 1.08
!XP 1.09
!XP 1.10+
|-
|1
|100%
|100%
|100%
|-
|2
|167%
|175%
|150%
|-
|3
|233%
|250%
|200%
|-
|4
|300%
|325%
|250%
|-
|5
|367%
|375%
|300%
|-
|6
|433%
|400%
|350%
|-
|7
|500%
|425%
|400%
|-
|8
|567%
|450%
|450%
|-
|10
|
|455%
|
|-
|20
|
|505%
|
|-
|40
|
|605%
|
|-
|64
|
|725%
|
|-
|colspan="4" |(XP increases by 5% per player past 10 in 1.09a/b)
|}

===Items===
As already stated, the player setting will not affect the item quality, but will affect the amount of items dropped.

So how does the player setting affect monster drops? First, we'll have to introduce a term called "nodrop". Every monster has a certain chance for this "nodrop", that is the chance to drop nothing at all. The greater this number, the greater the chance to drop nothing. This value is cut down with increasing player settings according to the following formula '''''in V1.11''''' (for basics on item generation, nodrop an so on see the [http://forums.diabloii.net/showthread.php?t=392254 Item Generation Tutorial for Patch 1.11] on the DII Strategy Forum from Warrior of Light):

'''NewNoDrop=int( ProbSum/(1/((NoDrop/(NoDrop+ProbSum))^N)-1) )''', 
where N=int(1+AdditionalPlayers/2+ClosePartiedPlayers/2), 
AdditionalPlayers — the number of all additional players in the game, where the monster is killed, 
ClosePartiedPlayers — the number of players in your party near you (not far than two screens away), 
ProbSum=Prob1+Prob2+Prob3+...+Prob10, 
int — operation of truncating fractional part of a number.

This looks pretty complicated, so for the sake of comprehensibility let's just say: 

*'''For normal monsters:''' The more players, the more drops.
*'''For Super Uniques''' (like Pindleskin), '''Uniques and Champions''': player setting is irrelevant.
**Super Uniques will always drop two items.
**Uniques will always drop one item.
**Champions will always drop one item.
*'''Bosses''': "nodrop" will be reduced to zero for 5 unpartied players or 3 near players in the same party. In Single Player the difference between the drops for 3 player setting and 5 player setting is only marginal though.

Note: The formula implies, that for unpartied players (and simulated players via the Players X Command) only every second additional players has impact on drop rates. So the steps for more drops are '''players 3''', '''players 5''' and '''players 7'''. 
In other words: players 8 and players 7 have the same drop rates, players 6 and 5, players 4 and 3, and players 2 and 1.
Note that the amount of Experience gained and monsters' Hit Points are nonetheless different for each player setting (as stated above).

===Skills and Abilities===
A frequent question when it comes to player setting is, which skills and weapon abilties that correlate with a target's Hit Points scale with the player setting. For example, the Necromancer's Corpse Explosion deals damage depending on the corpse's HPs (between 60% and 100%). Does the skill take the base HPs or the modified (higher) HPs on higher player settings? Unfortunately the answer is: Depends on what version you are using. Here's a list of skills and abilities, that correlate with a target's HPs.

''The list is not complete yet. Feel free to add any information you have about scaling.''

{|style="text-align:center"
!rowspan="2"|Skill/Ability
!colspan="12"|scales in
|-
!1.10b+
!1.10a
!1.09
!1.08
!1.07
!1.06
!1.05
!1.04
!1.03
!1.02
!1.01
!1.00
|-
|style="text-align:left"|Static Field
|<nowiki>+</nowiki>
|<nowiki>+</nowiki>
|<nowiki>+</nowiki>
|<nowiki>+</nowiki>
|<nowiki>+</nowiki>
|<nowiki>+</nowiki>
|<nowiki>+</nowiki>
|<nowiki>+</nowiki>
|<nowiki>+</nowiki>
|<nowiki>+</nowiki>
|<nowiki>+</nowiki>
|<nowiki>+</nowiki>
|-
|style="text-align:left"|Corpse Explosion
|<nowiki>-</nowiki>
|<nowiki>+</nowiki>
|<nowiki>-</nowiki>
|<nowiki>-</nowiki>
|<nowiki>-</nowiki>
|<nowiki>-</nowiki>
|<nowiki>-</nowiki>
|<nowiki>-</nowiki>
|<nowiki>-</nowiki>
|<nowiki>+</nowiki>
|<nowiki>+</nowiki>
|<nowiki>+</nowiki>
|-
|style="text-align:left"|Death Sentry
|<nowiki>-</nowiki>
|<nowiki>+</nowiki>
|<nowiki>-</nowiki>
|<nowiki>-</nowiki>
|<nowiki>-</nowiki>
|n.a.
|n.a.
|n.a.
|n.a.
|n.a.
|n.a.
|n.a.
|-
|style="text-align:left"|Crushing Blow
|<nowiki>-</nowiki>
|?
|?
|?
|?
|?
|?
|?
|?
|?
|?
|?
|-
|style="text-align:left"|Summoned minions (HPs)
|<nowiki>-</nowiki>
|<nowiki>-</nowiki>
|<nowiki>+</nowiki>
|?
|?
|?
|?
|?
|?
|?
|?
|?
|}



=The Players X Command=
From version 1.09 onward, the player setting can be changed arbitrarily in Single Player mode, open battle.net and non battle.net Mulitplayer mode. In order to do so, one has to enter a certain command while in game. This is done by hitting "Enter", typing the players X command, and confirming by hitting "Enter" again (yes, it's the normal shoutbox usage). The command differs slightly for the different versions of Diablo II.

In genereal the Players X command simulates an amout of players in the game equal X, although less players are actually in game. X cannot be lower than the actual number of players in game. For example, if you're playing with 2 friends a multiplayer game via TCP/IP, you can only choose a number equal or greater than 3. All other commands will be ignored.

'''The Players X Command only simulates unpartied players.''' (Important for drop mechanics as explained above)

Note that the Players X command doesn't affect monsters that have already spawned by the time you type the command. I'm not entirely sure about the radius in which monsters spawn around you, but according to jiansonz's testings it's somewhat smaller than the distance from the stairs in Durance level 3 to Mephisto's spawning point (meaning that one could still tune down the player setting shortly after entering Durance 3 and thus have the Council spawn on a different player setting than Mephisto himself). To make sure every monster is affected, typing the command while still in town is recommended.

Players X does however affect all clickable items (i.e. logs, chests, urns etc.) immediately. In theory one could clear the whole area on p1, then set the player settings to 8 for maximised drops (i.e. minimised NoDrop) and pop all chests, urns etc. only then. This is in no way illegal, but considered cheesy by most players in the SPF. Ususall this (ab)use of the Players X command is prohibited in SPF tournaments.

In V1.09, when hit points of your summoned minions (e.g. Golems, Valkyrie) scaled with the player setting, it was useful to change the player setting to maximum before casting the minion and then immediately switch back to a lower player setting, which is also considered as cheesy. In V1.10 minions' hit points no longer scale up with the player setting.

===Versions 1.00 to 1.08===
No players X command available.

===Version 1.09a/b===
The command is '''''players X''''', where X can be any number between 1 and 64. You won't get any confirmation that the player setting has changed.

===Version 1.09c/d===
The command is '''''players X''''', where X can be any number between 1 and 8. You won't get any confirmation that the player setting has changed.

===Versions 1.10 and 1.11===
The command is '''''/players X''''' or '''''/playersX''''', where X can be any number between 1 and 8. You will get the confirmation ''players set to X'' on your screen. 
This command is available in all versions of 1.10 and 1.11.

Player Settings

2008-02-06T02:05:41Z

Joshgt2: /* Items */

=Overview=
The player setting gives account of how many players are present in one game. It has impact on monsters' hit points, experience gained and drops. The default player setting is 1. However, with every player joining a multiplayer game the player setting is increased by one up till a maximum of 8 (i.e. the maximum number of players in one game). In Single Player mode, open battle.net and non battle.net Multiplayer mode the player setting can be changed by the [[#PlayersX|Players X Command]].

Common abbreveations are "pX" or "/pX", e.g. "I cleared the whole Throne Room on p8", meaning that all of Baal's minion waves were defeated on a player setting of 8 players.

=Influence on game mechanics=
In general one could say: the higher the player setting, the higher the monsters' hit points, the amount of experience gained and the frequency/amount of drops. Basically that means:
*You'll level faster
*You'll need more time for killing monsters
*You'll find more items
'''Note:''' The player setting does '''not''' influence the quality of the dropped items! There's an entirely different algorithm for that.

To make things a bit more difficult: there is a distinction between near players in a party with you and unpartied players. That will be of importance for some game aspects.

===Monsters' Hit Points===
Each monster's Hit Points are multiplied by the number of players in the game according to a certain formula, which differs from version to version:

1.00-1.08: '''Hit Points = X * n''' 
1.09: '''see list below''' 
1.10+ (any): '''Hit Points = X * (n + 1) / 2'''

where
X = base Hit Points
n = # of players in game

Assorted in a table it looks like this:
{|
!Player setting
!HP 1.08
!HP 1.09
!HP 1.10+
|-
|1
|100%
|100%
|100%
|-
|2
|200%
|200%
|150%
|-
|3
|300%
|300%
|200%
|-
|4
|400%
|400%
|250%
|-
|5
|500%
|450%
|300%
|-
|6
|600%
|520%
|350%
|-
|7
|700%
|570%
|400%
|-
|8
|800%
|620%
|450%
|-
|10
|
|700%
|
|-
|20
|
|1200%
|
|-
|40
|
|2200%
|
|-
|64
|
|3400%
|
|-
|colspan="4" |(HPs increase by 50% per player past 10 in 1.09a/b)
|}

===Experience===
With increasing player settings the amount of Experience gained also increases according to a certain formula, which differs from version to version:

1.00-1.08: '''Experience = X * (2n + 1) / 3''' 
1.09 (any): '''see list below''' 
1.10+ (any): '''Experience = X * (n + 1) / 2'''

where
X = base experience
n = # of players in the game

So it's basically the same numbers as for the Hit Points calculations.

Here's the table:
{|
!Player setting
!XP 1.08
!XP 1.09
!XP 1.10+
|-
|1
|100%
|100%
|100%
|-
|2
|167%
|175%
|150%
|-
|3
|233%
|250%
|200%
|-
|4
|300%
|325%
|250%
|-
|5
|367%
|375%
|300%
|-
|6
|433%
|400%
|350%
|-
|7
|500%
|425%
|400%
|-
|8
|567%
|450%
|450%
|-
|10
|
|455%
|
|-
|20
|
|505%
|
|-
|40
|
|605%
|
|-
|64
|
|725%
|
|-
|colspan="4" |(XP increases by 5% per player past 10 in 1.09a/b)
|}

===Items===
As already stated, the player setting will not affect the item quality, but will affect the amount of items dropped.

So how does the player setting affect monster drops? First, we'll have to introduce a term called "nodrop". Every monster has a certain chance for this "nodrop", that is the chance to drop nothing at all. The greater this number, the greater the chance to drop nothing. This value is cut down with increasing player settings according to the following formula '''''in V1.11''''' (for basics on item generation, nodrop an so on see the [http://forums.diabloii.net/showthread.php?t=392254 Item Generation Tutorial for Patch 1.11] on the DII Strategy Forum from Warrior of Light):

'''NewNoDrop=int( ProbSum/(1/((NoDrop/(NoDrop+ProbSum))^N)-1) )''', 
where N=int(1+AdditionalPlayers/2+ClosePartiedPlayers/2), 
AdditionalPlayers — the number of all additional players in the game, where the monster is killed, 
ClosePartiedPlayers — the number of players in your party near you (not far than two screens away), 
ProbSum=Prob1+Prob2+Prob3+...+Prob10, 
int — operation of truncating fractional part of a number.

This looks pretty complicated, so for the sake of comprehensibility let's just say: 

*'''For normal monsters:''' The more players, the more drops.
*'''For Super Uniques''' (like Pindleskin), '''Uniques and Champions''': player setting is irrelevant.
**Super Uniques will always drop two items.
**Uniques will always drop one item.
**Champions will always drop one item.
*'''Bosses''': "nodrop" will be reduced to zero for 5 unpartied players or 3 near players in the same party. In Single Player the difference between the drops for 3 player setting and 5 player setting is only marginal though.

Note: The formula implies, that for unpartied players (and simulated players via the Players X Command) only every second additional players has impact on drop rates. So the steps for more drops are '''players 3''', '''players 5''' and '''players 7'''. 
In other words: players 8 and players 7 have the same drop rates, players 6 and 5, players 4 and 3, and players 2 and 1.
Note that the amount of Experience gained and monsters' Hit Points are nonetheless different for each player setting (as stated above).

===Skills and Abilities===
A frequent question when it comes to player setting is, which skills and weapon abilties that correlate with a target's Hit Points scale with the player setting. For example, the Necromancer's Corpse Explosion deals damage depending on the corpse's HPs (between 60% and 100%). Does the skill take the base HPs or the modified (higher) HPs on higher player settings? Unfortunately the answer is: Depends on what version you are using. Here's a list of skills and abilities, that correlate with a target's HPs.

''The list is not complete yet. Feel free to add any information you have about scaling.''

{|style="text-align:center"
!rowspan="2"|Skill/Ability
!colspan="11"|scales in
|-
!1.10+
!1.09
!1.08
!1.07
!1.06
!1.05
!1.04
!1.03
!1.02
!1.01
!1.00
|-
|style="text-align:left"|Static Field
|<nowiki>+</nowiki>
|<nowiki>+</nowiki>
|<nowiki>+</nowiki>
|?
|?
|?
|?
|?
|?
|?
|?
|-
|style="text-align:left"|Corpse Explosion
|<nowiki>-</nowiki>
|<nowiki>-</nowiki>
|<nowiki>-</nowiki>
|<nowiki>-</nowiki>
|<nowiki>-</nowiki>
|<nowiki>-</nowiki>
|<nowiki>-</nowiki>
|<nowiki>-</nowiki>
|<nowiki>+</nowiki>
|<nowiki>+</nowiki>
|<nowiki>+</nowiki>
|-
|style="text-align:left"|Death Sentry
|<nowiki>-</nowiki>
|<nowiki>-</nowiki>
|<nowiki>-</nowiki>
|<nowiki>-</nowiki>
|n.a.
|n.a.
|n.a.
|n.a.
|n.a.
|n.a.
|n.a.
|-
|style="text-align:left"|Crushing Blow
|<nowiki>-</nowiki>
|?
|?
|?
|?
|?
|?
|?
|?
|?
|?
|-
|style="text-align:left"|Summoned minions (HPs)
|<nowiki>-</nowiki>
|<nowiki>+</nowiki>
|?
|?
|?
|?
|?
|?
|?
|?
|?
|}


=The Players X Command=
From version 1.09 onward, the player setting can be changed arbitrarily in Single Player mode, open battle.net and non battle.net Mulitplayer mode. In order to do so, one has to enter a certain command while in game. This is done by hitting "Enter", typing the players X command, and confirming by hitting "Enter" again (yes, it's the normal shoutbox usage). The command differs slightly for the different versions of Diablo II.

In genereal the Players X command simulates an amout of players in the game equal X, although less players are actually in game. X cannot be lower than the actual number of players in game. For example, if you're playing with 2 friends a multiplayer game via TCP/IP, you can only choose a number equal or greater than 3. All other commands will be ignored.

'''The Players X Command only simulates unpartied players.''' (Important for drop mechanics as explained above)

Note that the Players X command doesn't affect monsters that have already spawned by the time you type the command. I'm not entirely sure about the radius in which monsters spawn around you, but according to jiansonz's testings it's somewhat smaller than the distance from the stairs in Durance level 3 to Mephisto's spawning point (meaning that one could still tune down the player setting shortly after entering Durance 3 and thus have the Council spawn on a different player setting than Mephisto himself). To make sure every monster is affected, typing the command while still in town is recommended.

Players X does however affect all clickable items (i.e. logs, chests, urns etc.) immediately. In theory one could clear the whole area on p1, then set the player settings to 8 for maximised drops (i.e. minimised NoDrop) and pop all chests, urns etc. only then. This is in no way illegal, but considered cheesy by most players in the SPF. Ususall this (ab)use of the Players X command is prohibited in SPF tournaments.

In V1.09, when hit points of your summoned minions (e.g. Golems, Valkyrie) scaled with the player setting, it was useful to change the player setting to maximum before casting the minion and then immediately switch back to a lower player setting, which is also considered as cheesy. In V1.10 minions' hit points no longer scale up with the player setting.

===Versions 1.00 to 1.08===
No players X command available.

===Version 1.09a/b===
The command is '''''players X''''', where X can be any number between 1 and 64. You won't get any confirmation that the player setting has changed.

===Version 1.09c/d===
The command is '''''players X''''', where X can be any number between 1 and 8. You won't get any confirmation that the player setting has changed.

===Versions 1.10 and 1.11===
The command is '''''/players X''''' or '''''/playersX''''', where X can be any number between 1 and 8. You will get the confirmation ''players set to X'' on your screen. 
This command is available in all versions of 1.10 and 1.11.

Player Settings

2008-02-05T23:43:12Z

Joshgt2: /* Overview */

=Overview=
The player setting gives account of how many players are present in one game. It has impact on monsters' hit points, experience gained and drops. The default player setting is 1. However, with every player joining a multiplayer game the player setting is increased by one up till a maximum of 8 (i.e. the maximum number of players in one game). In Single Player mode, open battle.net and non battle.net Multiplayer mode the player setting can be changed by the [[#PlayersX|Players X Command]].

Common abbreveations are "pX" or "/pX", e.g. "I cleared the whole Throne Room on p8", meaning that all of Baal's minion waves were defeated on a player setting of 8 players.

=Influence on game mechanics=
In general one could say: the higher the player setting, the higher the monsters' hit points, the amount of experience gained and the frequency/amount of drops. Basically that means:
*You'll level faster
*You'll need more time for killing monsters
*You'll find more items
'''Note:''' The player setting does '''not''' influence the quality of the dropped items! There's an entirely different algorithm for that.

To make things a bit more difficult: there is a distinction between near players in a party with you and unpartied players. That will be of importance for some game aspects.

===Monsters' Hit Points===
Each monster's Hit Points are multiplied by the number of players in the game according to a certain formula, which differs from version to version:

1.00-1.08: '''Hit Points = X * n''' 
1.09: '''see list below''' 
1.10+ (any): '''Hit Points = X * (n + 1) / 2'''

where
X = base Hit Points
n = # of players in game

Assorted in a table it looks like this:
{|
!Player setting
!HP 1.08
!HP 1.09
!HP 1.10+
|-
|1
|100%
|100%
|100%
|-
|2
|200%
|200%
|150%
|-
|3
|300%
|300%
|200%
|-
|4
|400%
|400%
|250%
|-
|5
|500%
|450%
|300%
|-
|6
|600%
|520%
|350%
|-
|7
|700%
|570%
|400%
|-
|8
|800%
|620%
|450%
|-
|10
|
|700%
|
|-
|20
|
|1200%
|
|-
|40
|
|2200%
|
|-
|64
|
|3400%
|
|-
|colspan="4" |(HPs increase by 50% per player past 10 in 1.09a/b)
|}

===Experience===
With increasing player settings the amount of Experience gained also increases according to a certain formula, which differs from version to version:

1.00-1.08: '''Experience = X * (2n + 1) / 3''' 
1.09 (any): '''see list below''' 
1.10+ (any): '''Experience = X * (n + 1) / 2'''

where
X = base experience
n = # of players in the game

So it's basically the same numbers as for the Hit Points calculations.

Here's the table:
{|
!Player setting
!XP 1.08
!XP 1.09
!XP 1.10+
|-
|1
|100%
|100%
|100%
|-
|2
|167%
|175%
|150%
|-
|3
|233%
|250%
|200%
|-
|4
|300%
|325%
|250%
|-
|5
|367%
|375%
|300%
|-
|6
|433%
|400%
|350%
|-
|7
|500%
|425%
|400%
|-
|8
|567%
|450%
|450%
|-
|10
|
|455%
|
|-
|20
|
|505%
|
|-
|40
|
|605%
|
|-
|64
|
|725%
|
|-
|colspan="4" |(XP increases by 5% per player past 10 in 1.09a/b)
|}

===Items===
As already stated, the player setting will not affect the item quality, but will affect the amount of items dropped.

So how does the player setting affect monster drops? First, we'll have to introduce a term called "nodrop". Every monster has a certain chance for this "nodrop", that is the chance to drop nothing at all. The greater this number, the greater the chance to drop nothing. This value is cut down with increasing player settings according to the following formula '''''in V1.11''''' (for basics on item generation, nodrop an so on see the [http://forums.diabloii.net/showthread.php?t=392254 Item Generation Tutorial for Patch 1.11] on the DII Strategy Forum from Warrior of Light):

'''NewNoDrop=int( ProbSum/(1/((NoDrop/(NoDrop+ProbSum))^N)-1) )''', 
where N=int(1+AdditionalPlayers/2+ClosePartiedPlayers/2), 
AdditionalPlayers — the number of all additional players in the game, where the monster is killed, 
ClosePartiedPlayers — the number of players in your party near you (not far than two screens away), 
ProbSum=Prob1+Prob2+Prob3+...+Prob10, 
int — operation of truncating fractional part of a number.

This looks pretty complicated, so for the sake of comprehensibility let's just say: 

*'''For normal monsters:''' The more players, the more drops.
*'''For Super Uniques''' (like Pindleskin), '''Uniques and Champions''': player setting is irrelevant.
**Super Uniques will always drop two items.
**Uniques will always drop one item.
**Champions will always drop one item.
*'''Bosses''': "nodrop" will be reduced to zero for 5 unpartied players or 3 near players in the same party. In Single Player the difference between the drops for 3 player setting and 5 player setting is only marginal though.

Note: For unpartied players (and simulated players via the Players X Command) only every second additional players has impact on drop rates. So the steps for more drops are '''players 3''', '''players 5''' and '''players 7'''. 
In other words: players 8 and players 7 have the same drop rates, players 6 and 5, players 4 and 3, and players 2 and 1.
Note that the amount of Experience gained and monsters' Hit Points are nonetheless different for each player setting (as stated above).

===Skills and Abilities===
A frequent question when it comes to player setting is, which skills and weapon abilties that correlate with a target's Hit Points scale with the player setting. For example, the Necromancer's Corpse Explosion deals damage depending on the corpse's HPs (between 60% and 100%). Does the skill take the base HPs or the modified (higher) HPs on higher player settings? Unfortunately the answer is: Depends on what version you are using. Here's a list of skills and abilities, that correlate with a target's HPs.

''The list is not complete yet. Feel free to add any information you have about scaling.''

{|style="text-align:center"
!rowspan="2"|Skill/Ability
!colspan="11"|scales in
|-
!1.10+
!1.09
!1.08
!1.07
!1.06
!1.05
!1.04
!1.03
!1.02
!1.01
!1.00
|-
|style="text-align:left"|Static Field
|<nowiki>+</nowiki>
|<nowiki>+</nowiki>
|<nowiki>+</nowiki>
|?
|?
|?
|?
|?
|?
|?
|?
|-
|style="text-align:left"|Corpse Explosion
|<nowiki>-</nowiki>
|<nowiki>-</nowiki>
|<nowiki>-</nowiki>
|<nowiki>-</nowiki>
|<nowiki>-</nowiki>
|<nowiki>-</nowiki>
|<nowiki>-</nowiki>
|<nowiki>-</nowiki>
|<nowiki>+</nowiki>
|<nowiki>+</nowiki>
|<nowiki>+</nowiki>
|-
|style="text-align:left"|Death Sentry
|<nowiki>-</nowiki>
|<nowiki>-</nowiki>
|<nowiki>-</nowiki>
|<nowiki>-</nowiki>
|n.a.
|n.a.
|n.a.
|n.a.
|n.a.
|n.a.
|n.a.
|-
|style="text-align:left"|Crushing Blow
|<nowiki>-</nowiki>
|?
|?
|?
|?
|?
|?
|?
|?
|?
|?
|-
|style="text-align:left"|Summoned minions (HPs)
|<nowiki>-</nowiki>
|<nowiki>+</nowiki>
|?
|?
|?
|?
|?
|?
|?
|?
|?
|}


=The Players X Command=
From version 1.09 onward, the player setting can be changed arbitrarily in Single Player mode, open battle.net and non battle.net Mulitplayer mode. In order to do so, one has to enter a certain command while in game. This is done by hitting "Enter", typing the players X command, and confirming by hitting "Enter" again (yes, it's the normal shoutbox usage). The command differs slightly for the different versions of Diablo II.

In genereal the Players X command simulates an amout of players in the game equal X, although less players are actually in game. X cannot be lower than the actual number of players in game. For example, if you're playing with 2 friends a multiplayer game via TCP/IP, you can only choose a number equal or greater than 3. All other commands will be ignored.

'''The Players X Command only simulates unpartied players.''' (Important for drop mechanics as explained above)

Note that the Players X command doesn't affect monsters that have already spawned by the time you type the command. I'm not entirely sure about the radius in which monsters spawn around you, but according to jiansonz's testings it's somewhat smaller than the distance from the stairs in Durance level 3 to Mephisto's spawning point (meaning that one could still tune down the player setting shortly after entering Durance 3 and thus have the Council spawn on a different player setting than Mephisto himself). To make sure every monster is affected, typing the command while still in town is recommended.

Players X does however affect all clickable items (i.e. logs, chests, urns etc.) immediately. In theory one could clear the whole area on p1, then set the player settings to 8 for maximised drops (i.e. minimised NoDrop) and pop all chests, urns etc. only then. This is in no way illegal, but considered cheesy by most players in the SPF. Ususall this (ab)use of the Players X command is prohibited in SPF tournaments.

In V1.09, when hit points of your summoned minions (e.g. Golems, Valkyrie) scaled with the player setting, it was useful to change the player setting to maximum before casting the minion and then immediately switch back to a lower player setting, which is also considered as cheesy. In V1.10 minions' hit points no longer scale up with the player setting.

===Versions 1.00 to 1.08===
No players X command available.

===Version 1.09a/b===
The command is '''''players X''''', where X can be any number between 1 and 64. You won't get any confirmation that the player setting has changed.

===Version 1.09c/d===
The command is '''''players X''''', where X can be any number between 1 and 8. You won't get any confirmation that the player setting has changed.

===Versions 1.10 and 1.11===
The command is '''''/players X''''' or '''''/playersX''''', where X can be any number between 1 and 8. You will get the confirmation ''players set to X'' on your screen. 
This command is available in all versions of 1.10 and 1.11.

Player Settings

2008-02-05T23:39:38Z

NextDelay

2008-01-27T23:28:46Z

Joshgt2:

NextDelay is a property that activates a hidden "hit timer" that limits how often any attack from that group (i.e. all the skills listed here) can damage a single target. This works similarly to the infamous [[Casting Delay]], which limits how often any spell in that group can be cast. The difference is that the hit timer doesn't prevent you from attacking, it just sets everyone's (includes you, your minions/merc, other players (hostile/neutral/allied), and their minions/mercs) chance-to-hit that monster (with a hit timer attack) at zero until the timer runs out.

So, the moment a certain skill from the following list damages a monster, it prevents every other skill on the list from hitting the said monster for the original skill's NextDelay duration (whether from you or any other character).

__TOC__

==Skills affected by NextDelay==

'''25-Frame Delay''' (1 second) 
*Shock Web 
*Blade Sentinel 
*Twister 
*Tornado 

'''10-Frame Delay''' (0.4 seconds) 
*Volcano (initial eruption) 

'''6-Frame Delay''' (0.24 seconds) 
*War Cry 
*Grim Ward 

'''5-Frame Delay''' (0.2 seconds) 
*Fissure 
*Volcano (small fireball) 

'''4-Frame Delay''' (0.16 seconds) 
*Multi Shot 
*Strafe 
*Lightning Strike 
*Chain Lightning 
*Nova 
*Frost Nova 
*Poison Nova 
*Shock Wave 
*Fist of Heavens (Holy Bolts) 
*Wake of Fire 
*Claws of Thunder ''(only 2nd and 3rd charge charges have Next Delay. 1st charge does not trigger Next Delay)'' 
*Phoenix Strike ''(only 2nd Chain Lightning and 3rd Chaos Orb charge have Next Delay. 1st charge does not trigger Next Delay)'' 
*Dragon Flight 
*Battle Cry 
*Battle Command 
*Battle Orders 

==Examples==

2 sorcs are questing along and they encounter a monster. They both cast Chain Lightning targeting the same monster, but one player has a slightly faster reaction/casting speed/whatever than the other, so his CL hits the monster first. The first CL to hit starts the NextDelay timer, which lasts for 4 frames (0.16 seconds). The second, slower sorcs, ChainLightning will automatically miss if it "hits" the monster within the 0.16 seconds of the first CL. If the NextDelay from the first CL has already run out when the second CL "hits", the monster will also receive the damage from the second spell (and reset the NextDelay timer again).

A Wind Druid is spamming Twister at some Frenzytaurs. He is quite well equipped and hits the 11 fpc breakpoint. Thus he can hit a monster at least two times a second. The Frenzytaur in lead gets hit by the first Twister, and even the second Twister cast 11 frames later hits him. Since he is still under the influence of the NextDelay timer from the first Twister, which lasts 25 frames, he will only take damage from the first Twister. The damage from the second one will not be applied.

==Credits==

The information about NextDelay is taken from the diabloii.net Assassin FAQ. 
The first example is sirpoopsalot's from the Sorceress FAQ.

Help:FAQ

2008-01-27T23:26:51Z

Joshgt2: Replaced "Hellgate: London" with "Diablo II"

=How do wikis work?=

A wiki is an open source document that anyone can edit or add to. "All of us are smarter than any of us," goes the theory. Wikis are designed to be easy to edit; they are primarily text-based, and you do not need to know HTML or PHP or CSS or any other programming language to edit wiki pages.

For more practical purposes, you can jump right in and edit text on this wiki without knowing anything more than how to click the "edit" button.

=How can I help?=

If you know about ''Diablo II'', you can fill in some pages that aren't yet online, or flesh out existing pages. A wiki is a living document, and with the game constantly evolving, there are always changes, updates, and corrections to be made to existing pages.

If you're less of an D2 expert, or aren't comfortable writing original material, you can help improve existing pages. Almost every page on this wiki could be improved by adding links to other related pages, illustrating the information by inserting thumbnails or links to full screenshots, improving the navigation (by adding links or categorization) to help people find the pages they seek, or even just italicizing "Diablo II" as needed.

If you have experience with wikis you can help fix up errors or formatting problems, or work with people who know ''Diablo II'' or writing, but aren't wiki experts.

If you don't want to get that involved you can make smaller changes; fix typos, join the "discussion" on a page or in our wiki forums to suggest additions or corrections or different interpretations.

=Do I need to know how to code?=

No. Wiki markup is very simple, much less complicated and fussy than HTML. Here's a markup page list all the codes you will need. Alternatively, if you see something on a page that you'd like to replicate simply click 'edit' at the top of the page and see what the code is and copy and paste it to the page you're working on.

Tables of Contents (like the one at the top of this page) are created automatically from the headings in a page.

Don't be afraid to make changes if you have the info; there's a handy preview button before you commit :)

*[[Help:Markup|Details of the Wiki Markup you can use]].
*Wikipedia.org hosts an [http://en.wikipedia.org/wiki/Help:Contents extensive help section] which will answer every conceivable question you might have about writing a wiki.

=Do I need a Wiki account to contribute?=

Yes, but there's a good chance you already have one. The HellgateWiki is linked to The Unoffical HGL Site forums, so if you're a forum member, you can use that account to edit the wiki. If you're not a forum member, [http://forums.diabloii.net visit them to sign up] (and for all your HGL discussion needs -- it only takes a moment.

=Any guidelines to adding content=

HellgateWiki prides itself on the high standard of site content and so we encourage everyone to check their updates for simple things like spelling and grammar. Also make sure you double check your info before committing. Accurate Hellgate: London information is the key!

Do not add copyrighted content from another on or off-line publication to HellgateWiki.

=Help, I need advice!=

Don't worry, if you haven't found the help you need here there is always the HellgateWiki support forum. Feel free to ask questions about general wiki issues, as well as specific page content.

=Can I cut and paste content from HellgateWiki to my own website?=

You may not copy sections or pages from HellgateWiki. This wiki is a collaborative effort, and the pages are a result of the efforts of hundreds of HGL fans. Contributors to the HellgateWiki have given permission for their work to appear in this wiki, on this site. But nowhere else.

Short, fair use quotations from HellgateWiki are permitted, (if you want to cite facts to back up your argument in a Hellgate Forum discussion, for instance) providing you clearly cite the source of the quote and provide a link back to the original page on HellgateWiki.

==Can I cut and paste content from other websites to HellgateWiki?==

No, not unless you have the express permission of the copyright holder. Information submitted to HellgateWiki should be your original writing, and don't lie, or we'll know. Quotations are permitted (and encouraged) to support your info, but they should come from original sources, (such as interviews with Hellgate Team members), and not someone else's summary of the information. Read and research, then write your own material.

=If I create a page can I stop others amending it?=

No. The whole point of a wiki is that all of us are smarter than one of us, and that as much as you or I know about some topic, someone else knows more. That being said, intentional misinformation, inflammatory or libelous comments are prohibited, and pages that deal with controversial subjects or are victimized by malicious editing may be temporarily locked.

=Can I post my strategy guide on HellgateWiki?=

No. The Diablo Wiki is not an appropriate venue for strategy guides. This wiki is the best available source for Diablo II information and fact, and writers should not be afraid to offer opinions, but this is not the place for strategy guides. Strategy submissions are welcome at the strategy section of The Unofficial Site, of course.