查看“Bugs”的源代码

<noinclude>此页列出了错误, 意外崩溃, 以及在 PD2 中发现的故障. 还列出了一些主要的原版 bugs. 参见: [https://discord.com/channels/701658302085595158/781105003535400991 #已知-bugs] discord 频道</noinclude>

有关崩溃或其他游戏问题的帮助, 查看这个 [[Support FAQ|常见问题解答]] 或这个 [https://discord.com/channels/701658302085595158/770081262982529064 #技术-支持] discord 频道.

== 非-原版 Non-Vanilla ==
<span class="emphasis">''Bugs 的引入在 PD2 中是由于新特性造成的''</span>

'''General Bugs:'''
* [[Recipes#Gem_&_Rune_Recipes|Flawless gems]] can only be promoted to perfect gems while in their ''stacked'' form.
* Sometimes when using the [[Cartographer's Orb]] recipe, the result is a Hand Axe instead of a map of a higher tier.
* The monsters named "skeleton" in act 1 (like those in mausoleum/crypt) don't drop loot.
* Shrieking Terror monsters in maps cause summon AI issues.
* In Character Select screen, some characters are missing heads or appear to have different equipment.
* Some people are crashing with HD text enabled (disable within ctrl+o menu if it's an issue)
* Text/Quantity numbers show through UI elements when using D2GL
* In some cases, having two equipment items of the same type within the cube when using a recipe which only requires one, one of those items may be destroyed.
* When attempting to connect while too many players are active, players may be presented with a dialogue box showing their position in a queue. This is misleading since the queue system is not used - players will need to connect manually instead. This may take several attempts, especially if the server they've selected is at its limit and others are also trying to join it. If other servers are acceptable, try using one of them temporarily instead.

'''Bugs for Specific Skills or Equipment:'''
* [[Revive|Revives']] own summon/sentry abilities (e.g. hydras cast by revived council members) don't grant player experience or quest progress if they kill enemies.
* Being in [[Whirlwind]] ([[Blade Dance]]) animation when leveling up on assassin locks up your animation.
* Hydras spawned from the [[Dragon_(Chest)|Dragon]] runeword (chest) are only staying up for ~1 second before despawning if trigged by whirlwind.
* Fire Resist aura from [[Flickering Flame]] on merc reduces max res back to 75 on paladin.
* Heart of the Wolverine (from [[Wisp Projector]]) despawns when you level up.
* Some items in the [[Elite#Immortal_King|Immortal King]] set have their set bonuses displayed in blue (like normal attributes) rather than in green.
* Ethereal versions of [[Elite#Immortal_King's_Stone_Crusher|Immortal King's Stone Crusher]] may display the incorrect damage (missing the set bonus) depending on the order of the set items being equipped.

<div id="BH"></div>'''BH-Related Bugs:'''
* Attribute ranges on tooltips are sometimes incorrect
** When multiple sources add the same attribute, only a single source's attribute range is shown rather than a combined range. Examples:
*** The 50% Damage to Undead automod for blunt weapons isn't included in the attribute's range.
*** Crafted items will display the standard attribute range (e.g. rolled affixes) without taking into account the attribute range from predetermined affixes.
*** When a runeword adds the same attribute as one of its runes, the attribute range doesn't include values from the rune. Example: [[Chains of Honor]] shows [35-45] all res in-game but is actually [50-60] since Um adds +15
**: <span class="omod">List of attribute sources: prefixes, suffixes, automods, superior affixes, predetermined crafting affixes, corruptions, socketed gems/runes/jewels, pointmods</span>
** When an item has a "hybrid" affix with multiple attributes, each attribute range is still treated separately which can result in inaccurate/ambiguous comparisons. Example:
*** A Fine Small Charm adds +[1-3] damage & +[10-20] AR but the attribute range for AR shows [2-36] in-game since the Bronze/Iron/Steel affixes can add that much AR (but of course those affixes don't add any damage)
** The attribute range may only reference affixes which are possible for rare items so some higher magic-only affixes won't have accurate ranges
* Some items have their [[Item_Filtering#Colors|default color]] built into '''%NAME%''', so their color won't change unless their name is rewritten completely.

Note that attribute ranges and lootfilters are handled by [https://github.com/Project-Diablo-2/BH PD2's open-source version of BH], which anyone may submit improvements for. The discord's [https://discord.com/channels/701658302085595158/771820538502971402 #lootfilter] channel may be a good place to learn more about it if you have questions, since devs and editors often frequent the channel and discuss BH-related changes there.

=== 仅限单机的错误 Singleplayer-Only Bugs ===
* PlugY: Having too many maps in a stash page can cause crashes if that page is the most recently visited stash page
*: <span class="omod">Fix: Reduce the number of maps stored per page, or switch to another page before leaving the stash</span>
* PlugY: Having gold in the shared stash can cause issues such as preventing oskills from working correctly
*: <span class="omod">Fix: Remove all gold from the shared stash, or disable the shared gold feature in the config file</span>
* PlugY: The "toggle stash" button may be set to the wrong stash upon loading until interacting with the current stash - this happens if the most recent stash interaction prior to saving/exiting involved using a PlugY stash button instead of manipulating an item in the stash
*: <span class="omod">Workaround: Add or remove an item from the stash prior to saving/exiting (this also fixes the button at any time if it's set wrong)</span>
* PlugY: Stash navigation may be buggy if the stash pages are empty - the navigation will appear to jump between the wrong pages, but it is actually just displaying the wrong page numbers for all pages between the first page (page 1) and the first index (page 10)
*: <span class="omod">Fix: Put an item on page 10 or higher and save/exit</span>
* Andariel quest bug (vanilla bug - fixed in multiplayer)
<noinclude>
For all singleplayer differences, see: [[Singleplayer]]
</noinclude>

== 原版 Vanilla ==
<span class="emphasis">''Bugs 发现在原版和 PD2''</span>

* Multiple corpse bug - rejoining a game with more than one corpse will result in only the highest value corpse being carried over and items on all other corpses being lost
* Corpse limit bug - only ~15 corpses can exist simultaneously, so if a player dies while wearing gear and at the corpse limit, the gear will be lost even without rejoining a game
* Strength bug - if stat requirements of equipped items are only met via the stats granted by those items, the gear won't be visible to other players; this may also contribute to losing items when there are multiple corpses or there isn't enough inventory space to store unequippable items when recovering them from a corpse
: <span class="omod">When recovering items from a corpse, they are re-equipped in the following order: helm, amulet, chest, left weapon/offhand, right weapon/offhand, left ring, right ring, belt, boots, gloves</span>
* Broken-offhand-whirlwind (BOW) bug - when dual-wielding and using whirlwind, if the offhand weapon is broken (0 durability) and has 1 gemmed socket (to prevent it from disappearing), the mainhand weapon is used as both the mainhand ''and'' offhand weapons
* Failed-to-Join (FTJ) bug
* [[Monsters#Bloodwitch_the_Wild|Blood Witch]] sometimes doesn't spawn in Halls of the Dead

For a more complete list of vanilla bugs, see wikis dedicated to vanilla. [https://www.theamazonbasin.com/wiki/index.php?title=Diablo_II The Amazon Basin] wiki does an especially good job, with bugs typically written in red in their relevant categories. Another example is this [https://us.forums.blizzard.com/en/d3/t/bugproblem-list-for-devs-what-to-fix-for-d2r/30490 list of 200+ bugs] that focuses on what should be fixed for D2: Resurrected.

For bugs fixed in PD2, see [[General_Changes#Bug_Fixes | General Changes]].