==daedra_ missing implementation

For bugs relating to quest scripts and quest system emulation.
Post Reply
User avatar
Jay_H
Posts: 2999
Joined: Tue Aug 25, 2015 1:54 am

==daedra_ missing implementation

Post by Jay_H » Fri May 24, 2019 12:19 am

Quest is P0B10L08

Image

Curiously, I see no need for a new name here. _daedra_ works perfectly well on its own, but for some reason this quest insists on using ==daedra_.

(The %vam stuff is irrelevant.)

BansheeXYZ
Posts: 532
Joined: Fri Oct 23, 2015 8:19 pm

Re: ==daedra_ missing implementation

Post by BansheeXYZ » Sat Jul 13, 2019 4:47 pm

This string is used by many witch coven quests as well as this vampire quest.

Since dfall treats daedra princes as factions, and I think == means faction name, the usage here is appropriately ==daedra_. So it should be a name like Hermaeus Mora or Namira.

_daedra_ is used by QBN to define enemy types like daedroths and frost daedras. I don't see it used in a QRC and I'm not sure what it would do if you tried.

BansheeXYZ
Posts: 532
Joined: Fri Oct 23, 2015 8:19 pm

Re: ==daedra_ missing implementation

Post by BansheeXYZ » Sun Jul 14, 2019 8:23 am

Here is the macro in action in classic, Q0C00Y08 quest. It is indeed a random daedra prince faction.
dae1.png
dae1.png (41.36 KiB) Viewed 1699 times
dae2.png
dae2.png (43.37 KiB) Viewed 1699 times

Post Reply