It's not working.
I have a sorc who I got up through Act 1 Hell in 1.12 before upgrading to 1.13. Single Player, by the way, if that makes a difference. Well, now I'd like to use one of her older difficulty's respecs, but when I go back to either Normal or Nightmare respecing isn't on the list of Akara functions. Even more strangely, when I went to the Den of Evil, thinking if I cleared it out again that might help, I noticed that the area is called The Cave, despite clearly being in the Blood Moor.
Anyone know what the deal is here?|||It looks to be working correctly:
[blue=http://forums.battle.net/thread.html?topicId=21730644778&sid=3000]Specific changes/improvements
- Respecialization is now possible! Completing the 'Den of Evil' quest will now additionally reward 1 free respec which can be saved. Players who have already completed this quest should receive 1 free respec in Hell difficulty. [/blue]
The Den of Evil is always called The Cave when the creator of the game has already completed the quest, and it has for at least the last several patches.|||Ah, bummer. I thought I would get one free re-spec per difficulty, but perhaps that was not the intent of that wording. Thanks.
Saturday, April 21, 2012
Update Released
Well mine just updated to 1.13
Tried to copy and paste the full details but wouldn't let me highlight them.
Most important though is some items now have orange names (items need for uber trist like keys included) and increased chance of HR drop.
Or maybe not? Corner of my D2 main page still says 1.12 :/
Odd...|||AFAIK, it's not 1.13 yet...there's nothing on the Battle.net forums or news pages.
Did you click on the PTR?|||Nope, I switched from west to east and it updated.
Tried to copy and paste the full details but wouldn't let me highlight them.
Most important though is some items now have orange names (items need for uber trist like keys included) and increased chance of HR drop.
Or maybe not? Corner of my D2 main page still says 1.12 :/
Odd...|||AFAIK, it's not 1.13 yet...there's nothing on the Battle.net forums or news pages.
Did you click on the PTR?|||Nope, I switched from west to east and it updated.
Temp bans get extended...?
when I mule after 20 hell baal games, i use to switch chars a lot and today i wasn't careful and got temp banned because i did it too fast...anyway the thing is,i've been reading topics on this site for weeks and the answer i see the most around is:when you log in after a temp ban,it will reset the ban time or extend it...but where did those conclusions come from? I really would like to know for sure if logging in does that or just nothing,cause i try to log to know if I can play again and not wait a whole 12 hours when it actually was a 1-2 hour ban...
also,with my actual router i can't refresh my IP just by rebooting it,i have to wait the ban to finish...i tried a lot of stuff to solve it but i didn't do anything new
thanks in advance|||If you have had a temp ban once or more that week, i think it will be a extended one.
Also, run DiaBaal games, they give approx the same XP (debatable) and they last longer so you will have less chances to face the temp ban. Also, i think that if you try log in after temp ban, the first 3 have no effect but after that, it gets extended.
Finally, don't rush while muling, i keep a 3mins as the least time the character is in the game.
Ps. Try logging every 1 and half hours after the ban, if after the second (3 hours after tban) you still can't log in, wait 9 more hours.|||Temp bans are annoying just because it took the people who program the bots all of 2 minutes to edit their scripts just beyond the amount of time that would get them temp banned. Where as I, the honest Dkey runner who knows the maps and does the runs in ~45 sec-1.5 min (if tomb vipers) normally gets banned.|||ah, so it takes 3 of those tries to have it extended...now it's clearer...but when you say to wait that much time...does it mean that the 5-10 mins bans are no more and that now they are at least 1 hour almost every time a ban occurs? because it almost always takes near 1 to 12 hours to unlock the IP from ban whenever I get it,very rarely there has been less than a hour to wait
thank you for replying to my interrogation|||For me I try at 10 minutes and then if it doesn't work then, I try again at 30-45 minutes (normally get distracted waiting so it's more like 45) and it generally works then.
also,with my actual router i can't refresh my IP just by rebooting it,i have to wait the ban to finish...i tried a lot of stuff to solve it but i didn't do anything new
thanks in advance|||If you have had a temp ban once or more that week, i think it will be a extended one.
Also, run DiaBaal games, they give approx the same XP (debatable) and they last longer so you will have less chances to face the temp ban. Also, i think that if you try log in after temp ban, the first 3 have no effect but after that, it gets extended.
Finally, don't rush while muling, i keep a 3mins as the least time the character is in the game.
Ps. Try logging every 1 and half hours after the ban, if after the second (3 hours after tban) you still can't log in, wait 9 more hours.|||Temp bans are annoying just because it took the people who program the bots all of 2 minutes to edit their scripts just beyond the amount of time that would get them temp banned. Where as I, the honest Dkey runner who knows the maps and does the runs in ~45 sec-1.5 min (if tomb vipers) normally gets banned.|||ah, so it takes 3 of those tries to have it extended...now it's clearer...but when you say to wait that much time...does it mean that the 5-10 mins bans are no more and that now they are at least 1 hour almost every time a ban occurs? because it almost always takes near 1 to 12 hours to unlock the IP from ban whenever I get it,very rarely there has been less than a hour to wait
thank you for replying to my interrogation|||For me I try at 10 minutes and then if it doesn't work then, I try again at 30-45 minutes (normally get distracted waiting so it's more like 45) and it generally works then.
Diablo errors at "random" times
At random times, Diablo II will freeze, I'll have to Ctrl+Alt+Del to get out, and it'll say that there is an error and exiting the error will close Diablo. This never happened until now (I'm at the last quest of Act I).
I say "random" because I found that certain actions will cause it to freeze such as equipping the shield that I have in my inventory.
Anyone know what to do?
EDIT: Also, the error says "Unrecoverable internal error 6fe22f1b"|||most likely a corrupt file, try reinstalling
copy your d2 save folder to backup your chars|||Quote:
most likely a corrupt file, try reinstalling
copy your d2 save folder to backup your chars
I've done that and it doesn't work.
I reinstalled using the download client and the cd (separate times). It never works.|||I am having similiar too and it always slaps it at the lobby.
Doesn't matter if i am running 2 clients or one, either.
I remember having these same problems like, 5 to 6 YEARS ago. (Had a 4 year break ^^)
Just roll with it bro, these games are rather old already, desinged for the Win 98 / 2k era. (Maybe xp too
?)
Anyways, my issue isn't the same as yours, so you might want to try and running it in compability mode, just as starters.
Also Defrag your computer. (Suggesting Defraggler, i hope i wont be banned for shamelesly advertising)
Also keep your drivers updated.
Lastly, try running the game in windowed mode, using "-w" command, google it for more info.
EDIT: I googled around and found this. Uninstall the game by using the exe, then delete everything left in the game folder /Diablo II Excpt saves ofc. then reinstall and it should work.
Also try this
I say "random" because I found that certain actions will cause it to freeze such as equipping the shield that I have in my inventory.
Anyone know what to do?
EDIT: Also, the error says "Unrecoverable internal error 6fe22f1b"|||most likely a corrupt file, try reinstalling
copy your d2 save folder to backup your chars|||Quote:
most likely a corrupt file, try reinstalling
copy your d2 save folder to backup your chars
I've done that and it doesn't work.
I reinstalled using the download client and the cd (separate times). It never works.|||I am having similiar too and it always slaps it at the lobby.
Doesn't matter if i am running 2 clients or one, either.
I remember having these same problems like, 5 to 6 YEARS ago. (Had a 4 year break ^^)
Just roll with it bro, these games are rather old already, desinged for the Win 98 / 2k era. (Maybe xp too
?)Anyways, my issue isn't the same as yours, so you might want to try and running it in compability mode, just as starters.
Also Defrag your computer. (Suggesting Defraggler, i hope i wont be banned for shamelesly advertising
)Also keep your drivers updated.
Lastly, try running the game in windowed mode, using "-w" command, google it for more info.
EDIT: I googled around and found this. Uninstall the game by using the exe, then delete everything left in the game folder /Diablo II Excpt saves ofc. then reinstall and it should work.
Also try this
Weird bug - Mac 1.13beta - Life "text" always showing
Hi!
Sorry about the thread title, I don't what's called the life "text".
Bug?
As long as I can remember playing 1.13beta (both 1.13a and now after updating) that is always showing, even without the mouse over the life "bowl".
It happens will all chars I create.|||Not a bug ^^
Click again near bottom area of: Life bowl or Mana bowl|||I feel dumb!
I over it with my mouse and tried clicking several times with no luck. The bottom is the key :P
Thanks :)
Sorry about the thread title, I don't what's called the life "text".
Bug?
As long as I can remember playing 1.13beta (both 1.13a and now after updating) that is always showing, even without the mouse over the life "bowl".
It happens will all chars I create.|||Not a bug ^^
Click again near bottom area of: Life bowl or Mana bowl|||I feel dumb!
I over it with my mouse and tried clicking several times with no luck. The bottom is the key :P
Thanks :)
D/A/E Bug
Hey, I'm new btw.
I was just wondering whether the D/A/E bug was fixed or not. I'm playing 1.12 and it's really painful. I really hope they get it done.
Cheers,
P.S: This is the right place to ask, right?|||I wasn't, sadly.
I was just wondering whether the D/A/E bug was fixed or not. I'm playing 1.12 and it's really painful. I really hope they get it done.
Cheers,
P.S: This is the right place to ask, right?|||I wasn't, sadly.
What is the eth bug in 1.11?
Someone told me using a given recipe for the cube, craft an eth armor/shield so the eth bonus (+50%edef) is applied again.
Is this true? Ive seen eth shield rw with huge def, and people saying it has the eth bug.
If so....what is the recipe?
Fer|||use the cube socket recipe- its posted on the arreat summit. It is true- I made 2 eth merc fortitudes after the 1.11 patch before the end of last season that each had over 3000 defense. This also works with eth shields and helms, but not NOT SUPERIOR VERSIONS. The cube formula only works with eth regular unsocketed helms armors and shields:
1 Tal Rune + 1 Thul Rune + 1 Perfect Topaz + Normal Body Armor = Socketed Body Armor of same type
The number of sockets created will vary. The item must be normal and unsocketed. Low-quality items and superior items do not work. The item gets 1-4 sockets, randomly. However, the number of sockets is then restricted by the maximum number of sockets that base item with that ilvl can have. The chance to get X sockets in most armor is 1/4, (I.E: Mage plate has a max of 3 sockets, so it has a 2/4 [1/2] chance to get 3 socketss). The base of 6 was used in the ratios for all the above mentioned areas.
1 Ral Rune + 1 Thul Rune + 1 Perfect Sapphire + Normal Helm = Socketed Helm of same type
The number of sockets created will vary. The item must be normal and unsocketed. Low-quality items and superior items do not work. The item gets 1-3 sockets, randomly. However, the number of sockets is then restricted by the maximum number of sockets that base item with that ilvl can have. For example, if you have an item that can only have 2 sockets, there's a 5/6 chance of getting 2 sockets and a 1/6 chance of getting 1 socket.
1 Tal Rune + 1 Amn Rune + 1 Perfect Ruby + Normal Shield = Socketed Shield of same type
The number of sockets created will vary. The item must be normal and unsocketed. Low-quality items and superior items do not work. The item gets 1-4 sockets, randomly. However, the number of sockets is then restricted by the maximum number of sockets that base item with that ilvl can have. For example, if you have an item that can only have 2 sockets, there's a 5/6 chance of getting 2 sockets and a 1/6 chance of getting 1 socket.|||Ok,
I got an eth kurast shield unsocketed. IF i do the recipe cube for socketing him instead of regular Larkuz (which always will give me 4 sockets on that shield), ill get the +50% ed appiled again but there is a chance I dont get the 4 sockets, a 50% chence of getting 4 socks, right?|||Quote:
Ok,
I got an eth kurast shield unsocketed. IF i do the recipe cube for socketing him instead of regular Larkuz (which always will give me 4 sockets on that shield), ill get the +50% ed appiled again but there is a chance I dont get the 4 sockets, a 50% chence of getting 4 socks, right?
Yes.
Kurast Shield has a max of 4 sockets at all ilvls.
The socket recipe will give 1/6 chance at each of 1 to 6 sockets.
If it gives too many sockets, it sets the socket to the max possible.
we sum:
1/6 chance at 4
1/6 chance at 5 (set to 4)
1/6 chance at 6 (set to 4)
and get
3/6 (or 50%) chance of 4 sockets|||Thnx for replies. I already made it. Too bad the shield only got 3 sockets and I wont be able to make exile on it. But I did noticed something with def, it was boosted much more than I expected. In fact, I thought the def bonus from the cube would work only over the base def on shield, but it was applied over the hole def of the eth shield. I mean:
currents shield def: 280 (ethereal)
so base shield def : 186.6 (eth bonus is +50% ed)
I did expected the boost to be another 50% ed, so:
(base def)*[(50%ed-eth bonus) + (50%ed-cube bonus)]= base def *100%ed =base def * (1+100/100)= base def * 2
this is:
186*2=372 def after cube thing
But the fact is the shield got 420 def after cube, so the calculation is:
[(base def)*(50%ed-eth bonus)]*50%ed-cube bonus= [(base def)*(1+50/100)]*(1+50/100)=base def * 2.25
this is:
186.6*2.25=420 (well I did dropp decimals nvm that)
which is much nicer :PPP|||Quote:
use the cube socket recipe- its posted on the arreat summit. It is true- I made 2 eth merc fortitudes after the 1.11 patch before the end of last season that each had over 3000 defense. This also works with eth shields and helms, but not NOT SUPERIOR VERSIONS. The cube formula only works with eth regular unsocketed helms armors and shields:
1 Tal Rune + 1 Thul Rune + 1 Perfect Topaz + Normal Body Armor = Socketed Body Armor of same type
The number of sockets created will vary. The item must be normal and unsocketed. Low-quality items and superior items do not work. The item gets 1-4 sockets, randomly. However, the number of sockets is then restricted by the maximum number of sockets that base item with that ilvl can have. The chance to get X sockets in most armor is 1/4, (I.E: Mage plate has a max of 3 sockets, so it has a 2/4 [1/2] chance to get 3 socketss). The base of 6 was used in the ratios for all the above mentioned areas.
1 Ral Rune + 1 Thul Rune + 1 Perfect Sapphire + Normal Helm = Socketed Helm of same type
The number of sockets created will vary. The item must be normal and unsocketed. Low-quality items and superior items do not work. The item gets 1-3 sockets, randomly. However, the number of sockets is then restricted by the maximum number of sockets that base item with that ilvl can have. For example, if you have an item that can only have 2 sockets, there's a 5/6 chance of getting 2 sockets and a 1/6 chance of getting 1 socket.
1 Tal Rune + 1 Amn Rune + 1 Perfect Ruby + Normal Shield = Socketed Shield of same type
The number of sockets created will vary. The item must be normal and unsocketed. Low-quality items and superior items do not work. The item gets 1-4 sockets, randomly. However, the number of sockets is then restricted by the maximum number of sockets that base item with that ilvl can have. For example, if you have an item that can only have 2 sockets, there's a 5/6 chance of getting 2 sockets and a 1/6 chance of getting 1 socket.
Just wondering...if you create a socket eth armor like this and get the extra defense, will it stay that way after the correct this bug, or will de defense drop to the level of a "normal eth socketed armor"?|||Quote:
Just wondering...if you create a socket eth armor like this and get the extra defense, will it stay that way after the correct this bug, or will de defense drop to the level of a "normal eth socketed armor"?
It will stay.|||I'm just hearing of this bug for the first time. Did 1.11 cause this?|||Quote:
I'm just hearing of this bug for the first time. Did 1.11 cause this?
yes it did; I made use of it right before the ladder reset to make 2 eth fortitudes with over 3,000 defense each :)|||Interesting, this works with other armor types, right? Like shields?
Oh yeah, how about weapons, do they gain twice the eth damage bonus, too?
Is this true? Ive seen eth shield rw with huge def, and people saying it has the eth bug.
If so....what is the recipe?
Fer|||use the cube socket recipe- its posted on the arreat summit. It is true- I made 2 eth merc fortitudes after the 1.11 patch before the end of last season that each had over 3000 defense. This also works with eth shields and helms, but not NOT SUPERIOR VERSIONS. The cube formula only works with eth regular unsocketed helms armors and shields:
1 Tal Rune + 1 Thul Rune + 1 Perfect Topaz + Normal Body Armor = Socketed Body Armor of same type
The number of sockets created will vary. The item must be normal and unsocketed. Low-quality items and superior items do not work. The item gets 1-4 sockets, randomly. However, the number of sockets is then restricted by the maximum number of sockets that base item with that ilvl can have. The chance to get X sockets in most armor is 1/4, (I.E: Mage plate has a max of 3 sockets, so it has a 2/4 [1/2] chance to get 3 socketss). The base of 6 was used in the ratios for all the above mentioned areas.
1 Ral Rune + 1 Thul Rune + 1 Perfect Sapphire + Normal Helm = Socketed Helm of same type
The number of sockets created will vary. The item must be normal and unsocketed. Low-quality items and superior items do not work. The item gets 1-3 sockets, randomly. However, the number of sockets is then restricted by the maximum number of sockets that base item with that ilvl can have. For example, if you have an item that can only have 2 sockets, there's a 5/6 chance of getting 2 sockets and a 1/6 chance of getting 1 socket.
1 Tal Rune + 1 Amn Rune + 1 Perfect Ruby + Normal Shield = Socketed Shield of same type
The number of sockets created will vary. The item must be normal and unsocketed. Low-quality items and superior items do not work. The item gets 1-4 sockets, randomly. However, the number of sockets is then restricted by the maximum number of sockets that base item with that ilvl can have. For example, if you have an item that can only have 2 sockets, there's a 5/6 chance of getting 2 sockets and a 1/6 chance of getting 1 socket.|||Ok,
I got an eth kurast shield unsocketed. IF i do the recipe cube for socketing him instead of regular Larkuz (which always will give me 4 sockets on that shield), ill get the +50% ed appiled again but there is a chance I dont get the 4 sockets, a 50% chence of getting 4 socks, right?|||Quote:
Ok,
I got an eth kurast shield unsocketed. IF i do the recipe cube for socketing him instead of regular Larkuz (which always will give me 4 sockets on that shield), ill get the +50% ed appiled again but there is a chance I dont get the 4 sockets, a 50% chence of getting 4 socks, right?
Yes.
Kurast Shield has a max of 4 sockets at all ilvls.
The socket recipe will give 1/6 chance at each of 1 to 6 sockets.
If it gives too many sockets, it sets the socket to the max possible.
we sum:
1/6 chance at 4
1/6 chance at 5 (set to 4)
1/6 chance at 6 (set to 4)
and get
3/6 (or 50%) chance of 4 sockets|||Thnx for replies. I already made it. Too bad the shield only got 3 sockets and I wont be able to make exile on it. But I did noticed something with def, it was boosted much more than I expected. In fact, I thought the def bonus from the cube would work only over the base def on shield, but it was applied over the hole def of the eth shield. I mean:
currents shield def: 280 (ethereal)
so base shield def : 186.6 (eth bonus is +50% ed)
I did expected the boost to be another 50% ed, so:
(base def)*[(50%ed-eth bonus) + (50%ed-cube bonus)]= base def *100%ed =base def * (1+100/100)= base def * 2
this is:
186*2=372 def after cube thing
But the fact is the shield got 420 def after cube, so the calculation is:
[(base def)*(50%ed-eth bonus)]*50%ed-cube bonus= [(base def)*(1+50/100)]*(1+50/100)=base def * 2.25
this is:
186.6*2.25=420 (well I did dropp decimals nvm that)
which is much nicer :PPP|||Quote:
use the cube socket recipe- its posted on the arreat summit. It is true- I made 2 eth merc fortitudes after the 1.11 patch before the end of last season that each had over 3000 defense. This also works with eth shields and helms, but not NOT SUPERIOR VERSIONS. The cube formula only works with eth regular unsocketed helms armors and shields:
1 Tal Rune + 1 Thul Rune + 1 Perfect Topaz + Normal Body Armor = Socketed Body Armor of same type
The number of sockets created will vary. The item must be normal and unsocketed. Low-quality items and superior items do not work. The item gets 1-4 sockets, randomly. However, the number of sockets is then restricted by the maximum number of sockets that base item with that ilvl can have. The chance to get X sockets in most armor is 1/4, (I.E: Mage plate has a max of 3 sockets, so it has a 2/4 [1/2] chance to get 3 socketss). The base of 6 was used in the ratios for all the above mentioned areas.
1 Ral Rune + 1 Thul Rune + 1 Perfect Sapphire + Normal Helm = Socketed Helm of same type
The number of sockets created will vary. The item must be normal and unsocketed. Low-quality items and superior items do not work. The item gets 1-3 sockets, randomly. However, the number of sockets is then restricted by the maximum number of sockets that base item with that ilvl can have. For example, if you have an item that can only have 2 sockets, there's a 5/6 chance of getting 2 sockets and a 1/6 chance of getting 1 socket.
1 Tal Rune + 1 Amn Rune + 1 Perfect Ruby + Normal Shield = Socketed Shield of same type
The number of sockets created will vary. The item must be normal and unsocketed. Low-quality items and superior items do not work. The item gets 1-4 sockets, randomly. However, the number of sockets is then restricted by the maximum number of sockets that base item with that ilvl can have. For example, if you have an item that can only have 2 sockets, there's a 5/6 chance of getting 2 sockets and a 1/6 chance of getting 1 socket.
Just wondering...if you create a socket eth armor like this and get the extra defense, will it stay that way after the correct this bug, or will de defense drop to the level of a "normal eth socketed armor"?|||Quote:
Just wondering...if you create a socket eth armor like this and get the extra defense, will it stay that way after the correct this bug, or will de defense drop to the level of a "normal eth socketed armor"?
It will stay.|||I'm just hearing of this bug for the first time. Did 1.11 cause this?|||Quote:
I'm just hearing of this bug for the first time. Did 1.11 cause this?
yes it did; I made use of it right before the ladder reset to make 2 eth fortitudes with over 3,000 defense each :)|||Interesting, this works with other armor types, right? Like shields?
Oh yeah, how about weapons, do they gain twice the eth damage bonus, too?
Mac Patch Bug?
I have had my Mac for 5 years and before today I only ever froze eight times. Today, since the patch, my Mac has freezed 11 times.
Every time it happens I have just pressed either Join or Create.
Four times this happened while I was trying to mule all the runes that the damned Countess gave me, these were most of the join game freezes.
It also happened when I went to make a trade with someone in a game they created.
Every time I freeze I have to reboot which means if it happens while muling I lose all my items, not to mention the fact I have to pay for my modem to reconnect because I am on dial-up.
Is this a Mac patch bug or is it happening to people with PCs as well? I was also thinking that it might have something to do with their anti-hack measures and it is somehow effecting muling as well. If it is anti-hack that does nothing to stop me being pissed, if anything it makes me more so, because I have never even used maphack, let alone d2loader and stuff, and it means I am being penalized for what others do.
Or could it just be B.Net server problems and the problem might go away in a few days? If it's a Mac patch bug then Blizzard has effectively just kicked all Mac users off B.Net.|||Make that thirteen times.
|||Quote:
Make that thirteen times.
It's a bug that unfortunately cannot be replicated, but it happens often enough that it needs to be addressed.
Mac Cube G4 1g, 1.25g RAM, GeForce 3 running 10.3.9
It is indeed a leave-then-rejoin bug that simply freezes the mac. I also get freezes durring gameplay which make the arrow (regular mouse cursor) appear.
Whenever I leave and rejoin a game that I made, I exit battle.net -- haven't had any problems on the join bug since then.|||I played it today with an powerbook (still 10.2.8) and had no problems.
*stkrause|||my mac freezes quite a bit now, usually when i exit a game. have to force quit.|||Quote:
my mac freezes quite a bit now, usually when i exit a game. have to force quit.
i've definatly notice more of this my mac too. usually when i try to create. havn't tried joining many though, only creating.|||17 freezes in 24 hours (and I slept for six) is not right.
I am only getting it when I try to join or create games.
If I could force quit I would, at least then I would have a chance at not loosing my items when trying to transfer, but this is a complete freeze and I have to reboot and wait for Disk First Aid to finish as well as my dial-up to reconnect.
NOT HAPPY.|||i fell better knowing it happens to other, cause then maybe it will be fixed
i simply can't play it anymore because of this
it crashes while i'm creating, joining, or exiting bnet... i just have to reboot.
g4 powerbook os9|||Quote:
i fell better knowing it happens to other, cause then maybe it will be fixed
i simply can't play it anymore because of this
it crashes while i'm creating, joining, or exiting bnet... i just have to reboot.
g4 powerbook os9
christ. i'm not having nearly as much trouble as some of you guys. i've always just been able to force quit d2 when its happened.
i'm using OS X v10.4.2 on a 1.25 GHz G4|||Are those of you with OSX using the Carbon version of Diablo II?
Melissa
Every time it happens I have just pressed either Join or Create.
Four times this happened while I was trying to mule all the runes that the damned Countess gave me, these were most of the join game freezes.
It also happened when I went to make a trade with someone in a game they created.
Every time I freeze I have to reboot which means if it happens while muling I lose all my items, not to mention the fact I have to pay for my modem to reconnect because I am on dial-up.
Is this a Mac patch bug or is it happening to people with PCs as well? I was also thinking that it might have something to do with their anti-hack measures and it is somehow effecting muling as well. If it is anti-hack that does nothing to stop me being pissed, if anything it makes me more so, because I have never even used maphack, let alone d2loader and stuff, and it means I am being penalized for what others do.
Or could it just be B.Net server problems and the problem might go away in a few days? If it's a Mac patch bug then Blizzard has effectively just kicked all Mac users off B.Net.|||Make that thirteen times.
|||Quote:Make that thirteen times.
It's a bug that unfortunately cannot be replicated, but it happens often enough that it needs to be addressed.
Mac Cube G4 1g, 1.25g RAM, GeForce 3 running 10.3.9
It is indeed a leave-then-rejoin bug that simply freezes the mac. I also get freezes durring gameplay which make the arrow (regular mouse cursor) appear.
Whenever I leave and rejoin a game that I made, I exit battle.net -- haven't had any problems on the join bug since then.|||I played it today with an powerbook (still 10.2.8) and had no problems.
*stkrause|||my mac freezes quite a bit now, usually when i exit a game. have to force quit.|||Quote:
my mac freezes quite a bit now, usually when i exit a game. have to force quit.
i've definatly notice more of this my mac too. usually when i try to create. havn't tried joining many though, only creating.|||17 freezes in 24 hours (and I slept for six) is not right.
I am only getting it when I try to join or create games.
If I could force quit I would, at least then I would have a chance at not loosing my items when trying to transfer, but this is a complete freeze and I have to reboot and wait for Disk First Aid to finish as well as my dial-up to reconnect.
NOT HAPPY.|||i fell better knowing it happens to other, cause then maybe it will be fixed
i simply can't play it anymore because of this
it crashes while i'm creating, joining, or exiting bnet... i just have to reboot.
g4 powerbook os9|||Quote:
i fell better knowing it happens to other, cause then maybe it will be fixed
i simply can't play it anymore because of this
it crashes while i'm creating, joining, or exiting bnet... i just have to reboot.
g4 powerbook os9
christ. i'm not having nearly as much trouble as some of you guys. i've always just been able to force quit d2 when its happened.
i'm using OS X v10.4.2 on a 1.25 GHz G4|||Are those of you with OSX using the Carbon version of Diablo II?
Melissa
Massive 1.13 Bug List
These Bugs Need Fixing!
All bugs are considered to be 1.12 and 1.13 problems. If not 1.13, then consider for later patches.
1) Waypoint Memory Leak - more then one waypoint be activated at about the same time
2) Kick Skills - The result of this bug is that the skills will not perform an attack server side until you let go of the mouse button
3) Kick Skills Part II - it looks like it originally was supposed to factorize the mLvl and cLvl of target/attacker like other skills, but ends using the mLvl of the target for both factors (which means not matter what you attack with it, the outcome of this formula will be the same).
4) Kick Skills Part III - due to incorrect code in the default melee damage creation func, kick skills will recieve elemental damage from weapons.
5) Psychic Hammer - copy/pasted code from Dragon Talons knockback section, with the same formula bug on (using [acronym="Monster Level"]mlvl[/acronym] twice).
6) Kick Damage Bonus - This stat isn't really used in vanilla, but the bonus is added twice instead of once, so +1 is in reality +2.
7) Power Strike Bug - The power strike SrvStFunc ignores the attack rating bonus from skills.txt
8) Smite Bugs - It wasen't ever meant to hit all the time, they do call the attacker/defender routine :!:, the problem is that they ignore the results of this, probably because they confused AND with OR.
9) Smite also does not set unitflag #64 which tells the game a skill has been executed successfully (which will cause all kinds of glitches that may seem irrelated), finally.
10) Smite used by monsters uses the damage specified for mode A2, even if they didn't use A2 to launch the skill (and even if they have no damage specified for A2).
11) The Hell Meteors (stuff in river of flame) is entirely broken, that is meteors flash around the screen but never land, and when they land only rarely explode, and when they explode they spawn just 1 flame, instead of a fire patch (like meteor, and like they worked before v1.10)
12) Boss events that are delayed by a timer (Poison Death, Cold Enchanted, Lightning Enchanted, Firegolem Explosion, Fire Enchanted, Lightning Nova on death and others) all use the same timeout Id, as a result each single time a timeout is being set, all of these events will execute their effects.
13) After using certain skills (Frenzy, Leap Attack, Whirlwind, Charge) the player can get stuck in place
14) The defense bonus to ethereal items will increase every time the item is used in a cube recipe that alters item flags
15) Monster elemental damage is completely broken, the function Blizzard uses to generate monster stats does not discriminate between the different elemental damage columns, as a result the game will use the damage from the first column for all elementally enchanted attacks the monster can do (=Gloam Bug), this is further complicated by the feature that elemental damage done by monsters is effected by their critical hit chance (eg. Fire Explosion can deal double damage).
16) Melee attacking monsters that do life, mana and stamina steal damage do twice the amount of damage indicated
17) Mana drain bosses actually do 512 times the proper damage!
18) Skills that use SrcDamage values other then 128 do not have the proper amounts of damage as SrcDamage is incorrectly (and inconsistently) applied throughout the code which may lead to damage being reduced more then it should, on missiles the situation is worse as some damage types are not reduced at all.
19) This is more of a design flaw then a bug, the game will apply the ED% bonus after other damage bonus have been applied, this is not a bug because there is no way to change the check order in vanilla (weapon damage and extra weapon damage use the same stat, so changing the order would break ED% completely).
20) Poison rises its ugly head again, blizzard confused Poison_Count stat with Poison_Length when it comes to applying SrcDamage to the missile damage, as a result skills like Multishot (that have SrcDamage other then 128) will end up with invalid poison duration when you have more then one poison source (this is related to the above but deserves a seperate place)
21) Monsters that are low on max hitpoints will end up having no life regeneration (value rounded down to 0)
22) Players that have >99% physical resistance can become immune to crushing blow, as the function used for Crushing Blow does not discriminate between monsters and players
23) Summoned monsters will recieve extra attack rating and defense equal to 100% of the value listed in MonLvl.txt for their mLvl (noratio is ignored)
24) Monsters that use ranged attacks that require attack rating (Quill Rats, Blow Pipers etc) have twice the attack rating they should have
25) Throwing and shooting skills that add an attack rating bonus to the missiles do not add their bonus (it passes 0 to the function instead of reading the bonus of the missile)
26) Blessed Aim and Penetrate use the same state, as a result the two skills can cancel each other out because they will replace each others state statlists
27) There are many places in the code where Blizzard forgot to handle life and damage in 256ths, this results in 1/256 life assigned to units, which can cause all kinds of weird behavior
28) Evil Urn were not meant to spawn spiders
29) The ObjGroup data listed in levels.txt is very broken, some groups have a chance of 0% to spawn, other groups do not contain objects and thus just decimate the amount of objects spawning in the area
30) Curse Resistance is checked in the same function that handles most time-based statlists assigned to units, except for a few cases that are handled specially it will be applied to every time-based statlist, which means it will reduce the duration of positive effects as well for Fade (assassin skill)
31) The Frozen Horror arctic blast incorrectly triggers events, which can lead to a sprite overflow when the skill is cast on a Sorceress using Chilling Armor
32) All lookups for records in MonType.txt done on the client will incorrectly use the record count from MonProp.txt
33) This isn't a real bug, but then again it does cause some likely unintentional behavior (such as generating nests as bosses), the game uses nmon instead of umon to pick bosses after normal, which means they are picked out of the normal enemy pool instead of the special boss pool
34) Magic Pierce and Magic Skill Damage Stats
These stats, while not being used by vanilla, are inconsitently referenced by the code, so should they chose to use them in the future without fixing this mess, expect new bugs
35) Several boss death effects do not have NoMultishot set to true, as a result encountering and killing them if they have the Multishot UMod will spawn their death effect up to five times (Shenk et al.)
36) Extra oblivion knights added by v1.10 and v1.11x do not recieve the proper components, which means they show up with mismatching glow around their hands, this is caused by them not checking the BaseId, but rather checking the HcIdx
37) The game does not display affix-colors for Crafted Items because they were forgotten in the item-color function inside D2Client.dll
38) The fix to the old chest glitch has broken some act boss drops, some act bosses were originally meant to drop 7 rather then 6 items
39) The target seeking flags used on the client and server for missiles that automatically seek a target (Guided Arrow etc) are not identical, this can sometimes lead to different units being targeted on both ends, which makes the missile vanish
40) The last batch of palettes in RandTransforms.dat is never used by the game because they forget to adjust the index in the only lookup that really matters (the one in the drawing function)
41) Trapped souls that drop their items with a delay (those that go up in flames when you touch them), do not take into account your characters gold and magic find, they pass NULL to the tc function
42) Blizzard copy/pasted that Desert level for the uber quest in v1.11x, and forgot to set the Waypoint Id to -1 (255), waypoint lists are constructed clientside, and we all know what that means
43) Uber Diablo (or the Clone, one of the two) doesn't use the diablo-mode chart entry, instead he uses the same normal monsters use, which can cause unexpected problems
44) Treasure Class Upgrade Bug
This is a critical bug, the function does not check whenever it is reading the last record inside the TCEX BinImage, as a result it can end up traversing random memory until it asplodes
45) Some poison clouds have invalid hitclass set in Missiles.txt, as a result they play the same sound like a javelin does when you walk into them, which can be very annoying. The trail left by Plague Javelin doesn't do damage, because of a typo in the serverside movement function
46) Some quest flags are being reset when they shouldn't allowing you to recieve Andariels and Duriels quest drop infinite times until you visit Act II.
47) The guest monsters added in v1.11b (and also the Diablo Clone) have broken chains which will lead to various (but not really noteworthy) glitches
48) Broken Runewords
Some of the property codes assigned to the v1.11x runewords are not spelled properly (which will make the game quit assigning stats after the bad property is reached, which in itself is a bug, it should just skip it, like it does elsewhere)
49) There are several places where the walkable flags in the tiles are not properly set, allowing players to go to places they shouldn't be able to (eg. teleporting into walls), this also applies to monsters spawning on inaccessable islands (for example in the Act III sewers or the summoned creatures at Gibbding location)
50) Some items spawn with affixes they shouldn't recieve (such as circlets listed for both series of damage reduction, instead of only the first one meant for circlets, shields with AR), Small Charms should be able to recieve the Lucky prefix, instead the small charm version is assigned to large charms, some affixes have invalid itemtypes listed, which prevents them from spawning on those types (staves noteably listed as staff and not staf). There also are some problems with the qLvl and reqLvl of some affixes (ex. King's and Master's have the same qLvl and among the resistance affixes the strongest affixes have a lower level then a bunch of weaker ones available on the same items [IIRC] <keyword rods>), another incarnation of this is the Lizard's prefix on small charms, there are two variants available at the same qLvl that add different values (rather then one affix only), the weaker one was meant to be replaced by the later (I assume this because thats how some others like this are set up, the masters of copy/paste just forgot to edit the line...)
51) The Uber Quest Items drop in single player as well, where they are completely useless (quest drops like these should be hardcoded...)
52) The AiParams for some monsters (Vampires noteably) are incorrect, leading to the earliest species being more aggressive then the end-game variants, the Guest Monsters do not have their Ai adjusted at all, which means most of them act like Act1-2 enemies
53) Certain things are handled clientside that should never be controlled by the client, for very obvious reasons I wont mention what, because these things are presently not known to the armies of seething scriptkiddiots and I have no intention to feed them.
54) Trang-Oul's transformation bug (which is even listed on the Arreat Summit) - that being locked as a Vampire locks everything from attack, cast, and open-things speed at a vampire's, rather than the player's actual. It's really annoying to get "frozen" after kicking a barrel.
55) Santard of Heroes still do nothing.
56) Fire Enchnted damage got doubled, despite what stated in 1.13 patch notes.
57) Diablo Clone spawn mechanism encourage douping
58) TPPK problem: you all know this all too well
59) PK problem: doesn�t require mutual hostility-declaring to be able harm other players, deactivating hostility from one side result the other player still being able to harm the one renounced hostility.
60) Massive rune duping due to the rarity of high rune drops
61) Anya Resistance Bug (after player�s character�s death the resistances given by the Act5 questreward scroll disappears in effect but not at the shown value of character sheet, and only retruns when leaving the game)
62) Trang-Oul's Avatar Cast Rate Bug (it slows down the player for no known reason)
63) The client will continue executing the ClientDoFunc for skills even after you go into hit recovery, which leads to blank zeal swipes and ghost missiles that do not hit anything because they don't exist serverside (affects Fury, Zeal and Strafe),
dodge / avoide / evade interrputs Fend, Jab and Strafe in the way the animation continues but no damage is done
64) Glitch Rushing (Being able to complete Baal Quest by a lvl 1 character)
65) Game is Full Bug
66) Lying Character Screen (Speficically with +Damage modifiers)
67) Druid Spirits get 2 immunity on Nightmare and 1 in Hell, what makes them weaker contrary to all gamedesign.
68) When a nonladder character tries to join a ladder game, the following message is displayed:
Game does not exist.
69) When a ladder character tries to join a nonladder game, the following message is displayed:
A nonladder character can't join a ladder game.
70) The inferno-bug is still present. (skills that do damage per frame insted per hit deal half the listed damage)
71) The skill Sanctuary does not work correct: the Enhanced Damage doesn't work at all.
72) Game stops and bring back to chatroom when trying to revive mercenary without enough money at Qual'keh (act V NPC)
73) "% launch skill when attack/struck/die/level up" is not shown on item description in Diablo Spanish's version
74) Barbarian Leap/Leap Attack - The bug where you lose the ability to cast these skills until you exit and rejoin the game is fairly annoying and might even get you killed in hardcore.
75) Merc Equipment Auras - Having to reequip your merc's Insight/Harmony/etc to turn on the aura every time you resurrect him/her is a minor annoyance, but a big time waster for everyone.
76) Slowed Baal - When you use Clay Golem, Decrepify or items with Slow Monster on Baal, it completely neuters him. Because of the way his animations are set up, he constantly interrupts himself while slowed, never finishing one animation before starting the next. This bug prevents him from using teleport and many of his other dangerous skills, making him one of the easiest bosses to slaughter.
77) 1.11 patch gave only 7 runeword instead of 10 what patch notes says
78) While playing on the PTR today, my party and I noticed something strange while we were gathering the pieces of the staff in Act 2. On the Quest screen, the sixth and final quest box read "Talk to Meshif" before the party had killed Duriel. I suspect the player had beaten Duriel in a previous game, but that player left before answering my inquiry.
79) Dire Wolf Bug (Dire Wolf often trying to eat corpse that they cant eat. (for example corpse of Skeleton or Thorned Hulk)
80) Volcano Bug (it cant be using on very narrow place, for example stairs in arcane sanctuary and it cant be using on monsters that stay near by some objects)
81) the blue hireling (when the merc is chilled, so coloured blue, change map (like Tower Level. doessn�t work on open spaces as there no map-redraw happens). When map is redrawn the merc loos slowness, but isn�t coloured back to its original state. Rarely this also happens with the poison effect (colour green, cause unknown)
82) New glitch with Hellforge Hammer: it can be found more then one time by the same person.
83) bug with Wirst's Leg: Runewords do not work in this weapon at all. I think because it is handled as unque item, despite it is a regular item.
84) new bug: quest item upgrade is possible. Their item type is changed to "hand axe", quality is turned to normal instead of exceptional (�unique normal to exceptional� Horadric recipe is used)
85) Im not sure if the palace glitch has been addressed but. I do find it anoying when another player goes in Palace celler, canyon or arcane way points. (so people without completing the Horadric Staff can talk to Jehrim)
86) Damage/Defense Reducing skills: They�ve been broken since the game has been released� they�re included in the damage calculation instead of using the end-result damage to calculate it.
87) thorns stacked dmgreduce in PvP (first dmg caused to target player is reduced, then the reduced number is reduced again when reflected to the attacker)
88) Fire Golem: My problem with this is that 1) He doesn�t absorb the fire damage period. It�s immune but it doesn�t get healed at all.
89) The two top lightning traps are actually so strong that at Nihlatak they can cause a bug killing Nihlatak so fast and from far away that the quest turns uncomplatable.
90) repairing harpoons and of the sort will not increase the quantity above 20, which is stupid as HELL because the cross-arrows show up at 15 or less, plus 20 isn't very much to work with. Also, it may just be on increased stack size weapons. I have 2 harpoon-type weapons and both were 110+ quantity, won't freaking repair over 20. BIG DEAL TO ME. I've not tried it with any other weapons though, so look out.
91) Sorceress Timerbug which came up with 1.10 and got ofc never fixed ......
92) bug: the assassins Dragon Talon skill first uses the monsters physical resistances, then converts the unresisted physical damage to its explosion damage, then uses the monsters fire resistances to further more lower the damage. This way it uses to kind of resistances instead of one, and is absolutly useless against physical immun monsters for what this skill was invented.
93) Act 5 Quest #5 - destroy the 3 Ancients Barbarians. I use Cloak of Shadow on them, hit them a few hit, then the game crash
94) Grief Smite Bug (the damage of Grief applied fully when Smite skill is used)
95) While using Impale Critical Strike (and maybe Double Strike?) abilities do not work.
96) Ice skating in town (run, then hold shift. The character�s walking animation stops, but the movement does not)
97) charge desync (clientside charge is faster, therefor serverside the character is shown at an incorrect place, resulting practical invisibility)
98) respec-aurastack glitch (when respeced the visual parts of skills will remain, and charactersheet modifiers falsly remain until skill is recast or rejoned to the game. Not sure what happens with period-skills, like Enchant, Werewolf form, Energy shield, Venom etc.)
99) Sometimes the mercenary turns invisible. It functions, but have no visible component. The provided aura is also not visibly on the affected targets, but still works correctly.
100) Sometimes when player's character gets poisoned (eg. in Act2 from Greater Mumies) the poison duration is unexpectedly long and the damage unreasonably high. Eg. when normally (99% of the time) the poison-effect damages 1/5 of the mximum health of the player this bugged damage will cause 3 times the maximum health the character have very fast.
I suspect here both poison lenght reduced and resistance of the player isn't applied.
101) Duping
102) FE + CE bug (when both ability is present on a boss monster, their effect activates twice on Nightmare difficulty only.)
103) Skating Assassin bug
104) With Charged Strike / Lightning Strike use Critical Strike /Doube Strike / Crushing Blow / Open Wounds or anything like that that depend on melee attack
105) gambling on classic from gheed act 1 norm
has throwing weapons in the gambling screen (unidentified), which when purchased are always 'white' superior throwing weapons, not magic/rare/unique
106) Dragon Talon attacks twice for every "hit" (but this bug is predicated on other bugs in various kick skills).
107) The knockback chance (at assassin finishing moves) factors slvl vs. mlvl, but incorrectly uses mlvl as a subtraction (leading to the end result being only slvl).
108) If somebody completes Den of Evil in a game, and somebody who hasn't done the quest joins the game, Akara will give them the option of respec as a chat option, but it does nothing. (May require the other player to be in game already, and then rejoin, but not get the quest done)
109) Due to typos in the column headers of weapons.txt, armor.txt, and possibly other places, Hratli incorrectly has a MagicLevel of 1. Her(?) name is misspelled as Hralti in those headers.
110) Oblivion Knights never attempt to heal their allies (they select a target to heal, however).
111) Fetish Shamans never use their Fetish Aura skill.
112) Fangskin, the superunique in the Viper Temple level 2, never drops any items in hell. This is because he has an incorrect Treasure Class.
113) Frozen Horrors in Act 5 cast Arctic Blast, which is incorrectly flagged to trigger events. This can easily cause a sprite limit overflow when they cast it on a Sorceress with Chilling Armor (or a character with a "Fortitude" that has cast Chilling Armor on them).
114) The "Fires Magic Arrows" property of some unique items doesn't correctly account for any other missile functions, leading to the arrows simply being normal arrows that (to the client) look like magic arrows. (I�m not sure if this bug has been corrected. Witchwild String seemed to work for me.)
115) Dragon Claw: If the first claw attack hits, the second one does normal damage and does not receive the charged-up bonus. (Also true for any multiply-hit finishing-moves of the assassin)
116) Tomb Viper variants in Act 5 in the "Halls" section of the Nithalak quest incorrectly apply their physical damage per frame when attacking with their "poison spear" attack. The attack should use their poison damage alone.
117) Prevent Monster Heal doesn't get applied from your merc's items.
118) Aura-stacking bug - When a character in-game equips 2 pieces of equipment which add the same active aura (example, equipping a dream runeword Hat and a dream runeword Shield both with lvl 15 holy shock auras), the aura's level will be stacked up (giving a level 30 holy shock aura).
119) However you can re-apply the levels repeatedly by trying and failing to trade with someone, triggered by trying to trade an item to a player when his inventory is full, trying to trade a 1-per-inventory item to a player that already has the same such item (trying to trade annhilus to a player holding one already), generally any situation where the trade can't go through for whatever reason. This will re-apply one (or both?) of the item's aura to the existing stacked aura, in our double dream case, giving you a level 45 holy shock. The stacking procedure can be further repeated and the effects further stack with additional failed trades.
120) When the window is stretched, the mouse still moves as if the window was the regular 800x600. This means that when you move the mouse completely off the window on a large resolution, it doesn't appear until so much further down.
121) wp: somtimes the town-wp is blue besides the currently used wp.
122) the change to duriel to allow the essence to drop screwed up his treasure class
he now sometimes doesnt drop a TP at all and sometimes drops nothing but town portals (lol)
123) When i create a game or leave one, the window moves back to its starting postion.... which isnt good at all, and if I recall correctly that didnt happen before 1.13
124) To reproduce: Buy a tome of town portal, set it to a F# key, make a town portal anywhere. Go back to town via a waypoint and put that town portal tome in the stash. Buy a new tome of town portal and go anywhere via a waypoint. This will not cast a town portal via the right mouse button when selected with the F# shortcut key (only the animation happens). A town portal can be cast with a right mouse click of the tome in the inventory though. If the original town portal tome is retrieved from the stash the right mouse button will cast a tp when the correct F# shortcut is selected.
125) char type = barb...while duel wielding, holding 1 weapon the damage adjusts as it should. adding a 2nd weapon for the first time the damage adjusts as it should in the character sheet. replacing either weapon with a 3rd , the damage remains unchanged. from that point on, in order to see the damage adjust i had to unwield all weapons. closing the inventory and character sheet windows, the "incorrect" damage was still listed in the character sheet when character window is reopened.
126) If you create a new game or join to an existing game or quit from a game and previously moved the window anywhere from the starting position (from the middle), it will jump back to it's original position.
127) If you travel to the next Act with quest (not through waypoint) and previously moved the window anywhere from the starting position (from the middle), it will jump back to it's original position.
128) The last charge on any summoning skill from item does not work (the summoned creature immediatelly disappears).
129) Hydra - Decreased base speed of Hydra projectile.
The projectile speed seems to have been decresed instead of being increased as stated in the patch notes. If they were meant to be increased, it is a bug. Only for players, ingame monsters work fine.
130) When an assassin wields a +2 DT claw, her DT skill level does not go up. Doesn't matter which hand she holds it in. +2 skills claw works, but not +2 Dragon Tail claw.
131) I have the option to respec in Hell from Akara, although I have not completed the Den of Evil quest.
I only played by myself in private rooms and didn't complete the quest in Normal or Nightmare either.
132) I had Thunderstorm active when I was killed then left the game and rejoined with a new character (played in hardcore). On my sons screen, the Thunderstorm graphics and sound was still flashing every few seconds.
133) When i have died, and click on my corpse. Tele is no longer mapped to a hot key. This also happends wheneven i am out of tele charges. Happens with any ability used from charges. This is when using items with charges only. Eg. Enigma dont have that problem.
134) When I use stat-up charms like hellfire charm, ani charm, 2 strength small charm, 1 dexterity charm
in my monitor my character is dressed
But in the others monitors my character is undressed
135) Strenght bug: When a piece of equipment is put on a character that only reach the Strenght (DEX etc.) requirement of the item with other items (like charms), and the item provides the same bonus the item remains usable when the equipments that helped to put on the character the euipment in question are removed. (Eg. the character has 10 STR, weapon has STR requirement of 20, and has an affix what provieds 10 STR. Player aquires a +10 STR charm, puts on the weapon, drops the +10 STR charm, and the weapon remains fully active.)
136) I used my normal respec and nightmare respec at akara. i then entered hell. after i got to act 5 i visited act 1 and when i talked to Akara the reset skill/stats option was available even though i didn't complete the den quest. After I clicked it and also clicked Ok nothing happened. I could do this as many times as I wanted. After clearing the den i tried again and then it worked and the option was no longer available.
137) waypoints aren�t active when you make a new game and visit an already activated wp on foot (not through the wp itself)
138) Oblivion Knights (located ANYWHERE) don't cast the curse Lower Resist anymore.
139) when moving and hit by decrep the slowing effect (not sure about its other effects) do not work
140) On the Barb there is a spelling error on one of the skill icons. It says "Pole Arm Mastery" instead of "Polearm Mastery" (the space). All the weapons say "Polearm Class".
141) "Drop barabarian" bug/exploit (bug doesnt appear in Single Player games).
Barbarian, wich have at least one point in each skill at Masteries tree, under Shout, Battle Orders, Battle Command,
Enchant, Venom buffs and with few auras (Fanaticism, Holy Shock, Holy Fire) causes droping from game other characters.
142) Wrong Paladin's Smite damage shown at character screen when items with "+ Damage" attribute equipped.
143) Sorceress skill Telekinesis and Waypoints. When Telekinesis casted from far distance on waypoint it
opens waypoint screen but waypoints at that case does not trigger.
144) "Invisible missiles". Missiles like Bone Spirit or Blessed Hammer can become invisible for players. In case of skill Blessed Hammer, missiles become invisible when Paladin moves around very fast when casting Blessed Hammer (with FRW attribute on items, Charge, Vigor).
145) radament & countess reported sometimes missing
146) when creating a game in window mode and tabbing back into diablo there is a weird wind like howling sound in the backround. to fix this i have to go to sounds and move the sound bar which is pretty annoying to do every time (windows xp)
147) Leaper cannot be killed (0 hp monster)
148) whirlwind death disconnection
description:
in pvp, when whirlwinding, sometimes when i die while in the whirlwind animation, it freezes at the "hit escape to revive in town message" and sits there for an annoyingly length of time, then tells me my connection has been interrupted.
149) not sure if this has been noted yet but i was going over the barb skill tree and saw that the mana cost of Double Swing was -1 (should show 0 as using the skill doesn�t generate mana)
150) you can access Waypoints in town using telekenesis, however if you've just spawned in the game and haven't moved before attempting to use a waypoint via telekenesis then you cannot travel to any other waypoints until you move.
151) Blaze don't give 1% damage per point to firewall.
152) Dual-wield in were-forms is bugged.
153) i gave my act 1 mercenary a magic bow called 'composite bow of transcendence', an ordinary composite bow with extra 18 min dmg option
when i looked at her stat, her dmg was shown as 227-188 which didnt make any sense
i tried with other bows with min dmg option and they seemed to be fine until i found a 'long bow of transcendence', an ordinary long bow with extra 19 min dmg option
funnily these two bows are shown to have the same dmg (22-23) even though their original dmg are different
(long bow: 3-10 and composite bow: 4-8)
when i gave her this bow, the min dmg also showed up higher than the max dmg
also the max dmg of long bow was a little bit higher than that of composite bow, 227-194 (which is true but they both are shown to have the same dmg, 22-23)
i have tried these bows myself and my dmg is shown as 37-38 for both bows
i personally think that 22-23 dmg is because their normal max dmg is lower than 18 or 19 making the min dmg as 'normal min dmg + extra dmg' and the max dmg as 'min dmg + 1'
but i dunno why the min dmg is shown higher than max dmg on the mercenary
(Simply put: the game-mechanic should have been adjusted with a line what�d tell if min. dmg is > max. dmg, then min dmg = max. dmg�1 or if min. dmg is > max. dmg, then max. dmg = min. dmg+1. This later whould be preferred to avoid balance problems with certain skills.)
154) Hsarus' Iron Heel (Set Chain Boots) with an Assassin and it doesn't display the kick damage that goes with it of 6-12. It goes is applied and everything though.
155) When in WorldStoneKeep�;s levels and fighting without walking around (happens when many monsters are present and using a somewhat low damage weapon) the AI thinks the player don�t do anything, so initiates the elemental attack �from Baal�. The effect actually doesn�t come to play, but the laughing effect do happen from this effect. (Try it on higher difficulty where the AI is more active.)
156) When defeating Baal Tyrael appears fixedly at the location where Baal is defeated. Compared to Tyrael the red portal appears at a fixed location. The result of this is that sometimes the portal�s location is inaccessible.
Submitted by Erichvon, after gathering the list from the Battle.net - Diablo II - Test Realm Forum
D2 Test Realm|||Holy ****. I haven't read that, but assuming it's accurate...thanks for posting, but to be honest, I doubt that blizz cares...
Edit: I read the first few....these are not all problems with 1.13. Many are issues (features?) of 1.12. It seems a bit dishonest to pretend that they are problems introduced by 1.13.
Maybe it should be labeled "comprehensive" or "continuing"?|||Some are from 1.13 as you said, but I think if I'm right, that the "suggestions for future patches" fits into this thread. Correct me if I'm wrong though.
(O) Changed title of thread.
(O) Added a brief description at the top.|||Quote:
Some are from 1.13 as you said, but I think if I'm right, that the "suggestions for future patches" fits into this thread. Correct me if I'm wrong though.
Yeah.
Quote:
(O) Changed title of thread.
Quote:
(O) Added a brief description at the top.
Much better, thanks.|||Well you're mighty welcome, one could hope that blizzard would fix all bugs. Another person thinks this is impossible and the guy down the street is indifferent. No one is going to know if they'll fix it, except Blizzard.|||Some of those arent bugs but "features"
e.g. no rare throwing weapons in classic
+damage to smite (from grief)
standards of heroes are supposed to do nothing (just like that gem thingie in the lobby)|||i hope they aint going to enable that unique ring from wiki pages which has been disabled. if they going to enable that ring....|||Read all of those and only have a comment on this one,
"145) radament & countess reported sometimes missing"
I think here is that Radament and the Countess ocassionaly spawn outside of their area. Like the countess (since lvl5 is always the same) spawns in the top right passage (leading to the middle room with chest) by the doorway instead of in the room with the chest.|||Regardless, 100+ bugs are ridiculous, especially with the simplicity of d2's programming.|||wow, great work. I haven't noticed a lot of these bugs but some of them seem like they really need to be fixed. Hopefully blizzard reads this...
-brick
All bugs are considered to be 1.12 and 1.13 problems. If not 1.13, then consider for later patches.
1) Waypoint Memory Leak - more then one waypoint be activated at about the same time
2) Kick Skills - The result of this bug is that the skills will not perform an attack server side until you let go of the mouse button
3) Kick Skills Part II - it looks like it originally was supposed to factorize the mLvl and cLvl of target/attacker like other skills, but ends using the mLvl of the target for both factors (which means not matter what you attack with it, the outcome of this formula will be the same).
4) Kick Skills Part III - due to incorrect code in the default melee damage creation func, kick skills will recieve elemental damage from weapons.
5) Psychic Hammer - copy/pasted code from Dragon Talons knockback section, with the same formula bug on (using [acronym="Monster Level"]mlvl[/acronym] twice).
6) Kick Damage Bonus - This stat isn't really used in vanilla, but the bonus is added twice instead of once, so +1 is in reality +2.
7) Power Strike Bug - The power strike SrvStFunc ignores the attack rating bonus from skills.txt
8) Smite Bugs - It wasen't ever meant to hit all the time, they do call the attacker/defender routine :!:, the problem is that they ignore the results of this, probably because they confused AND with OR.
9) Smite also does not set unitflag #64 which tells the game a skill has been executed successfully (which will cause all kinds of glitches that may seem irrelated), finally.
10) Smite used by monsters uses the damage specified for mode A2, even if they didn't use A2 to launch the skill (and even if they have no damage specified for A2).
11) The Hell Meteors (stuff in river of flame) is entirely broken, that is meteors flash around the screen but never land, and when they land only rarely explode, and when they explode they spawn just 1 flame, instead of a fire patch (like meteor, and like they worked before v1.10)
12) Boss events that are delayed by a timer (Poison Death, Cold Enchanted, Lightning Enchanted, Firegolem Explosion, Fire Enchanted, Lightning Nova on death and others) all use the same timeout Id, as a result each single time a timeout is being set, all of these events will execute their effects.
13) After using certain skills (Frenzy, Leap Attack, Whirlwind, Charge) the player can get stuck in place
14) The defense bonus to ethereal items will increase every time the item is used in a cube recipe that alters item flags
15) Monster elemental damage is completely broken, the function Blizzard uses to generate monster stats does not discriminate between the different elemental damage columns, as a result the game will use the damage from the first column for all elementally enchanted attacks the monster can do (=Gloam Bug), this is further complicated by the feature that elemental damage done by monsters is effected by their critical hit chance (eg. Fire Explosion can deal double damage).
16) Melee attacking monsters that do life, mana and stamina steal damage do twice the amount of damage indicated
17) Mana drain bosses actually do 512 times the proper damage!
18) Skills that use SrcDamage values other then 128 do not have the proper amounts of damage as SrcDamage is incorrectly (and inconsistently) applied throughout the code which may lead to damage being reduced more then it should, on missiles the situation is worse as some damage types are not reduced at all.
19) This is more of a design flaw then a bug, the game will apply the ED% bonus after other damage bonus have been applied, this is not a bug because there is no way to change the check order in vanilla (weapon damage and extra weapon damage use the same stat, so changing the order would break ED% completely).
20) Poison rises its ugly head again, blizzard confused Poison_Count stat with Poison_Length when it comes to applying SrcDamage to the missile damage, as a result skills like Multishot (that have SrcDamage other then 128) will end up with invalid poison duration when you have more then one poison source (this is related to the above but deserves a seperate place)
21) Monsters that are low on max hitpoints will end up having no life regeneration (value rounded down to 0)
22) Players that have >99% physical resistance can become immune to crushing blow, as the function used for Crushing Blow does not discriminate between monsters and players
23) Summoned monsters will recieve extra attack rating and defense equal to 100% of the value listed in MonLvl.txt for their mLvl (noratio is ignored)
24) Monsters that use ranged attacks that require attack rating (Quill Rats, Blow Pipers etc) have twice the attack rating they should have
25) Throwing and shooting skills that add an attack rating bonus to the missiles do not add their bonus (it passes 0 to the function instead of reading the bonus of the missile)
26) Blessed Aim and Penetrate use the same state, as a result the two skills can cancel each other out because they will replace each others state statlists
27) There are many places in the code where Blizzard forgot to handle life and damage in 256ths, this results in 1/256 life assigned to units, which can cause all kinds of weird behavior
28) Evil Urn were not meant to spawn spiders
29) The ObjGroup data listed in levels.txt is very broken, some groups have a chance of 0% to spawn, other groups do not contain objects and thus just decimate the amount of objects spawning in the area
30) Curse Resistance is checked in the same function that handles most time-based statlists assigned to units, except for a few cases that are handled specially it will be applied to every time-based statlist, which means it will reduce the duration of positive effects as well for Fade (assassin skill)
31) The Frozen Horror arctic blast incorrectly triggers events, which can lead to a sprite overflow when the skill is cast on a Sorceress using Chilling Armor
32) All lookups for records in MonType.txt done on the client will incorrectly use the record count from MonProp.txt
33) This isn't a real bug, but then again it does cause some likely unintentional behavior (such as generating nests as bosses), the game uses nmon instead of umon to pick bosses after normal, which means they are picked out of the normal enemy pool instead of the special boss pool
34) Magic Pierce and Magic Skill Damage Stats
These stats, while not being used by vanilla, are inconsitently referenced by the code, so should they chose to use them in the future without fixing this mess, expect new bugs
35) Several boss death effects do not have NoMultishot set to true, as a result encountering and killing them if they have the Multishot UMod will spawn their death effect up to five times (Shenk et al.)
36) Extra oblivion knights added by v1.10 and v1.11x do not recieve the proper components, which means they show up with mismatching glow around their hands, this is caused by them not checking the BaseId, but rather checking the HcIdx
37) The game does not display affix-colors for Crafted Items because they were forgotten in the item-color function inside D2Client.dll
38) The fix to the old chest glitch has broken some act boss drops, some act bosses were originally meant to drop 7 rather then 6 items
39) The target seeking flags used on the client and server for missiles that automatically seek a target (Guided Arrow etc) are not identical, this can sometimes lead to different units being targeted on both ends, which makes the missile vanish
40) The last batch of palettes in RandTransforms.dat is never used by the game because they forget to adjust the index in the only lookup that really matters (the one in the drawing function)
41) Trapped souls that drop their items with a delay (those that go up in flames when you touch them), do not take into account your characters gold and magic find, they pass NULL to the tc function
42) Blizzard copy/pasted that Desert level for the uber quest in v1.11x, and forgot to set the Waypoint Id to -1 (255), waypoint lists are constructed clientside, and we all know what that means
43) Uber Diablo (or the Clone, one of the two) doesn't use the diablo-mode chart entry, instead he uses the same normal monsters use, which can cause unexpected problems
44) Treasure Class Upgrade Bug
This is a critical bug, the function does not check whenever it is reading the last record inside the TCEX BinImage, as a result it can end up traversing random memory until it asplodes
45) Some poison clouds have invalid hitclass set in Missiles.txt, as a result they play the same sound like a javelin does when you walk into them, which can be very annoying. The trail left by Plague Javelin doesn't do damage, because of a typo in the serverside movement function
46) Some quest flags are being reset when they shouldn't allowing you to recieve Andariels and Duriels quest drop infinite times until you visit Act II.
47) The guest monsters added in v1.11b (and also the Diablo Clone) have broken chains which will lead to various (but not really noteworthy) glitches
48) Broken Runewords
Some of the property codes assigned to the v1.11x runewords are not spelled properly (which will make the game quit assigning stats after the bad property is reached, which in itself is a bug, it should just skip it, like it does elsewhere)
49) There are several places where the walkable flags in the tiles are not properly set, allowing players to go to places they shouldn't be able to (eg. teleporting into walls), this also applies to monsters spawning on inaccessable islands (for example in the Act III sewers or the summoned creatures at Gibbding location)
50) Some items spawn with affixes they shouldn't recieve (such as circlets listed for both series of damage reduction, instead of only the first one meant for circlets, shields with AR), Small Charms should be able to recieve the Lucky prefix, instead the small charm version is assigned to large charms, some affixes have invalid itemtypes listed, which prevents them from spawning on those types (staves noteably listed as staff and not staf). There also are some problems with the qLvl and reqLvl of some affixes (ex. King's and Master's have the same qLvl and among the resistance affixes the strongest affixes have a lower level then a bunch of weaker ones available on the same items [IIRC] <keyword rods>), another incarnation of this is the Lizard's prefix on small charms, there are two variants available at the same qLvl that add different values (rather then one affix only), the weaker one was meant to be replaced by the later (I assume this because thats how some others like this are set up, the masters of copy/paste just forgot to edit the line...)
51) The Uber Quest Items drop in single player as well, where they are completely useless (quest drops like these should be hardcoded...)
52) The AiParams for some monsters (Vampires noteably) are incorrect, leading to the earliest species being more aggressive then the end-game variants, the Guest Monsters do not have their Ai adjusted at all, which means most of them act like Act1-2 enemies
53) Certain things are handled clientside that should never be controlled by the client, for very obvious reasons I wont mention what, because these things are presently not known to the armies of seething scriptkiddiots and I have no intention to feed them.
54) Trang-Oul's transformation bug (which is even listed on the Arreat Summit) - that being locked as a Vampire locks everything from attack, cast, and open-things speed at a vampire's, rather than the player's actual. It's really annoying to get "frozen" after kicking a barrel.
55) Santard of Heroes still do nothing.
56) Fire Enchnted damage got doubled, despite what stated in 1.13 patch notes.
57) Diablo Clone spawn mechanism encourage douping
58) TPPK problem: you all know this all too well
59) PK problem: doesn�t require mutual hostility-declaring to be able harm other players, deactivating hostility from one side result the other player still being able to harm the one renounced hostility.
60) Massive rune duping due to the rarity of high rune drops
61) Anya Resistance Bug (after player�s character�s death the resistances given by the Act5 questreward scroll disappears in effect but not at the shown value of character sheet, and only retruns when leaving the game)
62) Trang-Oul's Avatar Cast Rate Bug (it slows down the player for no known reason)
63) The client will continue executing the ClientDoFunc for skills even after you go into hit recovery, which leads to blank zeal swipes and ghost missiles that do not hit anything because they don't exist serverside (affects Fury, Zeal and Strafe),
dodge / avoide / evade interrputs Fend, Jab and Strafe in the way the animation continues but no damage is done
64) Glitch Rushing (Being able to complete Baal Quest by a lvl 1 character)
65) Game is Full Bug
66) Lying Character Screen (Speficically with +Damage modifiers)
67) Druid Spirits get 2 immunity on Nightmare and 1 in Hell, what makes them weaker contrary to all gamedesign.
68) When a nonladder character tries to join a ladder game, the following message is displayed:
Game does not exist.
69) When a ladder character tries to join a nonladder game, the following message is displayed:
A nonladder character can't join a ladder game.
70) The inferno-bug is still present. (skills that do damage per frame insted per hit deal half the listed damage)
71) The skill Sanctuary does not work correct: the Enhanced Damage doesn't work at all.
72) Game stops and bring back to chatroom when trying to revive mercenary without enough money at Qual'keh (act V NPC)
73) "% launch skill when attack/struck/die/level up" is not shown on item description in Diablo Spanish's version
74) Barbarian Leap/Leap Attack - The bug where you lose the ability to cast these skills until you exit and rejoin the game is fairly annoying and might even get you killed in hardcore.
75) Merc Equipment Auras - Having to reequip your merc's Insight/Harmony/etc to turn on the aura every time you resurrect him/her is a minor annoyance, but a big time waster for everyone.
76) Slowed Baal - When you use Clay Golem, Decrepify or items with Slow Monster on Baal, it completely neuters him. Because of the way his animations are set up, he constantly interrupts himself while slowed, never finishing one animation before starting the next. This bug prevents him from using teleport and many of his other dangerous skills, making him one of the easiest bosses to slaughter.
77) 1.11 patch gave only 7 runeword instead of 10 what patch notes says
78) While playing on the PTR today, my party and I noticed something strange while we were gathering the pieces of the staff in Act 2. On the Quest screen, the sixth and final quest box read "Talk to Meshif" before the party had killed Duriel. I suspect the player had beaten Duriel in a previous game, but that player left before answering my inquiry.
79) Dire Wolf Bug (Dire Wolf often trying to eat corpse that they cant eat. (for example corpse of Skeleton or Thorned Hulk)
80) Volcano Bug (it cant be using on very narrow place, for example stairs in arcane sanctuary and it cant be using on monsters that stay near by some objects)
81) the blue hireling (when the merc is chilled, so coloured blue, change map (like Tower Level. doessn�t work on open spaces as there no map-redraw happens). When map is redrawn the merc loos slowness, but isn�t coloured back to its original state. Rarely this also happens with the poison effect (colour green, cause unknown)
82) New glitch with Hellforge Hammer: it can be found more then one time by the same person.
83) bug with Wirst's Leg: Runewords do not work in this weapon at all. I think because it is handled as unque item, despite it is a regular item.
84) new bug: quest item upgrade is possible. Their item type is changed to "hand axe", quality is turned to normal instead of exceptional (�unique normal to exceptional� Horadric recipe is used)
85) Im not sure if the palace glitch has been addressed but. I do find it anoying when another player goes in Palace celler, canyon or arcane way points. (so people without completing the Horadric Staff can talk to Jehrim)
86) Damage/Defense Reducing skills: They�ve been broken since the game has been released� they�re included in the damage calculation instead of using the end-result damage to calculate it.
87) thorns stacked dmgreduce in PvP (first dmg caused to target player is reduced, then the reduced number is reduced again when reflected to the attacker)
88) Fire Golem: My problem with this is that 1) He doesn�t absorb the fire damage period. It�s immune but it doesn�t get healed at all.
89) The two top lightning traps are actually so strong that at Nihlatak they can cause a bug killing Nihlatak so fast and from far away that the quest turns uncomplatable.
90) repairing harpoons and of the sort will not increase the quantity above 20, which is stupid as HELL because the cross-arrows show up at 15 or less, plus 20 isn't very much to work with. Also, it may just be on increased stack size weapons. I have 2 harpoon-type weapons and both were 110+ quantity, won't freaking repair over 20. BIG DEAL TO ME. I've not tried it with any other weapons though, so look out.
91) Sorceress Timerbug which came up with 1.10 and got ofc never fixed ......
92) bug: the assassins Dragon Talon skill first uses the monsters physical resistances, then converts the unresisted physical damage to its explosion damage, then uses the monsters fire resistances to further more lower the damage. This way it uses to kind of resistances instead of one, and is absolutly useless against physical immun monsters for what this skill was invented.
93) Act 5 Quest #5 - destroy the 3 Ancients Barbarians. I use Cloak of Shadow on them, hit them a few hit, then the game crash
94) Grief Smite Bug (the damage of Grief applied fully when Smite skill is used)
95) While using Impale Critical Strike (and maybe Double Strike?) abilities do not work.
96) Ice skating in town (run, then hold shift. The character�s walking animation stops, but the movement does not)
97) charge desync (clientside charge is faster, therefor serverside the character is shown at an incorrect place, resulting practical invisibility)
98) respec-aurastack glitch (when respeced the visual parts of skills will remain, and charactersheet modifiers falsly remain until skill is recast or rejoned to the game. Not sure what happens with period-skills, like Enchant, Werewolf form, Energy shield, Venom etc.)
99) Sometimes the mercenary turns invisible. It functions, but have no visible component. The provided aura is also not visibly on the affected targets, but still works correctly.
100) Sometimes when player's character gets poisoned (eg. in Act2 from Greater Mumies) the poison duration is unexpectedly long and the damage unreasonably high. Eg. when normally (99% of the time) the poison-effect damages 1/5 of the mximum health of the player this bugged damage will cause 3 times the maximum health the character have very fast.
I suspect here both poison lenght reduced and resistance of the player isn't applied.
101) Duping
102) FE + CE bug (when both ability is present on a boss monster, their effect activates twice on Nightmare difficulty only.)
103) Skating Assassin bug
104) With Charged Strike / Lightning Strike use Critical Strike /Doube Strike / Crushing Blow / Open Wounds or anything like that that depend on melee attack
105) gambling on classic from gheed act 1 norm
has throwing weapons in the gambling screen (unidentified), which when purchased are always 'white' superior throwing weapons, not magic/rare/unique
106) Dragon Talon attacks twice for every "hit" (but this bug is predicated on other bugs in various kick skills).
107) The knockback chance (at assassin finishing moves) factors slvl vs. mlvl, but incorrectly uses mlvl as a subtraction (leading to the end result being only slvl).
108) If somebody completes Den of Evil in a game, and somebody who hasn't done the quest joins the game, Akara will give them the option of respec as a chat option, but it does nothing. (May require the other player to be in game already, and then rejoin, but not get the quest done)
109) Due to typos in the column headers of weapons.txt, armor.txt, and possibly other places, Hratli incorrectly has a MagicLevel of 1. Her(?) name is misspelled as Hralti in those headers.
110) Oblivion Knights never attempt to heal their allies (they select a target to heal, however).
111) Fetish Shamans never use their Fetish Aura skill.
112) Fangskin, the superunique in the Viper Temple level 2, never drops any items in hell. This is because he has an incorrect Treasure Class.
113) Frozen Horrors in Act 5 cast Arctic Blast, which is incorrectly flagged to trigger events. This can easily cause a sprite limit overflow when they cast it on a Sorceress with Chilling Armor (or a character with a "Fortitude" that has cast Chilling Armor on them).
114) The "Fires Magic Arrows" property of some unique items doesn't correctly account for any other missile functions, leading to the arrows simply being normal arrows that (to the client) look like magic arrows. (I�m not sure if this bug has been corrected. Witchwild String seemed to work for me.)
115) Dragon Claw: If the first claw attack hits, the second one does normal damage and does not receive the charged-up bonus. (Also true for any multiply-hit finishing-moves of the assassin)
116) Tomb Viper variants in Act 5 in the "Halls" section of the Nithalak quest incorrectly apply their physical damage per frame when attacking with their "poison spear" attack. The attack should use their poison damage alone.
117) Prevent Monster Heal doesn't get applied from your merc's items.
118) Aura-stacking bug - When a character in-game equips 2 pieces of equipment which add the same active aura (example, equipping a dream runeword Hat and a dream runeword Shield both with lvl 15 holy shock auras), the aura's level will be stacked up (giving a level 30 holy shock aura).
119) However you can re-apply the levels repeatedly by trying and failing to trade with someone, triggered by trying to trade an item to a player when his inventory is full, trying to trade a 1-per-inventory item to a player that already has the same such item (trying to trade annhilus to a player holding one already), generally any situation where the trade can't go through for whatever reason. This will re-apply one (or both?) of the item's aura to the existing stacked aura, in our double dream case, giving you a level 45 holy shock. The stacking procedure can be further repeated and the effects further stack with additional failed trades.
120) When the window is stretched, the mouse still moves as if the window was the regular 800x600. This means that when you move the mouse completely off the window on a large resolution, it doesn't appear until so much further down.
121) wp: somtimes the town-wp is blue besides the currently used wp.
122) the change to duriel to allow the essence to drop screwed up his treasure class
he now sometimes doesnt drop a TP at all and sometimes drops nothing but town portals (lol)
123) When i create a game or leave one, the window moves back to its starting postion.... which isnt good at all, and if I recall correctly that didnt happen before 1.13
124) To reproduce: Buy a tome of town portal, set it to a F# key, make a town portal anywhere. Go back to town via a waypoint and put that town portal tome in the stash. Buy a new tome of town portal and go anywhere via a waypoint. This will not cast a town portal via the right mouse button when selected with the F# shortcut key (only the animation happens). A town portal can be cast with a right mouse click of the tome in the inventory though. If the original town portal tome is retrieved from the stash the right mouse button will cast a tp when the correct F# shortcut is selected.
125) char type = barb...while duel wielding, holding 1 weapon the damage adjusts as it should. adding a 2nd weapon for the first time the damage adjusts as it should in the character sheet. replacing either weapon with a 3rd , the damage remains unchanged. from that point on, in order to see the damage adjust i had to unwield all weapons. closing the inventory and character sheet windows, the "incorrect" damage was still listed in the character sheet when character window is reopened.
126) If you create a new game or join to an existing game or quit from a game and previously moved the window anywhere from the starting position (from the middle), it will jump back to it's original position.
127) If you travel to the next Act with quest (not through waypoint) and previously moved the window anywhere from the starting position (from the middle), it will jump back to it's original position.
128) The last charge on any summoning skill from item does not work (the summoned creature immediatelly disappears).
129) Hydra - Decreased base speed of Hydra projectile.
The projectile speed seems to have been decresed instead of being increased as stated in the patch notes. If they were meant to be increased, it is a bug. Only for players, ingame monsters work fine.
130) When an assassin wields a +2 DT claw, her DT skill level does not go up. Doesn't matter which hand she holds it in. +2 skills claw works, but not +2 Dragon Tail claw.
131) I have the option to respec in Hell from Akara, although I have not completed the Den of Evil quest.
I only played by myself in private rooms and didn't complete the quest in Normal or Nightmare either.
132) I had Thunderstorm active when I was killed then left the game and rejoined with a new character (played in hardcore). On my sons screen, the Thunderstorm graphics and sound was still flashing every few seconds.
133) When i have died, and click on my corpse. Tele is no longer mapped to a hot key. This also happends wheneven i am out of tele charges. Happens with any ability used from charges. This is when using items with charges only. Eg. Enigma dont have that problem.
134) When I use stat-up charms like hellfire charm, ani charm, 2 strength small charm, 1 dexterity charm
in my monitor my character is dressed
But in the others monitors my character is undressed
135) Strenght bug: When a piece of equipment is put on a character that only reach the Strenght (DEX etc.) requirement of the item with other items (like charms), and the item provides the same bonus the item remains usable when the equipments that helped to put on the character the euipment in question are removed. (Eg. the character has 10 STR, weapon has STR requirement of 20, and has an affix what provieds 10 STR. Player aquires a +10 STR charm, puts on the weapon, drops the +10 STR charm, and the weapon remains fully active.)
136) I used my normal respec and nightmare respec at akara. i then entered hell. after i got to act 5 i visited act 1 and when i talked to Akara the reset skill/stats option was available even though i didn't complete the den quest. After I clicked it and also clicked Ok nothing happened. I could do this as many times as I wanted. After clearing the den i tried again and then it worked and the option was no longer available.
137) waypoints aren�t active when you make a new game and visit an already activated wp on foot (not through the wp itself)
138) Oblivion Knights (located ANYWHERE) don't cast the curse Lower Resist anymore.
139) when moving and hit by decrep the slowing effect (not sure about its other effects) do not work
140) On the Barb there is a spelling error on one of the skill icons. It says "Pole Arm Mastery" instead of "Polearm Mastery" (the space). All the weapons say "Polearm Class".
141) "Drop barabarian" bug/exploit (bug doesnt appear in Single Player games).
Barbarian, wich have at least one point in each skill at Masteries tree, under Shout, Battle Orders, Battle Command,
Enchant, Venom buffs and with few auras (Fanaticism, Holy Shock, Holy Fire) causes droping from game other characters.
142) Wrong Paladin's Smite damage shown at character screen when items with "+ Damage" attribute equipped.
143) Sorceress skill Telekinesis and Waypoints. When Telekinesis casted from far distance on waypoint it
opens waypoint screen but waypoints at that case does not trigger.
144) "Invisible missiles". Missiles like Bone Spirit or Blessed Hammer can become invisible for players. In case of skill Blessed Hammer, missiles become invisible when Paladin moves around very fast when casting Blessed Hammer (with FRW attribute on items, Charge, Vigor).
145) radament & countess reported sometimes missing
146) when creating a game in window mode and tabbing back into diablo there is a weird wind like howling sound in the backround. to fix this i have to go to sounds and move the sound bar which is pretty annoying to do every time (windows xp)
147) Leaper cannot be killed (0 hp monster)
148) whirlwind death disconnection
description:
in pvp, when whirlwinding, sometimes when i die while in the whirlwind animation, it freezes at the "hit escape to revive in town message" and sits there for an annoyingly length of time, then tells me my connection has been interrupted.
149) not sure if this has been noted yet but i was going over the barb skill tree and saw that the mana cost of Double Swing was -1 (should show 0 as using the skill doesn�t generate mana)
150) you can access Waypoints in town using telekenesis, however if you've just spawned in the game and haven't moved before attempting to use a waypoint via telekenesis then you cannot travel to any other waypoints until you move.
151) Blaze don't give 1% damage per point to firewall.
152) Dual-wield in were-forms is bugged.
153) i gave my act 1 mercenary a magic bow called 'composite bow of transcendence', an ordinary composite bow with extra 18 min dmg option
when i looked at her stat, her dmg was shown as 227-188 which didnt make any sense
i tried with other bows with min dmg option and they seemed to be fine until i found a 'long bow of transcendence', an ordinary long bow with extra 19 min dmg option
funnily these two bows are shown to have the same dmg (22-23) even though their original dmg are different
(long bow: 3-10 and composite bow: 4-8)
when i gave her this bow, the min dmg also showed up higher than the max dmg
also the max dmg of long bow was a little bit higher than that of composite bow, 227-194 (which is true but they both are shown to have the same dmg, 22-23)
i have tried these bows myself and my dmg is shown as 37-38 for both bows
i personally think that 22-23 dmg is because their normal max dmg is lower than 18 or 19 making the min dmg as 'normal min dmg + extra dmg' and the max dmg as 'min dmg + 1'
but i dunno why the min dmg is shown higher than max dmg on the mercenary
(Simply put: the game-mechanic should have been adjusted with a line what�d tell if min. dmg is > max. dmg, then min dmg = max. dmg�1 or if min. dmg is > max. dmg, then max. dmg = min. dmg+1. This later whould be preferred to avoid balance problems with certain skills.)
154) Hsarus' Iron Heel (Set Chain Boots) with an Assassin and it doesn't display the kick damage that goes with it of 6-12. It goes is applied and everything though.
155) When in WorldStoneKeep�;s levels and fighting without walking around (happens when many monsters are present and using a somewhat low damage weapon) the AI thinks the player don�t do anything, so initiates the elemental attack �from Baal�. The effect actually doesn�t come to play, but the laughing effect do happen from this effect. (Try it on higher difficulty where the AI is more active.)
156) When defeating Baal Tyrael appears fixedly at the location where Baal is defeated. Compared to Tyrael the red portal appears at a fixed location. The result of this is that sometimes the portal�s location is inaccessible.
Submitted by Erichvon, after gathering the list from the Battle.net - Diablo II - Test Realm Forum
D2 Test Realm|||Holy ****. I haven't read that, but assuming it's accurate...thanks for posting, but to be honest, I doubt that blizz cares...
Edit: I read the first few....these are not all problems with 1.13. Many are issues (features?) of 1.12. It seems a bit dishonest to pretend that they are problems introduced by 1.13.
Maybe it should be labeled "comprehensive" or "continuing"?|||Some are from 1.13 as you said, but I think if I'm right, that the "suggestions for future patches" fits into this thread. Correct me if I'm wrong though.
(O) Changed title of thread.
(O) Added a brief description at the top.|||Quote:
Some are from 1.13 as you said, but I think if I'm right, that the "suggestions for future patches" fits into this thread. Correct me if I'm wrong though.
Yeah.
Quote:
(O) Changed title of thread.
Quote:
(O) Added a brief description at the top.
Much better, thanks.|||Well you're mighty welcome, one could hope that blizzard would fix all bugs. Another person thinks this is impossible and the guy down the street is indifferent. No one is going to know if they'll fix it, except Blizzard.|||Some of those arent bugs but "features"
e.g. no rare throwing weapons in classic
+damage to smite (from grief)
standards of heroes are supposed to do nothing (just like that gem thingie in the lobby)|||i hope they aint going to enable that unique ring from wiki pages which has been disabled. if they going to enable that ring....|||Read all of those and only have a comment on this one,
"145) radament & countess reported sometimes missing"
I think here is that Radament and the Countess ocassionaly spawn outside of their area. Like the countess (since lvl5 is always the same) spawns in the top right passage (leading to the middle room with chest) by the doorway instead of in the room with the chest.|||Regardless, 100+ bugs are ridiculous, especially with the simplicity of d2's programming.|||wow, great work. I haven't noticed a lot of these bugs but some of them seem like they really need to be fixed. Hopefully blizzard reads this...
-brick
Cd-Key disabled
Well after doing a search I found that it is because I am using a no-cd patch. I installed the game on an older laptop and the cd-rom drive is very noisy and unreliable, so I did what I usually do, installed a no-cd patch. I did not realize that this was punishable by banning. I did not cheat and did not mean to break Blizzards rules. Will they reinstate my key after a little while? Can I reinstall the game and just use the cds?
I am not sure why they do not send a warning before disabling my account. They have my email address through battle.net. I have never once cheated while playing a Blizzard game, I am simply trying to get the game to work.|||Let me get this straight: you used a third-party no-CD patch to get your game to work?
The official 1.12 patch doesn't require CD, so you really screwed yourself for nothing if that's what you did.
And yes, Blizzard is not in the habit of warning anyone when third-party mods are involved. Your CD-key may be banned for good, and it definitely is banned for as long as you keep using that mod.|||I deleted the mod. I now know that I do not need the cd to play, but I didn't know at the time. Turns out I had to transfer the music file off the play disk before I could ditch the cds. I would hope they do not ban my cd-key for good. That would be pretty lame since I wasn't cheating in anyway. Anyhow, I emailed them to find out some more information. I guess now would be a good time to make another run through diablo. Maybe starcraft seeing as how the new game is going to be out soon.....|||Ah crud. I believe I heard somewhere that Diablo 1 is not compatible with windows 7?
I am not sure why they do not send a warning before disabling my account. They have my email address through battle.net. I have never once cheated while playing a Blizzard game, I am simply trying to get the game to work.|||Let me get this straight: you used a third-party no-CD patch to get your game to work?
The official 1.12 patch doesn't require CD, so you really screwed yourself for nothing if that's what you did.
And yes, Blizzard is not in the habit of warning anyone when third-party mods are involved. Your CD-key may be banned for good, and it definitely is banned for as long as you keep using that mod.|||I deleted the mod. I now know that I do not need the cd to play, but I didn't know at the time. Turns out I had to transfer the music file off the play disk before I could ditch the cds. I would hope they do not ban my cd-key for good. That would be pretty lame since I wasn't cheating in anyway. Anyhow, I emailed them to find out some more information. I guess now would be a good time to make another run through diablo. Maybe starcraft seeing as how the new game is going to be out soon.....|||Ah crud. I believe I heard somewhere that Diablo 1 is not compatible with windows 7?
XP sp3 crashing DII
I have been playing DII single player and I am getting a serious crash after killing Andariel at the end of Act 1. This only happens on Windows XP machine with Service Pack 3 installed. Has never happened on SP2 or Vista. Oh yeah DII v1.12
Worst part is it does not save the fact I defeated her so no getting to Act 2.
Any work arounds? (My new netbook came with SP3 so no way to uninstall it.)
I updated a sp2 machine to sp3 and this happens on it too now.
Screen caps
First error
Next error
|||Try recopying the music file from the game cd to your d2 directory? Or run in compatibility mode with SP2.|||Thanks nicro. That did the trick.|||Update. I just had this happen again.
This time on a brand new build with Windows 7 (64bit)
The music file copy worked again.
Worst part is it does not save the fact I defeated her so no getting to Act 2.
Any work arounds? (My new netbook came with SP3 so no way to uninstall it.)
I updated a sp2 machine to sp3 and this happens on it too now.
Screen caps
First error
Next error
|||Try recopying the music file from the game cd to your d2 directory? Or run in compatibility mode with SP2.|||Thanks nicro. That did the trick.|||Update. I just had this happen again.This time on a brand new build with Windows 7 (64bit)
The music file copy worked again.
missing character o_0
I am trying 1.13 beta, and then all of a sudden I lost my current non beta character that was showing up on MP login before...I realize beta carries no guarantees etal,,but just asking has anyone seen this happen ( character shows up on local computer DIR under USwest and dates match and its not single player ) and have a fix if so ?
thx
leebo|||The beta realm is a different realm from uswest.|||Quote:
The beta realm is a different realm from uswest.
I dont know what that has to do with anything at all.
Im asking what 'happened' to the character I was playing which was a sorcerer, which has been replaced somehow by my older assassin character I was playing a while back. I know it doesn't make sense but thats what has happened.
Even if I had made a error and somehow mixed up my characters, how would that affect my online game ?
Is this related to this beta ?
thx anyone
leebo|||so you're saying that when you login to your normal USwest realm you see your older normal USwest realm assassin character instead of your normal USwest realm sorcerrer ?|||make sure your using the correct realm and acctname
chars are marked for deletion after 90 days of inactivity
(name is open for new chars, if used it will be deleted)
accts are deleted after 90 days of inactivity|||Quote:
So you're saying that when you login to your normal USwest realm you see your older normal USwest realm assassin character instead of your normal USwest realm sorceress?
If indeed this is what happened, I can think of only one halfway plausible reason. The server on which your account and characters were stored may have suffered a catastrophic failure that resulted in the data being lost, and the server was restored from old backup files. Those backups contained your old character, but not your newer one.
I can't see how this could have anything to do with playing Beta, or with anything else you could have done.|||Quote:
make sure your using the correct realm and acctname
chars are marked for deletion after 90 days of inactivity
(name is open for new chars, if used it will be deleted)
accts are deleted after 90 days of inactivity
Thx everyone for chiming in, just letting you know {embarrasing though it is}, that I fixed it, by ( was talking with a friend whom I play online with prior to coming here today actually ) logging into MP with leebojamminman, which brought up my characater right away LOL.
I dont know why I had to create a new account, unless maybe somehow server was down at the time I tried as my acct names thus I had to create new , which may be why I thought this acct. was it and that I had lost my previous assassin character..OH well its solved anyway LOL
Thx for chiming in its appreciated.
Looking fwd to D3 as I'm sure most everyone is, while friend and I play through beta ( going well so far )
cheers
leebo
thx
leebo|||The beta realm is a different realm from uswest.|||Quote:
The beta realm is a different realm from uswest.
I dont know what that has to do with anything at all.
Im asking what 'happened' to the character I was playing which was a sorcerer, which has been replaced somehow by my older assassin character I was playing a while back. I know it doesn't make sense but thats what has happened.
Even if I had made a error and somehow mixed up my characters, how would that affect my online game ?
Is this related to this beta ?
thx anyone
leebo|||so you're saying that when you login to your normal USwest realm you see your older normal USwest realm assassin character instead of your normal USwest realm sorcerrer ?|||make sure your using the correct realm and acctname
chars are marked for deletion after 90 days of inactivity
(name is open for new chars, if used it will be deleted)
accts are deleted after 90 days of inactivity|||Quote:
So you're saying that when you login to your normal USwest realm you see your older normal USwest realm assassin character instead of your normal USwest realm sorceress?
If indeed this is what happened, I can think of only one halfway plausible reason. The server on which your account and characters were stored may have suffered a catastrophic failure that resulted in the data being lost, and the server was restored from old backup files. Those backups contained your old character, but not your newer one.
I can't see how this could have anything to do with playing Beta, or with anything else you could have done.|||Quote:
make sure your using the correct realm and acctname
chars are marked for deletion after 90 days of inactivity
(name is open for new chars, if used it will be deleted)
accts are deleted after 90 days of inactivity
Thx everyone for chiming in, just letting you know {embarrasing though it is}, that I fixed it, by ( was talking with a friend whom I play online with prior to coming here today actually ) logging into MP with leebojamminman, which brought up my characater right away LOL.
I dont know why I had to create a new account, unless maybe somehow server was down at the time I tried as my acct names thus I had to create new , which may be why I thought this acct. was it and that I had lost my previous assassin character..OH well its solved anyway LOL
Thx for chiming in its appreciated.
Looking fwd to D3 as I'm sure most everyone is, while friend and I play through beta ( going well so far )
cheers
leebo
Paladin Aura glitch
if you going from shock a din ( paladin with main holy shock aura ) and ask for restats from akara, i still get HS active with my fanatism aura up. ( currently main aura ( i planned zealer, but hs was easier to get myself into nm ) )|||*Plans on exploiting*|||You cant exploit as its visual only.|||Quote:
You cant exploit as its visual only.
naah, all you have to do, get your holy shock up, then kiss akara and do restats, aura still there, and you still got it active untill you leave the game.|||Yes but its visual only it wont do any damage,I know ive tried it.
Just tested it again its not just visual on your char but also on the stat sheet but both are false and you wont get any damage from it.Try punching some thing in act 1 normal with your fists and you will see that your not doing anywhere near that damage.|||Quote:
Yes but its visual only it wont do any damage,I know ive tried it.
Just tested it again its not just visual on your char but also on the stat sheet but both are false and you wont get any damage from it.Try punching some thing in act 1 normal with your fists and you will see that your not doing anywhere near that damage.
it works for me.
You cant exploit as its visual only.
naah, all you have to do, get your holy shock up, then kiss akara and do restats, aura still there, and you still got it active untill you leave the game.|||Yes but its visual only it wont do any damage,I know ive tried it.
Just tested it again its not just visual on your char but also on the stat sheet but both are false and you wont get any damage from it.Try punching some thing in act 1 normal with your fists and you will see that your not doing anywhere near that damage.|||Quote:
Yes but its visual only it wont do any damage,I know ive tried it.
Just tested it again its not just visual on your char but also on the stat sheet but both are false and you wont get any damage from it.Try punching some thing in act 1 normal with your fists and you will see that your not doing anywhere near that damage.
it works for me.
GUbers gone?
From the list of updates.
- Uber Mephisto and Uber Baal's summoned minions no longer give experience.
Does this mean gubers as we know it are no longer in the game starting in 1.13?|||I read it to mean that all the skeletons in UT will now give no XP. Namely, people will not be able to Uber lvl/spin/bonewall for mass xp any more. But if that is "Gubers as you know it" then yes.|||I always found it bit lame, even baal-bot-leeching takes time and it wont shoot you from 1 to 92 in 1 hour.
I never used it so i'm pretty neutral about it disappearing.|||I never used it either, just pointing it out because it seems like so many use to level.
Also I noticed they fixed the magic immunities thing for pallys?|||Yeah, they did.|||Wonder what people will use for baal bots then considering he throws out magic immunes...|||in a perfect world, nothing. bots ruin things.|||Yeah, but they are inevitable. Though bot pking is fun as long as you use a good setup, the bot won't get you.|||stop talking about how would bots kill wave 2 if they are bots. programmers who made it are not stupid, they ll come up with something, they are more then capable of it, after all they managed to make them in 1st place.
i used to use UT leveling, it is time saving, because i am lazy to level up from lvl 1 to lvl 85 i get classic rush, get UT, get my items from mule and char which has RIPed is replaced.
or simply trying new build like dream sorc which requires high runewords to wear, and being weak for like 1 week and just leeching didnt look appealing at all.
it just made me chuckle: they neutralized UT, yet they didnt put more magic immunes for hammer din. well done blizzard / sarcasm.|||Personally, I'd prefer if the immunities were all done away with, instead of changing the magic hammer skill. Instead of nerfing paladins, that would make plenty of character types more viable. Why do they have these immunities in the first place? For the most part, there is no pattern or point to them, other than ghosts being immune to physical.
- Uber Mephisto and Uber Baal's summoned minions no longer give experience.
Does this mean gubers as we know it are no longer in the game starting in 1.13?|||I read it to mean that all the skeletons in UT will now give no XP. Namely, people will not be able to Uber lvl/spin/bonewall for mass xp any more. But if that is "Gubers as you know it" then yes.|||I always found it bit lame, even baal-bot-leeching takes time and it wont shoot you from 1 to 92 in 1 hour.
I never used it so i'm pretty neutral about it disappearing.|||I never used it either, just pointing it out because it seems like so many use to level.
Also I noticed they fixed the magic immunities thing for pallys?|||Yeah, they did.|||Wonder what people will use for baal bots then considering he throws out magic immunes...|||in a perfect world, nothing. bots ruin things.|||Yeah, but they are inevitable. Though bot pking is fun as long as you use a good setup, the bot won't get you.|||stop talking about how would bots kill wave 2 if they are bots. programmers who made it are not stupid, they ll come up with something, they are more then capable of it, after all they managed to make them in 1st place.
i used to use UT leveling, it is time saving, because i am lazy to level up from lvl 1 to lvl 85 i get classic rush, get UT, get my items from mule and char which has RIPed is replaced.
or simply trying new build like dream sorc which requires high runewords to wear, and being weak for like 1 week and just leeching didnt look appealing at all.
it just made me chuckle: they neutralized UT, yet they didnt put more magic immunes for hammer din. well done blizzard / sarcasm.|||Personally, I'd prefer if the immunities were all done away with, instead of changing the magic hammer skill. Instead of nerfing paladins, that would make plenty of character types more viable. Why do they have these immunities in the first place? For the most part, there is no pattern or point to them, other than ghosts being immune to physical.
Diablo 2 LOD Won't Launch
I came to this forum in hopes that maybe you guys could help me out in getting this game working again. I read the common technical difficulties thread, and either I've arleady done what they said, or they don't apply to me. Anyway I used to be able to play this game back in the day, but now it seems it won't work. I had a similiar problem with starcraft, but I set my resolution really low, and it fixed the problem, tryed that with d2..and no fix.
I installed both diablo 2, and LOD without a problem, I haven't tryed the standard diablo 2, but I've been trying to start LOD, and its not working. I own 2 cds of LOD, and neither work, so I highly doubt its the cd (plus it let me install the game without a problem). Like I said, I haven't tryed the standard diablo 2, but I am fairly sure it will just give me the same problem.
Anyway, here is the problem. I put the cd in, the game pops up (or I use the game icon) to try and launch the game, and it does nothing. The little hour glass pops up for a split sec, and then nada... My computer then begins to go extremely slow as if it was trying to launch a game, but regardless of how long you wait, nothing happens. I end up having to restart my computer to rid it of the "slowness" created by trying to launch D2.
My operating system is windows xp, and my video card is Nvidia (not sure which nvidia, not really a computer knowledgable guy). Anyway, have any of you heard of this kinda problem? I can't get into the game at all, it will not launch, there is no error message, no pop up thats something is wrong, no black screen... nothing! It just shows the little hour glass mouse icon for a split sec, like its trying to load the game. Then computer goes really slow, and the game never launches.
Can anyone help me get this game running again? Thanks for any help!!|||Have you tried to run the D2 Vid Test thing in the installation directory, and changing it 2D? Also, check to see if game.exe is running in the processes. If it is, you should be able to kill that without having to restart the entire computer.|||Yes it ran the video test without a problem, and when it was done I selected my nvidia card.
And no, I didn't switch it to 2d, that has to be done manually? And that may be the problem? If so, how do I switch it to 2d. Thanks!|||run D2VidTst.exe -> run tests -> select DirectDraw (2d) -> ok
if that doesnt work, try patching to the 1.12a
http://ftp.blizzard.com/pub/diablo2e...Patch_112a.exe
and if that doesnt work
create a blizzard store acct
https://us.battle.net/account/creation/tos.xml
and register your d2/lod game keys
download and install using the new blizzard keys|||Hmm, thanks for all the info guys! I tryed re-running the vid test, and setting it at the 2d option (originally I chose the 3d option because I didn't know better). Well I keep choosing the 2d option, and hitting okay, and finish, and it keeps showing that I'm still using the 3d Option. For example, I'll run the test, choose 2d, hit ok/finished, then I run test again to see what its on, and it keeps showing that its on 3d, regardless of how many times I choose 2d, it will still show that I have it on 3d after I run the next test.
What do I need to do to KEEP it on 2d? Should I reinstall the game, and choose the 2d option during the first time it asks you to run the test? I don't understand why it won't go off of the 3d option.|||if you pick 2d and ok, it is set
running D2VidTst.exe defaults to autoselect glide over 3d over 2d
to find out what mode it is using
ingame chat /fps
at the top it will say video mode:(direct3d/directdraw/glide)
if you want it to look at its best, try the glide wrapper
http://www.svenswrapper.de/english/downloads.html
then run D2VidTst.exe, test again and seelct glide|||Well I selected 2d and tryed to run the game...and no success. Still gives me the same problem...it simply doesn't start up.
I will now try patching to the 1.12a, and if still no success, I'll try creating a blizz store accnt.
Any more ideas on a solution? Thanks!
I will let you know if patching or creating a store accnt fixes the problem for me.|||Try running it in windowed mode by inputting -w behind the target folder line in the preferences section of D2Lod shortcut.|||Thanks for all the help guys!! I finally got it working, patching it to the 1.12a did the trick. Thanks again, I woulda been lost without ya.
I installed both diablo 2, and LOD without a problem, I haven't tryed the standard diablo 2, but I've been trying to start LOD, and its not working. I own 2 cds of LOD, and neither work, so I highly doubt its the cd (plus it let me install the game without a problem). Like I said, I haven't tryed the standard diablo 2, but I am fairly sure it will just give me the same problem.
Anyway, here is the problem. I put the cd in, the game pops up (or I use the game icon) to try and launch the game, and it does nothing. The little hour glass pops up for a split sec, and then nada... My computer then begins to go extremely slow as if it was trying to launch a game, but regardless of how long you wait, nothing happens. I end up having to restart my computer to rid it of the "slowness" created by trying to launch D2.
My operating system is windows xp, and my video card is Nvidia (not sure which nvidia, not really a computer knowledgable guy). Anyway, have any of you heard of this kinda problem? I can't get into the game at all, it will not launch, there is no error message, no pop up thats something is wrong, no black screen... nothing! It just shows the little hour glass mouse icon for a split sec, like its trying to load the game. Then computer goes really slow, and the game never launches.
Can anyone help me get this game running again? Thanks for any help!!|||Have you tried to run the D2 Vid Test thing in the installation directory, and changing it 2D? Also, check to see if game.exe is running in the processes. If it is, you should be able to kill that without having to restart the entire computer.|||Yes it ran the video test without a problem, and when it was done I selected my nvidia card.
And no, I didn't switch it to 2d, that has to be done manually? And that may be the problem? If so, how do I switch it to 2d. Thanks!|||run D2VidTst.exe -> run tests -> select DirectDraw (2d) -> ok
if that doesnt work, try patching to the 1.12a
http://ftp.blizzard.com/pub/diablo2e...Patch_112a.exe
and if that doesnt work
create a blizzard store acct
https://us.battle.net/account/creation/tos.xml
and register your d2/lod game keys
download and install using the new blizzard keys|||Hmm, thanks for all the info guys! I tryed re-running the vid test, and setting it at the 2d option (originally I chose the 3d option because I didn't know better). Well I keep choosing the 2d option, and hitting okay, and finish, and it keeps showing that I'm still using the 3d Option. For example, I'll run the test, choose 2d, hit ok/finished, then I run test again to see what its on, and it keeps showing that its on 3d, regardless of how many times I choose 2d, it will still show that I have it on 3d after I run the next test.
What do I need to do to KEEP it on 2d? Should I reinstall the game, and choose the 2d option during the first time it asks you to run the test? I don't understand why it won't go off of the 3d option.|||if you pick 2d and ok, it is set
running D2VidTst.exe defaults to autoselect glide over 3d over 2d
to find out what mode it is using
ingame chat /fps
at the top it will say video mode:(direct3d/directdraw/glide)
if you want it to look at its best, try the glide wrapper
http://www.svenswrapper.de/english/downloads.html
then run D2VidTst.exe, test again and seelct glide|||Well I selected 2d and tryed to run the game...and no success. Still gives me the same problem...it simply doesn't start up.
I will now try patching to the 1.12a, and if still no success, I'll try creating a blizz store accnt.
Any more ideas on a solution? Thanks!
I will let you know if patching or creating a store accnt fixes the problem for me.|||Try running it in windowed mode by inputting -w behind the target folder line in the preferences section of D2Lod shortcut.|||Thanks for all the help guys!! I finally got it working, patching it to the 1.12a did the trick. Thanks again, I woulda been lost without ya
.
Your connection has been temporarily restricted from this realm....:S?
"Your connection has been temporarily restricted from this realm. Please try to log in at another time".... What is this about? Really :S I would like to have a fast answere and I wanna know now.... have waited for 2 hours now and I�m getting pretty mad about this.|||Quote:
"Your connection has been temporarily restricted from this realm. Please try to log in at another time".... What is this about? Really :S I would like to have a fast answere and I wanna know now.... have waited for 2 hours now and I�m getting pretty mad about this.
Since it said "temporary" you don't have a whole lot to worry about. You were probably muling too fast or entering/exiting games really quickly, like during very fast baal runs or mf runs over an extended period of time. The more you try to access your account during the temporary restriction the longer it will last. The best thing you can do at this point is take a break and come back in a few hours. If you hadn't tried to access it a lot directly afterwards, it would probably have only lasted 5-15 minutes tops.
This is an anti-botting method implemented by blizzard. If you were muling get someone to help you and take your time a bit more; try not to join and then immediately exit within a matter of seconds, especially if you need to come and go several times. If you were magic finding, add something else to your list of things to run. For example, if you were running only Pindle, add Meph, or andy, or mephy and andy, etc.|||Quote:
This is an anti-botting method implemented by blizzard. If you were muling get someone to help you and take your time a bit more; try not to join and then immediately exit within a matter of seconds, especially if you need to come and go several times. If you were magic finding, add something else to your list of things to run. For example, if you were running only Pindle, add Meph, or andy, or mephy and andy, etc.
How can it be anti-bot when bots are the only ones *never* caught by this, except for the first logon after the "feature" was released?
Bots can be programmed to perfectly avoid the restrictions by adding one tenth of a second delays rigged after the specific time needed to wait betwee games.
Besides -- Bots will stil collect more items and faster than humans, seeing that bots never need any rest and can work with no water and no food. [/Terminator theme]|||this is plain bull**** i just wanted to play , so i logged in a few more times... i got all ****ing night to play and no chars to do it on sigh /hate blizzard for this ...|||Quote:
How can it be anti-bot when bots are the only ones *never* caught by this, except for the first logon after the "feature" was released?
Actually, when it was first released, it eliminated a good partion of them botted hammerdins.
The whole anti-bot things means it prevents making games rapidly, meaning that for example baalbotting is impossible without tweaking it.
Quote:
Bots can be programmed to perfectly avoid the restrictions by adding one tenth of a second delays rigged after the specific time needed to wait betwee games.
This is true, but at least they tried to do something. In the end, the people designing the bots are not exactly rookieprogrammers themselves. I would actually bet that most of them are pretty experienced in computer science and programming. So in the end it comes down to the single truth in reality: No one is perfect, ever. With that, you cannot expect them to ever be capable of completedly cutting away bots, there will always be a loophole somewhere. If the original programmer cannot find it, someone else will. And in the worst case, this someone is one of them botprogrammers, ready to exploit the loophole.
It's really funny how people either underestimate the programmers of the bots or overestimate the programmers at Blizzard. It could very well be that they are all equal or that the botprogrammers are even superior. Just because you work for a company like Blizzard does not mean you are the best in the world.|||Quote:
It's really funny how people either underestimate the programmers of the bots or overestimate the programmers at Blizzard. It could very well be that they are all equal or that the botprogrammers are even superior. Just because you work for a company like Blizzard does not mean you are the best in the world.
I'd say motivation is a key factor. Hackers have lots of motivation to hack, however, blizzard trying to patch up every hole every time a botter finds a new method to bot....well, that's sort of like a kid mashing ants in the driveway. That don't exactly stop coming and you start to ask, what's the point?|||Quote:
How can it be anti-bot when bots are the only ones *never* caught by this, except for the first logon after the "feature" was released?
It's not anti-botting. It's anti-server strain (which was mainly caused by the botting). If you were around for the 30 minute waits to create a single game, you'd understand.|||Quote:
It's not anti-botting. It's anti-server strain (which was mainly caused by the botting). If you were around for the 30 minute waits to create a single game, you'd understand.
I was around and I understand..
I was playing the game with my girlfriend and now I can't get on (I just tried after waiting about an hour, and I am still receiving the message). I read the official message posted here at Blizzard.com and none of those reasons apply to me. This is rather annoying because I only have a few hours a week to play D2 with my girlfriend each week.
Had to vent, sorry.|||This function is arch-annoying, I've gotten this message lots of times the last month and I've never had a bot on my hard drive/ used one on any account I've ever had. My friend and I were tristrunning when this bullsh*t struck us and now we have to wait an unknown period of time before continuing.
What the hell blizzard, why me?|||I just got this message for the crime of
trying to finish act 2. I had just run andy and the countess and decided to do arcane too for some exp. I hit level 50 and decided to go ahead and try duiel. about half way through the tomb and i get a really bad case of lag.
screen eventually goes black and when it finally comes back I'm getting this stupid message.
I guess some bots will enter a game, kill the countess and Andariel then mess around in the arcane sanc for a while and fianlly head for duriel.
That must be it otherwise why would I get this message lol?
"Your connection has been temporarily restricted from this realm. Please try to log in at another time".... What is this about? Really :S I would like to have a fast answere and I wanna know now.... have waited for 2 hours now and I�m getting pretty mad about this.
Since it said "temporary" you don't have a whole lot to worry about. You were probably muling too fast or entering/exiting games really quickly, like during very fast baal runs or mf runs over an extended period of time. The more you try to access your account during the temporary restriction the longer it will last. The best thing you can do at this point is take a break and come back in a few hours. If you hadn't tried to access it a lot directly afterwards, it would probably have only lasted 5-15 minutes tops.
This is an anti-botting method implemented by blizzard. If you were muling get someone to help you and take your time a bit more; try not to join and then immediately exit within a matter of seconds, especially if you need to come and go several times. If you were magic finding, add something else to your list of things to run. For example, if you were running only Pindle, add Meph, or andy, or mephy and andy, etc.|||Quote:
This is an anti-botting method implemented by blizzard. If you were muling get someone to help you and take your time a bit more; try not to join and then immediately exit within a matter of seconds, especially if you need to come and go several times. If you were magic finding, add something else to your list of things to run. For example, if you were running only Pindle, add Meph, or andy, or mephy and andy, etc.
How can it be anti-bot when bots are the only ones *never* caught by this, except for the first logon after the "feature" was released?
Bots can be programmed to perfectly avoid the restrictions by adding one tenth of a second delays rigged after the specific time needed to wait betwee games.
Besides -- Bots will stil collect more items and faster than humans, seeing that bots never need any rest and can work with no water and no food. [/Terminator theme]|||this is plain bull**** i just wanted to play , so i logged in a few more times... i got all ****ing night to play and no chars to do it on sigh /hate blizzard for this ...|||Quote:
How can it be anti-bot when bots are the only ones *never* caught by this, except for the first logon after the "feature" was released?
Actually, when it was first released, it eliminated a good partion of them botted hammerdins.
The whole anti-bot things means it prevents making games rapidly, meaning that for example baalbotting is impossible without tweaking it.
Quote:
Bots can be programmed to perfectly avoid the restrictions by adding one tenth of a second delays rigged after the specific time needed to wait betwee games.
This is true, but at least they tried to do something. In the end, the people designing the bots are not exactly rookieprogrammers themselves. I would actually bet that most of them are pretty experienced in computer science and programming. So in the end it comes down to the single truth in reality: No one is perfect, ever. With that, you cannot expect them to ever be capable of completedly cutting away bots, there will always be a loophole somewhere. If the original programmer cannot find it, someone else will. And in the worst case, this someone is one of them botprogrammers, ready to exploit the loophole.
It's really funny how people either underestimate the programmers of the bots or overestimate the programmers at Blizzard. It could very well be that they are all equal or that the botprogrammers are even superior. Just because you work for a company like Blizzard does not mean you are the best in the world.|||Quote:
It's really funny how people either underestimate the programmers of the bots or overestimate the programmers at Blizzard. It could very well be that they are all equal or that the botprogrammers are even superior. Just because you work for a company like Blizzard does not mean you are the best in the world.
I'd say motivation is a key factor. Hackers have lots of motivation to hack, however, blizzard trying to patch up every hole every time a botter finds a new method to bot....well, that's sort of like a kid mashing ants in the driveway. That don't exactly stop coming and you start to ask, what's the point?|||Quote:
How can it be anti-bot when bots are the only ones *never* caught by this, except for the first logon after the "feature" was released?
It's not anti-botting. It's anti-server strain (which was mainly caused by the botting). If you were around for the 30 minute waits to create a single game, you'd understand.|||Quote:
It's not anti-botting. It's anti-server strain (which was mainly caused by the botting). If you were around for the 30 minute waits to create a single game, you'd understand.
I was around and I understand..
I was playing the game with my girlfriend and now I can't get on (I just tried after waiting about an hour, and I am still receiving the message). I read the official message posted here at Blizzard.com and none of those reasons apply to me. This is rather annoying because I only have a few hours a week to play D2 with my girlfriend each week.
Had to vent, sorry.|||This function is arch-annoying, I've gotten this message lots of times the last month and I've never had a bot on my hard drive/ used one on any account I've ever had. My friend and I were tristrunning when this bullsh*t struck us and now we have to wait an unknown period of time before continuing.
What the hell blizzard, why me?|||I just got this message for the crime of
trying to finish act 2. I had just run andy and the countess and decided to do arcane too for some exp. I hit level 50 and decided to go ahead and try duiel. about half way through the tomb and i get a really bad case of lag.
screen eventually goes black and when it finally comes back I'm getting this stupid message.
I guess some bots will enter a game, kill the countess and Andariel then mess around in the arcane sanc for a while and fianlly head for duriel.
That must be it otherwise why would I get this message lol?
frozen hell mode
Playing in hell mode on the belta classic real, and
found some duriels shell, which says cannot be frozen.
Why then am I always being frozen?|||I'm having trouble understanding you here. What do you mean by "belta classic real"?
As for possible reasons why you're being frozen despite having Duriel's Shell:
1. You need to wear it to get the bonus.
2. Monsters with Holy Freeze aura ignore the bonus, so you're still frozen when they're around. The bonus only protects from the freeze from normal cold attacks.|||classic beta is on battlenet. The new realm with the
new patch.|||You could at least provide some situations when you were frozen
Were you fighting superunique monsters that have a blue aura?|||Monsters with "blue aura" have a Holy freeze aura, which will penerate any sort of resistances and CBF mods.|||yeah, it have to be holy freeze aura.this aura includes cold demage which not freezing u if u are wearing cbf gear, e.g.duri.but other part of this aura is "holy" freeze, which is not become from cold, but slows u down. so monsters or players with hf aura always slow u ...
found some duriels shell, which says cannot be frozen.
Why then am I always being frozen?|||I'm having trouble understanding you here. What do you mean by "belta classic real"?
As for possible reasons why you're being frozen despite having Duriel's Shell:
1. You need to wear it to get the bonus.
2. Monsters with Holy Freeze aura ignore the bonus, so you're still frozen when they're around. The bonus only protects from the freeze from normal cold attacks.|||classic beta is on battlenet. The new realm with the
new patch.|||You could at least provide some situations when you were frozen
Were you fighting superunique monsters that have a blue aura?|||Monsters with "blue aura" have a Holy freeze aura, which will penerate any sort of resistances and CBF mods.|||yeah, it have to be holy freeze aura.this aura includes cold demage which not freezing u if u are wearing cbf gear, e.g.duri.but other part of this aura is "holy" freeze, which is not become from cold, but slows u down. so monsters or players with hf aura always slow u ...
Mephisto.
Do you guys think that the map layout of Mephy should be changed?
I mean it's kinda stupid you lure him to the "safe spot" and he stands there like a moron. So much for being one of the Prime Evils :)|||It doesn't really matter because even if you couldn't moat him then teleporting through durance level 2 is still multitudes more difficult than dealing with him the normal way. (meaning not difficult at all)|||Don't care. I always take him head on, and I don't really run Meph anyway. Besides, the stygian dolls in Durance are far more dangerous, so if you can get past them, Mephisto should be easy to deal with in a fair fight.|||i thought you were talking about stupid level 2 design
if they could make it "smaller" i d be more then just happy to droll on him.
On topic, i always take him head on.|||The level 2 design was intentional, to prevent over farming of Meph in NM/Hell but ironically there still is the moat trick.|||The moat trick is unnecessary, any good runners will have a build that can tank him for the short amount of time it takes to kill him. On top of which moat tricking him takes longer than it does for my light sorc to kill him.|||Quote:
i thought you were talking about stupid level 2 design
if they could make it "smaller" i d be more then just happy to droll on him.
On topic, i always take him head on.
Actually it's quite easy to find Mephi IMHO, because the stairs to durance lvl3 are 90% of the time clockwise, just tele clockwise and u will be there.
Only on some rare occasion are they in the middle of durance lvl2.
Usually i go head on if i have strong Merc.|||not for me, its never in same direction.
I mean it's kinda stupid you lure him to the "safe spot" and he stands there like a moron. So much for being one of the Prime Evils :)|||It doesn't really matter because even if you couldn't moat him then teleporting through durance level 2 is still multitudes more difficult than dealing with him the normal way. (meaning not difficult at all)|||Don't care. I always take him head on, and I don't really run Meph anyway. Besides, the stygian dolls in Durance are far more dangerous, so if you can get past them, Mephisto should be easy to deal with in a fair fight.|||i thought you were talking about stupid level 2 design
if they could make it "smaller" i d be more then just happy to droll on him.
On topic, i always take him head on.|||The level 2 design was intentional, to prevent over farming of Meph in NM/Hell but ironically there still is the moat trick.|||The moat trick is unnecessary, any good runners will have a build that can tank him for the short amount of time it takes to kill him. On top of which moat tricking him takes longer than it does for my light sorc to kill him.|||Quote:
i thought you were talking about stupid level 2 design
if they could make it "smaller" i d be more then just happy to droll on him.
On topic, i always take him head on.
Actually it's quite easy to find Mephi IMHO, because the stairs to durance lvl3 are 90% of the time clockwise, just tele clockwise and u will be there.
Only on some rare occasion are they in the middle of durance lvl2.
Usually i go head on if i have strong Merc.|||not for me, its never in same direction.
Error 25: A critical error has occurred while initializing Direct3D
Anyone getting this message?
Error 25: A critical error has occurred while initializing Direct3D
I could play about 3 months ago and now I reinstalled for the reset and am unable to play. Thanks in advance for any help.|||This is usually video card related. Try to run D2VidTest manually from the installation directory and choosing DirectDraw (2D) and seeing how that goes. Direct3D isn't much of an improvement over 2D for a game as old as D2, in my opinion anyway
Error 25: A critical error has occurred while initializing Direct3D
I could play about 3 months ago and now I reinstalled for the reset and am unable to play. Thanks in advance for any help.|||This is usually video card related. Try to run D2VidTest manually from the installation directory and choosing DirectDraw (2D) and seeing how that goes. Direct3D isn't much of an improvement over 2D for a game as old as D2, in my opinion anyway
respecing
i heard in 1.13 you can acctualy restat your chars. is there any truth to this i cant find any information.|||I haven't played the final version yet, but did play on the test realm for a couple of weeks.
In that version (1.13b) you get a free respec from Akara as a reward for the Den of Evil quest, in addition to the bonus skill point. When you use this, you get back all of the stat and skill points you have spent, and can redistribute them however you like.
Also, in Hell difficulty, the Act Bosses would drop "essences", of which there are four types. Collect one of each and cube them to create a Respec Token that allows you to again reset your skill and stat points.
I like the way it works, for the most part, but I think that having Act Bosses drop the essences was a really bad idea. Think of how much variety was added to MF runs by having the Keys drop from three Super-Uniques. I'm hoping that in the final release of the patch (1.13c) they stopped having essences dropped by act bosses. Guess I'll find out tonight.
EDIT: Just learned from another player online that Act Bosses are still dropping the essences. So sad. They could have done so much more with that idea.|||hmmm im excited.
so any char regaurdless of what patch they were created is subject to this, ladder or non?|||Yup, ladder or not, any char.|||im giddy!!!!!
In that version (1.13b) you get a free respec from Akara as a reward for the Den of Evil quest, in addition to the bonus skill point. When you use this, you get back all of the stat and skill points you have spent, and can redistribute them however you like.
Also, in Hell difficulty, the Act Bosses would drop "essences", of which there are four types. Collect one of each and cube them to create a Respec Token that allows you to again reset your skill and stat points.
I like the way it works, for the most part, but I think that having Act Bosses drop the essences was a really bad idea. Think of how much variety was added to MF runs by having the Keys drop from three Super-Uniques. I'm hoping that in the final release of the patch (1.13c) they stopped having essences dropped by act bosses. Guess I'll find out tonight.
EDIT: Just learned from another player online that Act Bosses are still dropping the essences. So sad. They could have done so much more with that idea.|||hmmm im excited.
so any char regaurdless of what patch they were created is subject to this, ladder or non?|||Yup, ladder or not, any char.|||im giddy!!!!!
how to make d2 widescreen?
I read in the patch notes that wide screen users could now make the game fit their screen without stretching it all too hell. I dl'd the beta and can't find where i can change the video settings. In game it just gives me the same 800x600 option.|||adjust your monitor settings
or use the glide wrapper
enable desktopresolution and keep aspect ratio
http://www.svenswrapper.de/english/downloads.html|||Thats just refering to window mode your not going to get more play space in the game with widescreen but the aspect ratio gets corrected.|||Quote:
adjust your monitor settings
or use the glide wrapper
enable desktopresolution and keep aspect ratio
http://www.svenswrapper.de/english/downloads.html
what does that glide wrapper do? and is it considered a 3rd party program by blizz?|||yes/no
its a 3rd party app, but not detectable by bnet
iv been using it for years without any accts/keys being banned
it converts glide from d2 to opengl
d2 was written for glide (back in the 3dfx card days), d3d is slow but looks pretty, 2d is fast without any pretty effects
basically the wrapper gives the best preformance with all the pretty effects
glide.dll -> wrapper -> opengl
instead of d3d.dll -> d3d
there are 3rd party apps that can increase the visable area in d2, instead of making it fit your monitor better
but those cant be discussed here|||so glide will make its not as stretched on my screen?|||yup
heres what i play at 1680x1050
http://i186.photobucket.com/albums/x...s1680x1050.jpg
never drops below 60fps|||What OS are you using? I tooled around a bit and couldn't get it to work. Likely user error, though. I'm running windows 7 on a 23" monitor in 1600x900 resolution (1920x1080 is just too small) and from what I've sound, I can either run stretched in full screen (ew) or in a window, where I'm constantly clicking outside the game =[|||If it comes up in a window when you first run it then just press Alt Enter and it will go full screen.|||glide wrapper has a setting to capture mouse, which stops you from moving then clicking outside the window (alt+tab still works)
1.13 beta can be stretched to full screen with -w then doubleclick on the title bar
but double/triple pixel doesnt look nearly as pretty as bilinear filtering
or use the glide wrapper
enable desktopresolution and keep aspect ratio
http://www.svenswrapper.de/english/downloads.html|||Thats just refering to window mode your not going to get more play space in the game with widescreen but the aspect ratio gets corrected.|||Quote:
adjust your monitor settings
or use the glide wrapper
enable desktopresolution and keep aspect ratio
http://www.svenswrapper.de/english/downloads.html
what does that glide wrapper do? and is it considered a 3rd party program by blizz?|||yes/no
its a 3rd party app, but not detectable by bnet
iv been using it for years without any accts/keys being banned
it converts glide from d2 to opengl
d2 was written for glide (back in the 3dfx card days), d3d is slow but looks pretty, 2d is fast without any pretty effects
basically the wrapper gives the best preformance with all the pretty effects
glide.dll -> wrapper -> opengl
instead of d3d.dll -> d3d
there are 3rd party apps that can increase the visable area in d2, instead of making it fit your monitor better
but those cant be discussed here|||so glide will make its not as stretched on my screen?|||yup
heres what i play at 1680x1050
http://i186.photobucket.com/albums/x...s1680x1050.jpg
never drops below 60fps|||What OS are you using? I tooled around a bit and couldn't get it to work. Likely user error, though. I'm running windows 7 on a 23" monitor in 1600x900 resolution (1920x1080 is just too small) and from what I've sound, I can either run stretched in full screen (ew) or in a window, where I'm constantly clicking outside the game =[|||If it comes up in a window when you first run it then just press Alt Enter and it will go full screen.|||glide wrapper has a setting to capture mouse, which stops you from moving then clicking outside the window (alt+tab still works)
1.13 beta can be stretched to full screen with -w then doubleclick on the title bar
but double/triple pixel doesnt look nearly as pretty as bilinear filtering
Unrecoverable Internal Error 6fe1dc4c
I've been having trouble playing 1.13 in multiple ways. Anytime I use a 1.12 character or older, I get this error:
I can't use my Battle.Net characters from 1.12, my Single-Player characters from 1.12 and my edited characters from 1.12
1.13 Battle.Net characters seem to work fine, as well as new 1.13 Single-Player characters, however, if I generate a new 1.13 character and edit anything using Hero Editor, I get the same error as my 1.12 characters.
Can anyone help out? I'd be greatly appreciated.|||Quote:
and edit anything using Hero Editor
thats your problem|||Fixed it now, and if anyone runs into the same error, I just re-installed and it worked right after.
Quote:
thats your problem
Uh huh.
I can't use my Battle.Net characters from 1.12, my Single-Player characters from 1.12 and my edited characters from 1.12
1.13 Battle.Net characters seem to work fine, as well as new 1.13 Single-Player characters, however, if I generate a new 1.13 character and edit anything using Hero Editor, I get the same error as my 1.12 characters.
Can anyone help out? I'd be greatly appreciated.|||Quote:
and edit anything using Hero Editor
thats your problem|||Fixed it now, and if anyone runs into the same error, I just re-installed and it worked right after.
Quote:
thats your problem
Uh huh.
What does this mean?
Reading the game notes for the new patch, and it
says added the widows system buttons to the game
min, max,close . What does this mean and how does
it work?|||if your d2 shortcut has -w added to the end of the target line
you will have _, [], X at the top of the window, to _ minimize, [] maximize, and X close d2|||They should made a change like that in game. Like they have
on a web site.
says added the widows system buttons to the game
min, max,close . What does this mean and how does
it work?|||if your d2 shortcut has -w added to the end of the target line
you will have _, [], X at the top of the window, to _ minimize, [] maximize, and X close d2|||They should made a change like that in game. Like they have
on a web site.
Amazing, simply amazing!
Alright, i open up my computer, log in to diablo and enter a game.
After i leave it, i get lost connection to b.net and i am told i have a tempban
.
/rage
Also, note that i only joined ONE game and left it after around 2 minutes.
It was first time i logged in on the whole day!
What did i do wrong?
Edit, lol it only lasted 10 minutes. GG blizz|||Thats anti bot protection (but works as anti mule/fast baalrun protection).
It can last from 10minutes up 2 12hours:)|||Quote:
Thats anti bot protection (but works as anti mule/fast baalrun protection).
It can last from 10minutes up 2 12hours:)
The thing was that i logged in and got temp banned immediately after leaving the first game i joined, not after doing fast muling ect, ect.
Also i do know what it is, i just don't understand what it is, i just don't get why i would get it for reasons above.
|||slow down your actions while changing chars
wait 5-10 secs between actions
doing that quickly will give temp bans too|||The way I understood this was that nurman didn't even have time to change characters. Just leave the first game you're in, and instead of appearing in chat like you should, you get booted off Battle.net, with a temp ban as a courtesy detail.
I've had this happen numerous times. I'm betting that Blizzard has a standard action in their code for all exceptional situations. Whenever something goes wrong, whether it is a server bug, a network issue or something the player actually did, the result is that the player gets booted with a ban. And yes, I do feel that the whole approach is stupid and counter-productive.|||Quote:
The way I understood this was that nurman didn't even have time to change characters. Just leave the first game you're in, and instead of appearing in chat like you should, you get booted off Battle.net, with a temp ban as a courtesy detail.
I've had this happen numerous times. I'm betting that Blizzard has a standard action in their code for all exceptional situations. Whenever something goes wrong, whether it is a server bug, a network issue or something the player actually did, the result is that the player gets booted with a ban. And yes, I do feel that the whole approach is stupid and counter-productive.
Yup, this is what i was trying to tell you guys.|||Do anyone remember the unbelivable waiting time there was during the 1.09 to enter games?
Well, this approach, that can seem very bad, solved that problem. We simply have to learn to do things slowly.
- Do not stay in a game for a single minute or two. Stay at least 4-5 minutes
- Wait 5-10 seconds before moving after you enter a game
- Do not change characters immediately after leaving a game
- Do not enter a game immediately after chosing a character
- Simply do things SLOWLY. Always wait 4-5 seconds beteween EACH of your action (Login, choose character, open channell/chat, open game search window, enter game, start playing)
If you do your things quite and slow, you're going to have MUCH less problems... That's the price to have much less lag than times ago|||problem is that under blizz penalization is very very things, but they use just few notices before or during penalization. so many times its very confusing, cause u dont know why or what system sais is totaly nonsense...|||Quote:
Do anyone remember the unbelivable waiting time there was during the 1.09 to enter games?
Well, this approach, that can seem very bad, solved that problem. We simply have to learn to do things slowly.
- Do not stay in a game for a single minute or two. Stay at least 4-5 minutes
- Wait 5-10 seconds before moving after you enter a game
- Do not change characters immediately after leaving a game
- Do not enter a game immediately after chosing a character
- Simply do things SLOWLY. Always wait 4-5 seconds beteween EACH of your action (Login, choose character, open channell/chat, open game search window, enter game, start playing)
If you do your things quite and slow, you're going to have MUCH less problems... That's the price to have much less lag than times ago
Seriously read the thread first. I know your just trying to be helpful but at least be on target of what was said previously in the thread.|||Did you scroll through your skills really fast? That can land you a temp ban.
Quote:
I do feel that the whole approach is stupid and counter-productive.
It doesn't really matter to them what's smart or stupid. Regardless of any issue with the game, they'll NEVER upgrade their servers to allow such features. Their solution to the fire lag bug? Disconnect you if there is too much torch procs/meteors going on all at once. They COULD just upgrade their servers, but they won't. They barely make anything off of this game anymore, and the cost of upgrading their servers would just be a wasted expense, speaking from the perspective of a business.
All in all though, it really is a pointless measure. We all know bots thoroughly dominate this game, and their measures have done nothing to stop them, nor will they ever implement measures to stop them. The only thing they've managed to do is make this game a pain in the *** to enjoy for the legitimate players.
After i leave it, i get lost connection to b.net and i am told i have a tempban
./rage
Also, note that i only joined ONE game and left it after around 2 minutes.
It was first time i logged in on the whole day!
What did i do wrong?
Edit, lol it only lasted 10 minutes. GG blizz|||Thats anti bot protection (but works as anti mule/fast baalrun protection).
It can last from 10minutes up 2 12hours:)|||Quote:
Thats anti bot protection (but works as anti mule/fast baalrun protection).
It can last from 10minutes up 2 12hours:)
The thing was that i logged in and got temp banned immediately after leaving the first game i joined, not after doing fast muling ect, ect.
Also i do know what it is, i just don't understand what it is, i just don't get why i would get it for reasons above.
|||slow down your actions while changing charswait 5-10 secs between actions
doing that quickly will give temp bans too|||The way I understood this was that nurman didn't even have time to change characters. Just leave the first game you're in, and instead of appearing in chat like you should, you get booted off Battle.net, with a temp ban as a courtesy detail.
I've had this happen numerous times. I'm betting that Blizzard has a standard action in their code for all exceptional situations. Whenever something goes wrong, whether it is a server bug, a network issue or something the player actually did, the result is that the player gets booted with a ban. And yes, I do feel that the whole approach is stupid and counter-productive.|||Quote:
The way I understood this was that nurman didn't even have time to change characters. Just leave the first game you're in, and instead of appearing in chat like you should, you get booted off Battle.net, with a temp ban as a courtesy detail.
I've had this happen numerous times. I'm betting that Blizzard has a standard action in their code for all exceptional situations. Whenever something goes wrong, whether it is a server bug, a network issue or something the player actually did, the result is that the player gets booted with a ban. And yes, I do feel that the whole approach is stupid and counter-productive.
Yup, this is what i was trying to tell you guys.
|||Do anyone remember the unbelivable waiting time there was during the 1.09 to enter games?Well, this approach, that can seem very bad, solved that problem. We simply have to learn to do things slowly.
- Do not stay in a game for a single minute or two. Stay at least 4-5 minutes
- Wait 5-10 seconds before moving after you enter a game
- Do not change characters immediately after leaving a game
- Do not enter a game immediately after chosing a character
- Simply do things SLOWLY. Always wait 4-5 seconds beteween EACH of your action (Login, choose character, open channell/chat, open game search window, enter game, start playing)
If you do your things quite and slow, you're going to have MUCH less problems... That's the price to have much less lag than times ago|||problem is that under blizz penalization is very very things, but they use just few notices before or during penalization. so many times its very confusing, cause u dont know why or what system sais is totaly nonsense...|||Quote:
Do anyone remember the unbelivable waiting time there was during the 1.09 to enter games?
Well, this approach, that can seem very bad, solved that problem. We simply have to learn to do things slowly.
- Do not stay in a game for a single minute or two. Stay at least 4-5 minutes
- Wait 5-10 seconds before moving after you enter a game
- Do not change characters immediately after leaving a game
- Do not enter a game immediately after chosing a character
- Simply do things SLOWLY. Always wait 4-5 seconds beteween EACH of your action (Login, choose character, open channell/chat, open game search window, enter game, start playing)
If you do your things quite and slow, you're going to have MUCH less problems... That's the price to have much less lag than times ago
Seriously read the thread first. I know your just trying to be helpful but at least be on target of what was said previously in the thread.|||Did you scroll through your skills really fast? That can land you a temp ban.
Quote:
I do feel that the whole approach is stupid and counter-productive.
It doesn't really matter to them what's smart or stupid. Regardless of any issue with the game, they'll NEVER upgrade their servers to allow such features. Their solution to the fire lag bug? Disconnect you if there is too much torch procs/meteors going on all at once. They COULD just upgrade their servers, but they won't. They barely make anything off of this game anymore, and the cost of upgrading their servers would just be a wasted expense, speaking from the perspective of a business.
All in all though, it really is a pointless measure. We all know bots thoroughly dominate this game, and their measures have done nothing to stop them, nor will they ever implement measures to stop them. The only thing they've managed to do is make this game a pain in the *** to enjoy for the legitimate players.
Back to 1.12 possible?
Hi,
just wondering if its possible to reverse the game back to 1.12 (speaking of SP) after 1.13 patch was applied.
I am intending to respec my zon using 1.13 but play 1.12 then again.
I remember there was a reverse possibility from 1.10 back to 1.09 back then.|||Just change the realm from Classic Beta to any other realm you prefer.
I think you can get somekind of patch from Blizzard's website.|||only in single player obv.|||Quote:
I am intending to respec my zon using 1.13 but play 1.12 then again.
If you plan on MPing or trading on the single player forum, check with the SP moderators about this. I doubt this is allowed in the community.|||Quote:
If you plan on MPing or trading on the single player forum, check with the SP moderators about this. I doubt this is allowed in the community.
I am not! All my chars goes 100% self-find!
Just want to know if SP characters are still playable in 1.12 after they were played in 1.13. That is my question.
Thanks|||Again, you could most likely get a more accurate answer by heading to the SP forums.|||Quote:
Again, you could most likely get a more accurate answer by heading to the SP forums.
OK, I got the point....but this is a 1.13 suggestion, isn't it?
The same question could apply for open characters as well.|||If all you want to respect a character in 1.12, use plugY. It's much safer.
You can remove plugY once the respect is done and play the original game.
1.13 back to 1.12 is certainly possible, a simple way is just reinstall the game, download and apply patches up to 1.12. But when a 1.12 character is played thus converted to 1.13, it may not work anymore on 1.12. So imho it doesn't worth a try.|||Quote:
If all you want to respect a character in 1.12, use plugY. It's much safer.
You can remove plugY once the respect is done and play the original game.
1.13 back to 1.12 is certainly possible, a simple way is just reinstall the game, download and apply patches up to 1.12. But when a 1.12 character is played thus converted to 1.13, it may not work anymore on 1.12. So imho it doesn't worth a try.
You mean respec, not respect.
Also, PlugY is not acceptable in the SPF, not to mention help with it or anything is not supported on these forums.
just wondering if its possible to reverse the game back to 1.12 (speaking of SP) after 1.13 patch was applied.
I am intending to respec my zon using 1.13 but play 1.12 then again.
I remember there was a reverse possibility from 1.10 back to 1.09 back then.|||Just change the realm from Classic Beta to any other realm you prefer.
I think you can get somekind of patch from Blizzard's website.|||only in single player obv.|||Quote:
I am intending to respec my zon using 1.13 but play 1.12 then again.
If you plan on MPing or trading on the single player forum, check with the SP moderators about this. I doubt this is allowed in the community.|||Quote:
If you plan on MPing or trading on the single player forum, check with the SP moderators about this. I doubt this is allowed in the community.
I am not! All my chars goes 100% self-find!
Just want to know if SP characters are still playable in 1.12 after they were played in 1.13. That is my question.
Thanks|||Again, you could most likely get a more accurate answer by heading to the SP forums.|||Quote:
Again, you could most likely get a more accurate answer by heading to the SP forums.
OK, I got the point....but this is a 1.13 suggestion, isn't it?
The same question could apply for open characters as well.|||If all you want to respect a character in 1.12, use plugY. It's much safer.
You can remove plugY once the respect is done and play the original game.
1.13 back to 1.12 is certainly possible, a simple way is just reinstall the game, download and apply patches up to 1.12. But when a 1.12 character is played thus converted to 1.13, it may not work anymore on 1.12. So imho it doesn't worth a try.|||Quote:
If all you want to respect a character in 1.12, use plugY. It's much safer.
You can remove plugY once the respect is done and play the original game.
1.13 back to 1.12 is certainly possible, a simple way is just reinstall the game, download and apply patches up to 1.12. But when a 1.12 character is played thus converted to 1.13, it may not work anymore on 1.12. So imho it doesn't worth a try.
You mean respec, not respect.
Also, PlugY is not acceptable in the SPF, not to mention help with it or anything is not supported on these forums.
Aura stackers are back...
I do not know if this has been mentioned but i have already found a bug/exploit that allows aura stacking holy shock/fire.I wont go into detail, but you just need to"self stack"and you are back in buisness.I hope this bug wont make it in pvp,but i already know at least 2ppl using it(not me)so it wont be long until others find out.Be prepared to meet more stackers...|||Quote:
I do not know if this has been mentioned but i have already found a bug/exploit that allows aura stacking holy shock/fire.I wont go into detail, but you just need to"self stack"and you are back in buisness.I hope this bug wont make it in pvp,but i already know at least 2ppl using it(not me)so it wont be long until others find out.Be prepared to meet more stackers...
Please post the exact details of how this aura stacking is done so that it can be fixed. If blizzard doesn't know how it's reproduced, they can't fix it.|||It would be better if he did not post the exact details on this forum. There are other ways to report bugs.
Also, it is strange that you have one post and that single post is dedicated to "finding a bug so it can be fixed."|||Quote:
Please post the exact details of how this aura stacking is done so that it can be fixed. If blizzard doesn't know how it's reproduced, they can't fix it.
Which should probably be done on the Blizzard forum or in an email to them.|||Quote:
Also, it is strange that you have one post and that single post is dedicated to "finding a bug so it can be fixed."
And his account was created in February, meaning he must have been prowling these forums for a long time to make that first post.|||fair enough, you should probably just email it to hacks@blizzard.com then.
I do not know if this has been mentioned but i have already found a bug/exploit that allows aura stacking holy shock/fire.I wont go into detail, but you just need to"self stack"and you are back in buisness.I hope this bug wont make it in pvp,but i already know at least 2ppl using it(not me)so it wont be long until others find out.Be prepared to meet more stackers...
Please post the exact details of how this aura stacking is done so that it can be fixed. If blizzard doesn't know how it's reproduced, they can't fix it.|||It would be better if he did not post the exact details on this forum. There are other ways to report bugs.
Also, it is strange that you have one post and that single post is dedicated to "finding a bug so it can be fixed."|||Quote:
Please post the exact details of how this aura stacking is done so that it can be fixed. If blizzard doesn't know how it's reproduced, they can't fix it.
Which should probably be done on the Blizzard forum or in an email to them.|||Quote:
Also, it is strange that you have one post and that single post is dedicated to "finding a bug so it can be fixed."
And his account was created in February, meaning he must have been prowling these forums for a long time to make that first post.|||fair enough, you should probably just email it to hacks@blizzard.com then.
Stacked Aura Bug Fix?
"Major Bugs
- Fixed two issues where players could stack auras in an unintended way."
Has anyone figured out exactly what has been changed?
- Fixed two issues where players could stack auras in an unintended way."
Has anyone figured out exactly what has been changed?
Error Installing Patch?
"Blizzard BNUpdate v2.72 compiled on Oct 16 2003
Log created at 3:50 pm on 03/23/2010
ERROR: unable to open archive 'D2XP_IX86_112a_113c.mpq'
RESULT: Patch failed"
I think I may know the answer to why this occurred, but if I can solve it, that'd be marvelous. If anyone can help, please post ASAP.
thanks to like the two viewers. but i fixed my problem. it was a misplaced file and i am now playing under the new patch.
(:
hit up nuttersums.|||how did you fix it? im having the same problem|||If you are playing SP and using some mods like RWM you will see this error using your regular shortcut. Go to your install directory and run the game from the "Diablo II.exe" and you should do fine.
Nac|||EDIT: Nevermind, just saw the above post|||i cant fix this someone please post how u fixed it!!!
i dont use mods ive reinstalled it from the site 4 times in different locations each time i still get this error please tell me how to fix it|||i fixed it finally... somehow the file is moved to the c drive and u have to move it to the diablo folder ty not telling any1 how u fixed it opening poster..
Log created at 3:50 pm on 03/23/2010
ERROR: unable to open archive 'D2XP_IX86_112a_113c.mpq'
RESULT: Patch failed"
I think I may know the answer to why this occurred, but if I can solve it, that'd be marvelous. If anyone can help, please post ASAP.
thanks to like the two viewers. but i fixed my problem. it was a misplaced file and i am now playing under the new patch.
(:
hit up nuttersums.|||how did you fix it? im having the same problem|||If you are playing SP and using some mods like RWM you will see this error using your regular shortcut. Go to your install directory and run the game from the "Diablo II.exe" and you should do fine.
Nac|||EDIT: Nevermind, just saw the above post|||i cant fix this someone please post how u fixed it!!!
i dont use mods ive reinstalled it from the site 4 times in different locations each time i still get this error please tell me how to fix it|||i fixed it finally... somehow the file is moved to the c drive and u have to move it to the diablo folder ty not telling any1 how u fixed it opening poster..
Disconnected
Since 1.13 I can't stay in a game for more than max. 10 minutes at the time before the game stalls and I get the disconnected message. After this when i return to the create game screen My char can't join as well as I can't create a game..
any ideas? this was a big problem at 1.11 and 1.12, but now it has grown even bigger in 1.13 on LOD Europe realm...|||It is because of an exploit people are doing.
More or less hacks/cheating that is killing the servers.|||Ya its been doing the samething to me tonight. Played fine last night i just figured it was an overload on the server due to the amount of people playin i play us east|||Yeah, same.. it's been happening to me also. Is it affecting everyone in every game at that same instant? Or is it just me?|||I've seen "your connection has been interrupted" followed by "unable to join game" when I try to get back in at least 8 times today (on USWest) realm. Whoever or whatever it is doing hacks or something that causes this problem for real people just trying to play the game is really annoying. I was looking forward to the 1.13 patch, but now I wish there were some way to go back to 1.12 because the current mess is awful.|||It is most likely occuring to 85-90% of bnet of every realm
Where these numbers come from, i threw it out there but I only assume so because it is not people, it is the servers that people are playing in that are lagging. And having limited servers, of course a great majority will lag.|||It really @#$%es me off.
I made my own game and wait 10 min or so before I xfer'd some early treasures. Right when I dropped it all and was ready to exit and join with another character this stupid ban hits me.
I gotta pay the price for other's cheats, and they reap the rewards without facing anything.......|||^ Yeah. That's why i got someone to join my game just in time. phew.. Sorry for your loss though|||I also get this very regulary. Game stalls and then the message about being disconnected.
Can't create or join games anymore with the current character for a couple of minutes, but during those minutes i can play with another character just fine.... until that one runs into the same problem.
Game becomes less enjoyable every time|||Its a problem all over that seems to be a Blizzard problem from all I have been reading recently. These Interruptions and non-access is ridiculous. Like someone said, all we can do is complain and complain. Which is what I am doing. Good luck
any ideas? this was a big problem at 1.11 and 1.12, but now it has grown even bigger in 1.13 on LOD Europe realm...|||It is because of an exploit people are doing.
More or less hacks/cheating that is killing the servers.|||Ya its been doing the samething to me tonight. Played fine last night i just figured it was an overload on the server due to the amount of people playin i play us east|||Yeah, same.. it's been happening to me also. Is it affecting everyone in every game at that same instant? Or is it just me?|||I've seen "your connection has been interrupted" followed by "unable to join game" when I try to get back in at least 8 times today (on USWest) realm. Whoever or whatever it is doing hacks or something that causes this problem for real people just trying to play the game is really annoying. I was looking forward to the 1.13 patch, but now I wish there were some way to go back to 1.12 because the current mess is awful.
|||It is most likely occuring to 85-90% of bnet of every realmWhere these numbers come from, i threw it out there but I only assume so because it is not people, it is the servers that people are playing in that are lagging. And having limited servers, of course a great majority will lag.|||It really @#$%es me off.
I made my own game and wait 10 min or so before I xfer'd some early treasures. Right when I dropped it all and was ready to exit and join with another character this stupid ban hits me.
I gotta pay the price for other's cheats, and they reap the rewards without facing anything.......|||^ Yeah. That's why i got someone to join my game just in time. phew.. Sorry for your loss though|||I also get this very regulary. Game stalls and then the message about being disconnected.
Can't create or join games anymore with the current character for a couple of minutes, but during those minutes i can play with another character just fine.... until that one runs into the same problem.
Game becomes less enjoyable every time
|||Its a problem all over that seems to be a Blizzard problem from all I have been reading recently. These Interruptions and non-access is ridiculous. Like someone said, all we can do is complain and complain. Which is what I am doing. Good luck
Subscribe to:
Posts (Atom)