1.11 Release Notes

GlennDanzig220

New member
1.11 Release Notes

I connected to Bnet, and downloaded the patch. I copied/pasted the release notes.

--------------------------------------------------------------------------
Diablo II Version History
--------------------------------------------------------------------------
- Patch 1.11
--------------------------------------------------------------------------


A new Mystery has been revealed!

- Players of Hell Difficulty Realm games are hereby warned once again,
that a series of new and challenging tests await you! The answer lies
within Diablo's Bosses, which span across the world from the Den of Evil
to the Throne of Destruction...


New Items

- Added 10 New Runewords.
- Added new Unique Items that will drop from Special Bosses.


Hireling Enhancements

- Players can purchase hirelings that are within 1-5 levels below their
own level.
- The rate at which hirelings gain experience has been increased. They
should now stay closer to the player's level.


Major Bugs

- Creating a town portal when corpses or other objects entirely fill the
area where the portal will appear in town will no longer crash the game.
- Skills obtained from runewords created while the item is equipped will
no longer disconnect you from Battle.net when chosen.
- Barbarians will no longer become stuck when using Whirlwind right after
Inferno from the unique item Balrog Blade Flamebellow.
- German, Spanish, and Polish users will no longer crash when the mouse
cursor moves over an item that grants an Aura while equipped.
- The game will no longer crash when selecting a skill granted by a weapon
at the same time as switching weapons with the W key.
- Dying or being requested to trade while changing the key configuration
will no longer cause you to get stuck.
- The "Missile Firing too far" assertion error has been corrected.
- Attempting to sell a Horadric Cube or a quest item to an NPC by holding
Control while clicking will no longer disconnect you from Battle.net.


Minor Bugs

- Running the game with -install no longer causes the game to be installed
as a Windows Service. -install is now ignored.
- Sometimes the seals in Diablo's lair would not activate. This has been
corrected.
- Character expiration messages have been updated to reflect the
expiration policy implemented in patch 1.10.
- Unidentified items sometimes caused other set items to display green for
items the player does not have. This has been corrected.
- The German mouseover text for the Ist rune has been corrected.
- Account recovery is now allowed for existing accounts whose name is only
one or two characters.
- When leaving a game on Battle.net, you will now be brought back to the
channel in which you were previously.
- Transmuting an ethereal item now retains the ethereal stats bonuses.
- In Japanese Lord of Destruction, items that add to all Assassin skills
incorrectly stated in their mouseover text that they added to all Druid
skills. This has been corrected.
- Battle.net messages for non-English versions have been corrected.


Fixed Game Exploits

- It is no longer possible to bypass the 10-second hostility timer by
activating a waypoint at the same time as declaring hostility.
- Uber Diablo is no longer killed when Shenk the Overseer or Blood Raven
die nearby.
- Necromancers with Trang-Oul's Set equipped could sometimes become
invincible to attack. This has been corrected.
- Blessed Hammer no longer remains active while in town, preventing
players from subsequently declaring hostility and having the hammers hit
other players for damage.
- Set items retained their multi-piece bonuses after the player died, even
though they were removed. This has been corrected.
- Items with skill-charging effects will no longer give synergy bonuses to
skills when equipped on a character without those skills.
- Pasting from the Clipboard no longer allows the creation of characters
with more than one dash or underscore in their name.


There ya go!
 
GlennDanzig220 said:
- Items with skill-charging effects will no longer give synergy bonuses to
skills when equipped on a character without those skills.

There goes the marrowalk bug...

There doesn't seem to be much changes for the SP community, does it?
 
Like I was saying before... no need to "blow out" my v1.10 characters and inventory for this total crap patch!!!!!!!!!!!!
 
By the Light, I get disconnected from the net for nine days and they release a patch? It's a conspiracy! :)

I may have to install D2 again, now... hmm.

As the saying goes, better late than never! :clap:
 
- Added 10 New Runewords.
- Added new Unique Items that will drop from Special Bosses.

Someone know if that is even in SP?

Someone can check if they added the Only Battle.net 1.10 Season 2 RuneWord to SP?
 
Sophitia said:
Someone know if that is even in SP?

Someone can check if they added the Only Battle.net 1.10 Season 2 RuneWord to SP?

Already checked.

TirTalAmn gemmed bow.. *NOT* impressed.
 
I tried Edge real quick and it didn't work. I may have done something wrong.

Has anyone tried to verify that FE has been nerfed?
 
- Items with skill-charging effects will no longer give synergy bonuses to
skills when equipped on a character without those skills.

That sucks, there ends my dual elemental druid, magi barbs all 3 variants, off class summoners. And thats just the builds I have thought with. I guess they think Marrowwalks really is a bug.

The fire Enchant bug should be removed (as it was fixed with a Bnet server side patch) also the SP community should now have all of the newer runewords with that patch as they are serverside patches that we have been skipped on.

Then again Blizzard has done things wrong before in the past.
 
jjscud said:
I tried Edge real quick and it didn't work. I may have done something wrong.

Edge is TirTalAmn, confirmed not working..

Also;

Saracen's Chance
Amulet
Required Level: 47
Item Version: 1.10 Expansion
Item Level: 72
Fingerprint: 0x5e24117d
+12 to Strength
+12 to Energy
+12 to Dexterity
+12 to Vitality
All Resistances +18
10% Chance to cast Level 2 Iron Maiden when struck

I found this in a quick 1.11 game.. I'm guessing this could be an ATMA related display error, but most likely not, since ATMA doesn't seem to care that the char I'm using (I backed it up prior to the update) is running 1.11, it still reads it as 1.10.

I think we've been shafted.

Again.
 
Settle down everyone, seriously.

You don't know what they've done until we uncook the MPQ files and look inside. They may well have removed some of these frankly stupid runewords from the realms too. We'll know once we look inside the new runes.txt.
 
I've killed the countess at point blank range a couple time now and haven't been killed, still around 400 - 600 damage but not insta death.
 
I don't think getting the 1.11 patch would necesarrily patch everything for SP anyway. I mean, they'll want to keep the size of it down, and its already fixed for bnet, why would the code to fix those things be in the patch downloaded from bnet?

We may have to wait for 1.11 like a ftp download, so it includes things that aren't in this newest release which were already fixed bnet-side.
 
It looks like the FE ancients bug has gone, assuming my necro wasn't incredibly lucky 3 times when one was FE
 
Method, yikes, you're brave using Atma already.

Atma doesn't know anything about 1.11. At best, they have changed the save file format very little (possibly barely at all) and Atma can still understand most things in there. However, it should still be considered "use at own risk". I expect the Doc will say something about it shortly. It may take a few weeks for the new format (if it changed) to be unravelled and a new reader written.

Actually, if anyone wants to send me a save file from the new patch (ie, started as a new char inside 1.11) I can start poking around. Don't have the actual game here at work but a binary editor will reveal much :)
Don't want any items on there, just the stuff you start with will be cool, so I can compare it to a known 1.10 equivalent.

[email protected]
 
DougTheHead2 said:
I don't think getting the 1.11 patch would necesarrily patch everything for SP anyway. I mean, they'll want to keep the size of it down, and its already fixed for bnet, why would the code to fix those things be in the patch downloaded from bnet?

We may have to wait for 1.11 like a ftp download, so it includes things that aren't in this newest release which were already fixed bnet-side.

First point - a new patch should fix everything regardless of whether the bug was SP or not, just because they already fixed it online doesn't mean we should be missing out because we choose not to play with all the dupers and hackers that infest cattle.net

Second point - Why in blue-hell would they release two separate patches when it's not only easier to just have one, but also more convenient to distribute it anyway just by having the player update through accessing the realms.
 
Back
Top