I'm having some problems testing for a quest item.

At one stage in my quest, the player is asked to recover the Ink Container from Arlington (MS15ink). I can successfully use getitemcount in dialog to verify that the player possesses the the ink container and skip that stage, but the same test when used in the quest script does not seem to function.

(Player.getitemcount MS15Ink > 0)

Am I missing something about how GECK counts quest items in inventory or do my problems lie elsewhere?

This looks completely normal to me. I think it should work.

There is nothing wrong with the getItemCount so it must be a problem with your quest.

Actually, there is nothing wrong with the quest. I've just been chasing my tail hunting down stupid user tricks. Think its time to go to DisneyLand.

Uhm... Don't you need an "If" in front of that Quest script code snippet?

Just post the result script; there might be a silly mistake that a fresh pair of eyes will spot.

Just a small note about http://geck.gamesas.com/index.php/GetItemCount - because it can only return an integer greater than or equal to 0, and pretty much no optimisation is done to expressions when your script is compiled, it's more efficient to just do this:

if player.GetItemCount MS15Ink

That's as opposed to doing this:

if player.GetItemCount MS15Ink > 0

Cipscis

Show us the entire script. Are you using this in a gamemode block? Menumode? Anything like that could matter as it could be whats stopping the line from ever running.

Snippet is from a quest script. Full segment runs in a game mode block as follows:

IF  (Getstage xCalBOE == 20) && (Player.getitemcount MS15Ink > 0)		SetStage xCalBOE 25	EndIF

A few users have reported problems with the quest stalling at this point 'though they claim they recovered the ink container. At least one person who reported the problem later claimed they resolved it by changing load order.

I suspect there is nothing at all wrong with the code, but there is potentially an unanticipated condition that does not get handled directly. I just can't think what it might be.

As usual Cipscis your advice is sound, but I worry about those unanticipated states like another mod adding additional ink containers.

Hey, while I'm hogging a thread, does anyone know why this won't work?

;##################### Stupidity TestIF GetGameLoaded	IF (IsModLoaded xCALIBRmunitions_FOSEnhancements)		Showmessage xCalFUBAR1	ElseIF (IsModLoaded xCALIBRmunitions)		Showmessage xCalFUBAR1	EndIFEndIF

Hmm. Well, first off you could just create a unique reference of the ink in order to rid of the probably of compatability with other mods. Also, whats your quests script delay. Maybe they just arent waiting for it the process the script?

I've always use quotes for the mod names and it works:

IF GetGameLoaded	IF (IsModLoaded "xCALIBRmunitions_FOSEnhancements")		Showmessage xCalFUBAR1	ElseIF (IsModLoaded "xCALIBRmunitions")		Showmessage xCalFUBAR1	EndIFEndIF

Not a bad idea Gunmaster95, though not the direction I want to go in. I'd rather lead the player to a quest item they might otherwise miss.

Sweet! Thanks RickerHK. I never would have thought of quotes.

FOSE's documentation is just embarrassing. Maybe this community can start a stick thread to pool our collective, hard earned, wisdom (well others wisdom, not mine). I shudder every time I approach a new FOSE command knowing it will be like throwing darts against a wall figuring out the proper use and syntax.

I missed something from your post - for the IsModLoaded, you need the whole file name with the file extension .esp or .esm, as part of the string, like

IsModLoaded "FO3 Wanderers Edition - Main File.esp"

OK. Good to know. I stripped the file extensions because GECK's compiler choked with them.