Bug/problem list for Devs: what to fix for D2R

Grief is bugged Blizzard did a mistake and dont give it 340-400% instead they klick the wrong atrebut and give it 340-400 damage how is added to Character so even shilds or secund hand wapons get the bonus. that realy should get finaly fixed its like having 40 great chams with +10 max and 40 ones min Damage. sorry when sameone still dont think it is not absolutly OP and bugged. its extremly unhealthy for the game because it makes neerly every item in the game obsolet.

Sorry but I dont agree. I think it would be already fixed if that was such a obvious mistake.

Grief has special +damage property, its not really bug, that property is used by several other items, for example Redeemer, Astreon and ribcracker as well i believe. Its just very rare item mod.

It is possible that they didnt realize that type of dmg goes into shield too. But then they let it be because it really makes Smiter build to be viable.

Youā€™re obviously correct, here.

Hehe. Smite is so strong, grief is unnecessary. Can solo ubers in a few hours after reset with minimal gear. Viable ā€¦ :stuck_out_tongue:

This is an impressive list and deserves credit for itā€™s value. It is unfortunate however that you felt the need to pad it with several BS entries that are not bugs at all, you should feel particularly ashamed for entry ā€™ 103) Player killing problem '.

Several ā€˜bugsā€™ on this list are now considered ā€˜featuresā€™ by the majority of the player base IMO should remain. I hope the devs stay true to their comments about such things in the ā€˜deep diveā€™ video and leave some. Entries 1, 2, 3, and 10 are examples of ā€˜bugsā€™ which should now be considered ā€˜featuresā€™ and remain in the game.

There are also silly things on there like 117 and 118 which may or may not be ā€˜bugsā€™ but are also a complete waste of time to address. I hope the devs are wise and sort through this long list which does contain things which should be fixed but are hidden among garbage that is irrelevant, things that were never bugs to begin with, and carebear pleading to remove PK and ruin the game.

Iā€™ll add to this list one exploit I didnā€™t see mentioned since it contains other exploits that are only usable with third party addons or packet sending: Itā€™s possible to acquire several (but not all) quest rewards instantly by simply sending quest completed packets. One example is a player may be rewarded the +5 stat point reward from returning lam esonā€™s tome by sending a quest packet without even having the object in their inventory. IIRC it works for the horadric malus as well. It could also perform innocuous things like filling the Pandemonium Fortress with Mephistoā€™s Soulstone.

Hereā€™s another one: Itā€™s possible to select a hidden ā€˜kickā€™ skill (the one used to break pots etc) which has 100% accuracy and knockback. For instance, some PK exploits will watch for a namelock teleport or a teleport on your characterā€™s tile and then automatically activate this skill, sending the opponent into kb animation instead of sending you into the ā€˜slainā€™ state via hammers or whatever.

I just have to say that complaining about the Horadric Hand Axe is ridiculous, the thing is super-cute and Khalimā€™s Will is far superior for twinking a level 1 character anyways. I wish the cube bug worked on that thing!

I named the topic bug list because majority of it are bugs. There are some things which are exploits or bad mechancis used by hacks. Or were. I was out of battle net for a long time so I didnt know some stuff was maybe fixed. I will react to several things you said.

Just because they are considered features doesnt mean they should stay in game. Are we letting in only bugs which are making us characters stronger or better to make game more easy? I dont think we should. Bug is a bug and should be fixed.

Why? As I understand that point, its about ability to harm others even if you didnt want to while you were declared hostily by someone. You have to understand that I gathered points in my list from many sources and just because something is there, doesnt mean I believe it should be fixed, or not. Its not my opinion to fix all this stuff. For example I dont have really issue with point 103, but some people might. And thats why its there.

Why? Because they are making game more easy for you which was not intended?

I agree, these two points dont have to be adressed. But it is a bug and honestly any kind of bug might somehow result in exploits or for example duping method. There were many methods of duping using glitches and bugs in game.

Not sure what do you mean? I didnt plead anywhere to remove PK from the game. I was PK myself occasionaly and i like the feature.

Its not complaining, its a bug so i implemented that.

I will add these two.

the only bugs i think should be fixed are the ones that negatively effect the player. 99% of these bugs have been around so long they are practically as much a part of the game as the three prime evils.

Mmm it seems I misread 103 or it was edited to be more clear. For whatever reason when I read that it seemed like it was asserting that you should be able to prevent or disable the other playerā€™s hostility towards you - a big no no (and something that has been shamelessly asked for on this forum by trolls).

Just because they are considered features doesnt mean they should stay in game. Are we letting in only bugs which are making us characters stronger or better to make game more easy? I dont think we should. Bug is a bug and should be fixed.

I think they should, even if they werenā€™t originally intended they have been a part of the game and culture of the game for 20 years. The dev team acknowledged this in the deep dive video and said they would leave these features, specifically citing things like mephisto moat trick iirc. Quest bugging bosses falls along similar lines and incentivizes more character creation for specific tasks. It will still take hundreds to thousands of runs to find something worthwhile. The Horadric cube on quest items bug is more of a party trick than ā€˜making us characters stronger or better to make game more easyā€™, besides the novelty itā€™s really just a waste of mats. And ebug armors are just cool, additional mid-late game content, like a side quest to make your merc slightly stronger.

I find it pretty hilarious that people use the excuse of ā€œmakes the game easierā€ with any balance change, skill fixes, charm inventory, etc. However, fixing bugs or exploits that actually do make the game easier and thus fixing them properly would make the game ā€œharderā€ people call them ā€œfeaturesā€ and say hell no. With that said, I do agree to fix the ones that negatively impact players as opposed to the ones that have positive, if unintended, side effects. I would not be against fixing the Grush glitches though.

Charm inventory indisputably makes the game significantly easier. Itā€™s not about ā€˜easier or harderā€™ itā€™s about ā€˜changing the game into something elseā€™ in a remaster. Charm inventory is lame and everyone who wants it should feel bad.

It wasnt edited. Its exactly like it is there for weeks since i wrote that.

So because bug is making your char stronger its cool and wanted?

I have never in my life played with ebugg. And I didnt miss it.

Funny, negative bugs are around exactly same time as bugs making your character stronger or to exploint certain things. Both negative and postiive bugs should be fixed. They are bugs. Its hilarious that you people wan to keep bugs making game easier while you are ok with fixing bugs having negative effect on gameplay.

Because being able to utilize your entire inventory with charms anyways makes the game so much more hardcore. Gimme a break. The only think a charm inventory makes ā€œeasierā€ is inventory management and FFA loot space. But in any case, the point stands in that people are hypocrites many times with bug fixing vs QoL. Donā€™t balance skills because that would make it ā€œtoo easyā€ but donā€™t remove ebugging, quest bugging, glitch rushing, etc, even though removing those would actually make some aspect of the game harder.

So because bug is making your char stronger its cool and wanted?

You can keep saying that like a robot but like Iā€™ve already said that is not the reason. These have become iconic features and if the dev team stays true to what they said they will remain. Ebug is like running a quest for a dice roll at a chance of a better item for your mercenary. Removing it is removing content, and the power boost is actually pretty small. I generally use treachery so donā€™t ebug armors except for trading.

Loading a new character with a charm inventory would be pretty similar to playing with some botterā€™s enchantress buff. It will make the game significantly easier, youā€™re in denial. Play your mod if you want that. Once again regarding skill ā€œbalance changesā€ itā€™s not about ā€œeasierā€ itā€™s about ā€œfundamentally changing the gameā€. This is a ā€œremasterā€, if you want to change the game so your dunce builds compete with cookie cutter ones then once again please go play your mods. This discussion is off topic and besides itā€™s obvious youā€™re interested in insults rather than discussion. Bye.

If you think I was insulting, sorry. I was simply stating it is funny how people view QoL changes vs bug fixes, and there was no other way to get around using the word ā€œhypocriteā€ because it stands in that statement. I made a blanket statement, where on the other hand, you specifically called out Zax for ā€œsounding like a robot.ā€

As for your example of a new characterā€¦we ALREADY DO THAT through muling, and now a shared stash. As for a completely new character during ladder reset, you canā€™t fill up a space with something you have not found yet.

As for fundamentally changing the game, the originally devs specifically made the change to make balancing skills easier. It was meant to be tweaked, it was a unfinished balance from itā€™s original 1.10 incarnation, and HAD been tweaked in more recent patches. Wonā€™t argue remaster, as the distinctions have been argued to death anyways, and are pretty null and void in light of any recently released remasters that have made more drastic changes.

So negative bugs didnt become iconic? I think you only see what you want to see and ignoring bigger picuture. Its nice excuse tho, that bugs become iconic features.

If eth bug is so important and iconic, just buff eth armors and remove bug. Same with q drop bugs, improve drops and remove bugs. Problem solved, bug fixed.

LMAO what? bugs are content now? :smiley: I hope we wont see much of that content type in D2R.

Zax, you are doing an amazing thing compiling all this :slightly_smiling_face:. Keep doing what you are doing. Donā€™t listen to any naysayers. All you are doing is listing bugs no matter if they are beneficial or negative. At the end of the day, Itā€™s up to the D2R devs to decide on what to fix but itā€™s really good to have a compiled list of all the bugs that exist in D2, no matter what they are. :+1: :+1:

ā€œ160) Blaze skill bug
Blaze donā€™t give 1% damage per point to firewall.ā€
**Blaze is not supposed to give 1% dmg to firewall.

ā€œBlessed Hammer not describing its 50% damage vs demon bonus.ā€
**It does 50% more to undead unless that is what you ment?

ā€œ103) Player killing problem
PK problem: doesnt 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.ā€

It was intended to be able to kill other players without mutual hostility, this is not a bug.

It was intentionally designed as a nod to Diablo1, where you could even kill a teammate accidently with a misguided fireball or arrow. This has been referenced in interviews.

Thats why there is ā€œproblemā€ and not a bug.

This is about deactivating it. Lets say i missclick and declare hostily to you and then i will deactivate it immediately. You will still have declared hostilily against me even when you didnt click on anything on your own.

Iā€™m not sure this is a bug.

Lazy coding, maybe. Bad design, probably.

Do we have evidence itā€™s a bug?