Difference between revisions of "Talk:Heresiarch"

From DoomWiki.org

(Inconsistency in the article)
 
(Bleh, Hexen code >_<)
Line 8: Line 8:
  
 
Okay, so what's the truth? Can you hurt a shielded Heresiarch with the fighter's melee weapons or not? [[User:JudgeDeadd|JudgeDeadd]] 16:53, 29 December 2013 (UTC)
 
Okay, so what's the truth? Can you hurt a shielded Heresiarch with the fighter's melee weapons or not? [[User:JudgeDeadd|JudgeDeadd]] 16:53, 29 December 2013 (UTC)
 +
 +
: I'll try to dig into the code and confirm which damage types are allowed to get through the Heresiarch's invulnerability; unfortunately this stuff is just haphazardly hard-coded all over the Hexen executable so it's easy to miss - and in some cases even, misinterpret - the code responsible. To make it worse plenty of code in Hexen doesn't even do what it's obviously meant to do by the developers, due to subtle issues they didn't catch and which even skilled programmers can overlook when reading the code - it's a nightmare, in other words. --[[User:Quasar|Quasar]] 15:34, 30 December 2013 (UTC)

Revision as of 10:34, 30 December 2013

Disrepancy

"The Heresiarch can (...) Create a barrier that deflects projectiles."

"For players using Baratus (the Fighter), the Heresiarch can be hard to kill because he can only be hurt while his barrier is down."

"Note that the Heresiarch with the deflecting shield up will still be damaged by any melee weapons, including the fighter's axe (...) He's not that invincible really, it's only an anti-missile shield. "

Okay, so what's the truth? Can you hurt a shielded Heresiarch with the fighter's melee weapons or not? JudgeDeadd 16:53, 29 December 2013 (UTC)

I'll try to dig into the code and confirm which damage types are allowed to get through the Heresiarch's invulnerability; unfortunately this stuff is just haphazardly hard-coded all over the Hexen executable so it's easy to miss - and in some cases even, misinterpret - the code responsible. To make it worse plenty of code in Hexen doesn't even do what it's obviously meant to do by the developers, due to subtle issues they didn't catch and which even skilled programmers can overlook when reading the code - it's a nightmare, in other words. --Quasar 15:34, 30 December 2013 (UTC)