Page 2 of 2

Re: Alignment

Posted: 30 May 2012 18:31
by Jhael
NECRO THREAD!

Alignment is gained (or lost) by landing the killing blow on an enemy, right?

It seems like it would make sense for alignment to change based on what your team is killing. For example, if I'm holy but am in a team that is demolishing Kalaman ... just because my weapon didn't KILL anything, doesn't really mean I'm fault-free.

Re: Alignment

Posted: 30 May 2012 21:17
by Draugor
Jhael wrote:NECRO THREAD!

Alignment is gained (or lost) by landing the killing blow on an enemy, right?

It seems like it would make sense for alignment to change based on what your team is killing. For example, if I'm holy but am in a team that is demolishing Kalaman ... just because my weapon didn't KILL anything, doesn't really mean I'm fault-free.

Tbh just attacking good aligned NPCs should fuck your rep up, 10% drop from what the NPC would yield in regular instances and then it gets worse ad you keep fighting

Re: Alignment

Posted: 31 May 2012 15:30
by Jhael
Draugor wrote:
Jhael wrote:NECRO THREAD!

Alignment is gained (or lost) by landing the killing blow on an enemy, right?

It seems like it would make sense for alignment to change based on what your team is killing. For example, if I'm holy but am in a team that is demolishing Kalaman ... just because my weapon didn't KILL anything, doesn't really mean I'm fault-free.

Tbh just attacking good aligned NPCs should fuck your rep up, 10% drop from what the NPC would yield in regular instances and then it gets worse ad you keep fighting
This is basically what I was trying to get at. If I get Calof to DD and then leave so Draugor can get the last hit ... I should probably lose some good align.

Re: Alignment

Posted: 31 May 2012 16:09
by Makfly
Trying to make sense of the alignment system is futile.

It's an (irrational) artefact from old AD&D days, and it has its charm, even if it makes little real world sense.
At least I think it is easier to come to terms with, when I accept that it makes no sense, and doesn't have to.