I have a quest where the player has an NPC craft a necklace for them. The player then has to deliver this necklace to the questgiver. I don't want the player losing the necklace, so I'd like for it to be an Alias of the quest so I can mark it as a quest item. Can I somehow create an alias halfway through the quest to achieve this? Can I create it in a nearby (hidden) container, then move it to the player's inventory with a script command? (None SKSE) Is there some other way to do this?

Thanks for any help,
AJV

Yep.

Create the alias, and have it created IN a container (also an alias). Then in the script box for the stage you want, or in a script somewhere, simply use the Player.AddItem() script

Your item alias needs to be below your container alias in the alias list.

I have this in a couple of my hunting quests for some stuff.

You can't create an alias half way through a quest, but you can fill one with ForceRefTo(), for example after creating an object with PlaceAtMe() .

Another way is to start a new quest with an alias and then assign the object in that alias to an alias in another quest. That's particularly useful if you want to use the Find matching reference fill method, because Papyrus's Find functions are more limited.

A craft item event that forces the crafted object into an empty-by-default optional alias tagged with "quest item" in the parent quest?

Wait, how does it know what ref the alias is then? That doesn't make sense to me. I say 'Create a banana in this chest', then give the player a banana and it is the alias?


But if I use PlaceAtMe (Or another quest) how would I get the reference into the player's inventory? That's the issue. Creating the alias isn't a perticular problem, it's getting it added to the players inventory after it's created. Without the player having to do anything, as to immitate the NPC giving you the object.

Player.Additem(TheAlias).

Additem creates base references, but moves aliases.

Ah, sweet! Forget my further noobishness, but how exactly should I reference the alias when using that command? It will be in dialogue in the same quest, so is it already a 'property'? For example, if I create my alias inside a nearby underground chest, and I call the alias 'CoolNecklace' what would I type?

Player.AddItem(CoolNecklace, 1) ? I've never dealt with reference aliases before.

The trick they are talking about does work ... if you've setup for it in advance

So:

1. Create an Alias for your necklace, in the normal way. Make it Optional.
2. After the necklace is crafted, ForceToRef to get it into the (empty) Alias created
3. Then run the line of script as Ingenue suggests

Player.AddItem(MyAlias)

and all will be well




And, if you are doing it this way, no need to worry about Big's ordering ... that is only applicable if you are using the create-in, as he suggests ...

... and you could do it that way. Have the Player as an Alias (don't shoot me, Justin!) and then use a Create-In on the player to put the necklace in the game-world ... If you did that the necklace alias would need to come after the player-alias in the Quest-Alias Tab

Yea I should have said you don't need a container to be the middle man. You can create an alias to an object, make it optional, then add the item to the player at a later stage, calling the alias name inside the ()

Yep.

• If you pass the AddItem function an Alias it does a MOVE (not a create) ... because the Alias must be filled and so is already in the game-world (somewhere).
  
• If you pass it a base form then it does a create.

Okay, the whole 'fill the optional alias' thing just has me confused, so I'll just stick it in a chest somewhere hidden from the player, then I'll move it when the time comes for the player to have it.

Thanks guys! I didn't expect so much help!

You would add a property of type ReferenceAlias to the dialogue script. You can fill such a property with the alias of any quest.

Assuming a "jeweller" is passing this necklace to the player, for them to deliver, then you might find B1g's original suggestion easiest, AV?

Just do a create-in, on the Player (as a container) ... You'd need a sub-quest though ... So may not the best idea, afterall ...

So yeah, just shove the thing in a chest and move it as needed ... You're right AV.

Well, I get the impression the player is supposed to make the necklace, so if you don't want to deal with setting up a Craft Item event node to handle that, then what could happen is at the appropriate time, just start checking for if the player has crafted the necklace in a script and swap it out for the one in the alias once the player gets a copy.

The player is not crafting it, the NPC is. The issue was simply how to create it when he handed them the necklace, or move the already created alias into the players inventory, which I now know AddItem will do.

If it helps the WICourier quest does this with the courier's note. It creates a new note to fill the alias, sticks it in the courier's container and moves it to the player when the note is delivered. Useful if you need an example.

Not sure if I'm missing something, but I did 'Game.GetPlayer().AddItem(Necklace) and I get this error:


Necklace is a 'ReferenceAlias' property I made on the script and directed towards my quests alias. Do I need to cast as something? I tried ObjectReference, and Armor, and it said both were incompatable. :/

http://www.creationkit.com/AddItem_-_ObjectReference expects a parameter of type http://www.creationkit.com/Form_Script. In order to get this from a http://www.creationkit.com/ReferenceAlias_Script you'll want to call http://www.creationkit.com/GetReference_-_ReferenceAlias on it and then http://www.creationkit.com/GetBaseObject_-_ObjectReference on the result of that.

Cipscis

But that would circumvent the entire point of this. To add an alias to the players inventory partially through the quest. If I add the base object (And I know exactly what it is, and it's always the same), wouldn't it just add one of those objects, and not the one marked as my alias?

I still think best way is to start a new quest and use the Create-In Option.

Yeah, it may well mean making a couple of logic changes to the quest structure, but should not be much ... You could even split the quest just before the necklace is created. So Part1 runs to the step before creation and then Part Two starts and Creates the necklace alias (in the player container) as one of its startup steps.

Easy to do and works like a charm ----> Last dialogue event in Part One is "here is the necklace, can you take it to Mr Smith for me?" (script to start Part2) and then - in Part Two - necklace is "created in player container" Alias and Objective set to Mr Smith (script on Necklace, OnChangedContainer ... check it is Mr Smith ... complete Quest)


No need for all the mither

When you're adding an item to the player, the script needs to know which one. In this situation you have 2 options.

1. Make a property of the object, and add that item.
2. Add the item as its alias, rather than its property.

So you could use

Game.GetPlayer().AddItem(Alias.GetReference().Aliasnamehere, 1)

Which would make the quest look for that alias item and add it.

Going all the way back to the Form level is unnecessary for AddItem. The function permits References to be used, as well (Beth's own setup of the function is a bit misleading in that regard). So just do an AddItem (MyObjectAlias.GetReference()) and it will move the Refernce that is currently filling the Alias into the Player's inventory.

Okay this appears to be what I was missing, but I'm lost on the syntax. It's telling me that GetReference() isn't a function.

So I have the alias in my quest, that's a 'Create In' on a nearby underground chest. I created a property on the script fragment that's a ReferenceAlias directed to my quest's alias. And I called it Necklace. Based on that info, is this the incorrect way of typing the line?:

Game.GetPlayer().AddItem((Alias.GetReference()).Necklace)

It depends which script your AddItem is in. If its in the quest script, you call Alias. For example in a quest stage.

If its in a seperate script, you word it differently.

Let me switch my PC on and get you my script I only ever use aliases where I can, so I have it all down.

Okay. It's currently in a dialogue response end fragment.