Jump to content

[LE] Location Ref Types not filling Aliases


Recommended Posts

I am working on a mod where I am currently trying to get the boss of a location and put it into an alias, and I am trying to do it like the bounty quests where they simply use the location alias and find the ref type boss to fill the alias. I do not believe that this requires the use of the story manager (please tell me if I am wrong) because it is not using that aspect of the alias menu to fill the alias.

However, I am not sure what else I need to do to make the alias work. I have the locations checked so that they can't use an already reserved location, and trying to allow reserved on the boss alias does not work anyway. I do have the alias formatted as the bounty quests have it, but it still refuses to fill the alias.

Does anyone have any ideas about what I might be doing wrong? I prefer not to need to place an actor at these locations as I am trying to make the mod as compatible with other non-radiant quests as possible if they pop up in some of the dungeons I'm using.

 

Thanks in advance.

Link to comment
Share on other sites

1. Use the "SQV myQuest" console command to check whether your quest starts at all, and check which aliases fill and which do not. Be aware that if any alias in your quest fails to fill, all aliases below it in the list will automatically fail to fill too.

 

2. What are your exact fill type settings and conditions on your aliases?

Link to comment
Share on other sites

I have used the SQV command and my quest is running. I am using a script to force most of my alias to fill with randomly chosen object references, but the bosses are the only ones that don't fill except for maybe the unique character references below the bosses. Is there an easy way to reorder the reference aliases so that these unique references are on top.

 

Otherwise, my boss aliases use the location alias reference for my locations that I fill in from a script and using the ref type boss (all the locations have a boss, I checked). They reserve the reference and allow using reserved references. However, I plan to change this. they all store text as well.

Link to comment
Share on other sites

If you want to use Location Alias Reference fill type for the boss, then you need to make sure that the location alias itself is filled from the start as well, because aliases will only attempt to fill automatically once: When the quest starts. So it is not good enough to fill the location alias via script. Use a unique location or use conditions to fill it.

 

The same is true for any other aliases above the location alias and the boss alias. If they fail filling as the quest loads up, everything below them will also fail to fill. If you fill them via script, make sure to check the Optional setting for all of them. This marks for the quest that they don't need to fill immediately for the quest to run.

 

The << and >> symbols in the quest alias tab are used to move any selected alias up or down in the list.

Link to comment
Share on other sites

So I ended up needing to build an entirely new make of the quest and filling the aliases up again, being careful to keep all references that are not forced filled through script up at the top. It works a lot nicer, however, the quest is now iffy about whether or not it decides to fill the aliases when the quest starts. Sometimes the aliases fill when I coc on Riverwood, and sometimes they don't.

 

I was good up until the point that I start adding the optional blanks at the end of the quest, but I believe that I should be allowed to keep those aliases as they are optional. If anyone knows what I am doing wrong, I would love to hear it. I don't think that I need the optional aliases if push comes to shove, but I would prefer to be able to keep them if I can.

 

PS I am also waiting a reasonable amount of time to use the sqv command to check my quest (until Faendal is done collecting is wood as he does every time I coc on Riverwood.)

 

Edit: I tried removing the optional aliases and loading it up and it is still iffy. However, my other start-enabled quest is completely fine with all aliases filling, whether they are forced or not.

Edited by SirBeastling
Link to comment
Share on other sites

Optional aliases should be allowed by the quest no matter if they fill or not, and no matter where in the list they are. I recommend setting all of them to Forced fill type though, just pointing at no references at all. Otherwise, they might fill with something you don't want them to fill with.

 

Without knowing more details about your aliases and how they are all conditioned and placed, I can't help you much more.

 

One thing: For mods with start-enabled quests in particular, it is even more important than usual that one generates an SEQ-file for the mod. Whenever you create a new start-enabled quest or edits the start-enabled flag for a quest, you should generate SEQ. This primarily fixes dialogue issues, but it might help out with more than that. You can generate SEQ through TES5Edit, and if you don't use that, follow these instructions.

Link to comment
Share on other sites

Thank you. I've been sure to constantly generate seq files while I work through my mod, every time I make a new quest. I will make sure to fill the optional references as well, however, I removed them for the time being to lessen the number of aliases in the quest.

 

I also am not planning to keep the quest I am working on as start enabled. It is going at the end of a storyline. Once I feel it is starting up well enough, I will be moving it to the end of the quest. I just felt that having to do a fresh start and go through the prior to quests would not be as efficient, even though it would probably work better in its correct place, so I will move it to where it is supposed to be and give that a try as well.

 

I've also attached my alias list below if it helps. The forced references are on top while the location references use a form list of locations I created to choose from randomly, which works. The boss aliases then search for the boss ref type in that location to fill itself, which is now working better since I recreated the quest.

 

 

Link to comment
Share on other sites

List looks fine. Are you absolutely sure that all of your chosen locations even contain boss type references? And sure that they are not already marked as reserved for other quests?

 

If not, a way to test it: Instead of random locations, check your locations one at a time, and see if there's one specific location that prevents its boss alias from filling.

Link to comment
Share on other sites

So your suggestion gave me an idea. I set the boss aliases to optional and started up the game. So far, the aliases load, except for a couple of boss aliases which I've already noticed load up the boss from similar locations.

 

So I will need to go through all my locations and make sure each boss is not used by another hard-coded quest.

 

Thank you for all your help. I'll comment back when I find the locations that have their bosses in use.

Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...