-
Notifications
You must be signed in to change notification settings - Fork 793
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Golem fixes #6430
Golem fixes #6430
Conversation
Is there consensus on this? I think special-casing the golem like this is a bad idea. If he is classified as a Demon, he should have the Demon behaviors. |
There are only 3 monster types, and it seems plausible that demon was selected because weapon class bonuses wouldn't apply against it |
If we are to assume that Golem is not supposed to actually be a demon, then you also need a special case for |
That seems quite far-fetched to me actually. Why would you jump to this conclusion? It is much more likely to me that Demon was selected because it just made the most sense among the existing types. |
Perhaps because the only time the monster type of Golem matters in vanilla Diablo is when your melee attacks incidentally hit a passing Golem. Golems were not targetable, and they never attacked players. So there was likely zero thought put into the effect that 3XDAMVDEM would have on Golem. |
I agree they probably didn't think out how affixes would apply, but I also think that they could have just defined the golem as something else (I don't think making a 4th define just for Golem would have been a huge issue). I would probably just leave it as demon and keep whatever interactions come from that, since you could trigger them in vanilla, it was just more difficult because you couldn't select the golem, right? |
Logically, while I do see how one might jump to the conclusion from "they didn't think about weapon interactions with Golem because Golem can't be used for PvP," I also think it's ultimately a bit contradictory when you actually spell it out: "they must have chosen demon so the sword/club weapon interactions wouldn't apply." I'm inclined to agree with julealgon that they probably just thought demon was the most appropriate of the three.
As for this, I'd be inclined to believe they just didn't bother introducing a fourth type because they didn't have any reason to. Therefore, the technical difficulty of doing so is pretty irrelevant. EDIT: I suppose it would be more accurate to say that I'd be inclined to believe the technical difficulty is pretty irrelevant for the aforementioned reason. I don't feel I have enough info to make a definitive call on whether or not they would have introduced another type if they felt they did have a reason to do so.
Yes, I am pretty sure this is the case. |
Why would Golem be a Demon? If anything it would be Undead, but then Holy Bolt would damage it |
My thought was more that if they wanted golem to be something other than demon, they could have easily done that (I think). If there was some technical hurdle that I'm not thinking of, then maybe they would have picked demon to avoid having a 4th type defined, but I doubt that's the issue here.
Why would it be undead? It's made of clay (or stone), demon could make sense if you consider the golem body being possessed by a demon spirit or something. Regardless, they picked demon, not anything else. If they wanted something else, I'm sure they could have done that. |
Well... it was never alive in the first place, so how can it be undead 😆 At least that's my definition for what undead means: it must've been alive at one point surely. |
No, there's no technical hurdle. You can just add another value to the enum and apply it to Golem. It wouldn't be referenced anywhere in the codebase, so there wouldn't be any mechanics associated with it. It's just.. why do that? If |
TripleDemonDamage
(Golems are classified as Demons in the Monster table)