Quest is P0B10L08
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.)
==daedra_ missing implementation [RESOLVED 0.10.26]
- Jay_H
- Posts: 4078
- Joined: Tue Aug 25, 2015 1:54 am
- Contact:
-
- Posts: 555
- Joined: Fri Oct 23, 2015 8:19 pm
Re: ==daedra_ missing implementation
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.
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.
-
- Posts: 555
- Joined: Fri Oct 23, 2015 8:19 pm
Re: ==daedra_ missing implementation
Here is the macro in action in classic, Q0C00Y08 quest. It is indeed a random daedra prince faction.
- Ferital
- Posts: 282
- Joined: Thu Apr 05, 2018 8:01 am
Re: ==daedra_ missing implementation
I submitted a PR to fix this issue, as well a a similar error in quest R0C60Y24 which uses the ==vampire_ quest macro to get the name of the vampire clan.