0002572: Enslavement = Mummy Death Curse Mis-Target - Dungeon Crawl Stone Soup Tracker

(0008546)
evktalo (administrator)
2010-09-13 11:06

I've seen this too, and I think it's a bug (or a misfeature) - after all, summons work too, so you should be able to shift the blame. And Enslavement doesn't work on high-end mummies, so it's not something you could do Tomb with.

--Eino

(0008560)
Kyrris (reporter)
2010-09-13 15:41

The rationale is that the mummy died as a direct result of your charming it. So you got credit, including full--not half--xp, for the kill. And the curse.

(0008567)
evktalo (administrator)
2010-09-13 16:51

I agree the rationale is ok, but it'd be cooler the other way. :)

--Eino

(0014212)
jeffqyzt (reporter)
2011-08-17 15:10

Perhaps it would be clearer if there was a distinction in how the enslaved vs. summoned creature is described, since there is in fact a distinction in how they're treated? e.g. instead of "your mummy" in this case, something like "the mummy you enslaved" or "the enslaved mummy", representing that the creature's "true feelings" are still hostile toward you.

(0014217)
galehar (administrator)
2011-08-17 16:39

"your" means friendly. I don't think calling it enslaved would help anything. I agree with evktalo, it would be more fun if you didn't get the curse in this case. And maybe also half XP (or more if you hit it before enslaving it).

(0014218)
dpeg (administrator)
2011-08-17 16:45

While more fun at first, this could lead to something tedious at first: use wands of enslavement on mummies, and let them kill themselves -- akin to dropping potions before engaging a mummy before.

I like it if the player cannot shake off the mummy curse easily.

(0014220)
galehar (administrator)
2011-08-17 17:06

Players can already shake off mummy curses easily with summons. Enslaving them to make them fight hostile monsters is not much different than summoning monsters to fight them. The point is to not fight them yourself.

(0014221)
argonaut (reporter)
2011-08-17 19:17

There's a similar issue with inner flame. I used inner flame on a gnoll with the expectation that when the explosion got the mummy the curse would be directed at the gnoll (since it was the one blowing up). Didn't work out, I still got cursed.

I don't really see using either inner flame or enslavement as much different than letting a summons do the job.

(0026520)
wheals (administrator)
2014-06-15 18:27

Made more consistent in 6ffeb14a: killing a mummy with a summon will also curse you.

Issue History
Date Modified	Username	Field	Change
2010-09-13 01:56	Hybrid	New Issue
2010-09-13 11:06	evktalo	Note Added: 0008546
2010-09-13 11:06	evktalo	Status	new => confirmed
2010-09-13 15:41	Kyrris	Note Added: 0008560
2010-09-13 16:51	evktalo	Note Added: 0008567
2010-09-22 10:23	doy	Relationship added	related to 0002624
2011-08-17 15:10	jeffqyzt	Note Added: 0014212
2011-08-17 16:39	galehar	Note Added: 0014217
2011-08-17 16:45	dpeg	Note Added: 0014218
2011-08-17 17:06	galehar	Note Added: 0014220
2011-08-17 19:17	argonaut	Note Added: 0014221
2011-08-19 00:44	galehar	Issue Monitored: galehar
2011-10-25 00:26	galehar	Issue End Monitor: galehar
2014-06-15 18:27	wheals	Note Added: 0026520
2014-06-15 18:27	wheals	Status	confirmed => resolved
2014-06-15 18:27	wheals	Fixed in Branch	=> 0.15 development branch
2014-06-15 18:27	wheals	Resolution	open => done
2014-06-15 18:27	wheals	Assigned To	=> wheals

Notes
(0008546) evktalo (administrator) 2010-09-13 11:06	I've seen this too, and I think it's a bug (or a misfeature) - after all, summons work too, so you should be able to shift the blame. And Enslavement doesn't work on high-end mummies, so it's not something you could do Tomb with. --Eino

(0008560) Kyrris (reporter) 2010-09-13 15:41	The rationale is that the mummy died as a direct result of your charming it. So you got credit, including full--not half--xp, for the kill. And the curse.

(0008567) evktalo (administrator) 2010-09-13 16:51	I agree the rationale is ok, but it'd be cooler the other way. :) --Eino

(0014212) jeffqyzt (reporter) 2011-08-17 15:10	Perhaps it would be clearer if there was a distinction in how the enslaved vs. summoned creature is described, since there is in fact a distinction in how they're treated? e.g. instead of "your mummy" in this case, something like "the mummy you enslaved" or "the enslaved mummy", representing that the creature's "true feelings" are still hostile toward you.

(0014217) galehar (administrator) 2011-08-17 16:39	"your" means friendly. I don't think calling it enslaved would help anything. I agree with evktalo, it would be more fun if you didn't get the curse in this case. And maybe also half XP (or more if you hit it before enslaving it).

(0014218) dpeg (administrator) 2011-08-17 16:45	While more fun at first, this could lead to something tedious at first: use wands of enslavement on mummies, and let them kill themselves -- akin to dropping potions before engaging a mummy before. I like it if the player cannot shake off the mummy curse easily.

(0014220) galehar (administrator) 2011-08-17 17:06	Players can already shake off mummy curses easily with summons. Enslaving them to make them fight hostile monsters is not much different than summoning monsters to fight them. The point is to not fight them yourself.

(0014221) argonaut (reporter) 2011-08-17 19:17	There's a similar issue with inner flame. I used inner flame on a gnoll with the expectation that when the explosion got the mummy the curse would be directed at the gnoll (since it was the one blowing up). Didn't work out, I still got cursed. I don't really see using either inner flame or enslavement as much different than letting a summons do the job.

(0026520) wheals (administrator) 2014-06-15 18:27	Made more consistent in 6ffeb14a: killing a mummy with a summon will also curse you.