[Papyrus Help : inspect all items carry by player]

You will need to read or watch a how to create and compile papyrus scripts tutorial.

There are many on youtube.

The Bethesda Mod School series is good.

[Papyrus Help : inspect all items carry by player]

Player.inv is not a papyrus function.

You need to look up the Papyrus functions.

Most likely you will need to use GetInventoryItems() which is an F4SE function https://falloutck.uesp.net/wiki/GetInventoryItems_-_ObjectReference

Then you need to look at some base game scripts to understand the Payrus script structure and format.

[Sandboxing for non-human workshop actors]

Adding the actor to faction WorkshopNoPackages (either on ther ActorBase form or via script to the in game ObjectReference) blocks any of the WorkshopParent applied packages from asserting priority on therir package stack, so either their default or your added package will be active.

Having a script which dumps the current package is super helpful fir this stuff:

Debug.Trace("SKK_GetActorInfo CurrentPackage," + (ThisRef as Actor).GetCurrentPackage() )

 

[Sandboxing for non-human workshop actors]

Had  a similar issue with Multiracial Workshop Actors (Settlers).

(2) Most multiracial actors do not have idle animations for workshop work objects (farming, guarding, scavenge station). Rather than standing frozen in place they are configured to wander around looking busy. Calling with the bell can cause them to stop updating AI movement packages after being called until they are commanded or unload. 

 

    If ((ThisActor as SKK_MWACustomActorScript).bRaceHasWorkshopIdles == false)
        (ThisActor as Actor).AddToFaction(pWorkshopNoPackages) ;Package freeze in position when they are assigned to work objects this keeps them sandboxing
    Else
        (ThisActor as Actor).RemoveFromFaction(pWorkshopNoPackages)
    Endif

[Script to prevent certain weapons being used in power armor]

I use this simple snip for some custom objects stuff that are blocked for PA, attach it to your base weapon forms;

 

Scriptname myPowerArmorUnequipObjectScript extends ObjectReference

Keyword Property pIsPowerArmorFrame Auto Const Mandatory
Message Property pmyMessageName Auto Const Mandatory 
Weapon Property pmyWeaponBaseFormName Auto Const Mandatory 

Event OnEquipped(Actor akActor)
CheckForPowerArmor(akActor)
EndEvent

Event OnUnequipped(Actor akActor)
   Self.UnregisterForAllEvents()
EndEvent

Event OnAnimationEvent(ObjectReference akSource, string asEventName)
CheckForPowerArmor(akSource as Actor)
EndEvent

Function CheckForPowerArmor(Actor akActor)
If(akActor.WornHasKeyword(pIsPowerArmorFrame) == true)
   Self.UnregisterForAllEvents()
   akActor.UnequipItem(akItem = pmyWeaponBaseFormName, abPreventEquip = false, abSilent = false)
   If(akActor == Game.GetPlayer())
      pmyMessageName.Show()
   Endif
Else
    Self.RegisterForAnimationEvent(akSender = akActor, asEventName = "furnitureEnterSlavePA")
EndIf
EndFunction
 

 

 

 

[How Do I Add 'TeammateDontUseAmmoKeyword' To My Script?]

Here is a standlone global script fragment example that is callable from the console. Convert GetFormFromFile into properties for a form attached script:

Script SKK_GlobalScript

Function SwitchCurrentCompanionDontUseAmmo() Global ; CallGlobalFunction "SKK_GlobalScript.SwitchCurrentCompanionDontUseAmmo"

Quest Followers = Game.GetFormFromFile(0x00289e4, "Fallout4.esm") as Quest
ReferenceAlias Companion = (Followers as FollowersScript).Companion
ObjectReference CurrentCompanion = Companion.GetReference()

If(CurrentCompanion != None)
    Keyword TeammateDontUseAmmoKeyword = Game.GetFormFromFile(0x0023f1ca, "Fallout4.esm") as Keyword
    If(CurrentCompanion.HasKeyword(TeammateDontUseAmmoKeyword) == false)
        CurrentCompanion.AddKeyword(TeammateDontUseAmmoKeyword)    
    Else
        CurrentCompanion.RemoveKeyword(TeammateDontUseAmmoKeyword)    
    EndIf
    Debug.Trace("SKK_GlobalScript.CurrentCompanionDontUseAmmo updated " + CurrentCompanion)
Endif

EndFunction

 

 

 

[PSA: CK update uses a new BA2 archive format]

The version byte of the BA2 archive format changing to block older game versions is possibly as a wheeze to try and prevent the bundled CC content being back-published to frozen (you know the people who cant update for, ahem, legal reasons) game instances.

Or the action with zero documentation is yet another signal that back compatibility for mods is a zero priority for the new corporate ca$h register. 

[PSA: CK update uses a new BA2 archive format]

EZ new 100% compatible BA2 workflow, no repacking required only a hex editor (I use Free Hex Editor Neo)

 

[Delaying the start of a quest]

https://www.nexusmods.com/fallout4/articles/1038  Robust new game start script section

Replace AddInventory() with  myUserVisibleQuestName.Start() or myUserVisibleQuestName.SetStage(whatever)

 

[Condition Confusion - ANDs and ORs are giving me grief.]

It doesnt actualy matter if the AND block or OR block come first.

To help with game engine load (fail fast) I just put the broadest filter at the top which could be AND or OR.

Ideally the order would be exactly from broad to specific, but interleaving AND OR statements becomes super messy.

 

 

 

[Condition Confusion - ANDs and ORs are giving me grief.]

Gotta group them  and its always 50/50 if I configure the correct line to switch between them:

[PSA: CK update uses a new BA2 archive format]

UPDATE: the BSArchPro utility packed with xEdit 4.1.5f will OPEN the new BA2 format and SAVE the old BA2 format, so workflow can be: Meak new format archive in Creation Kit, drag into BSArch and save old format BA2. Publish old format or both. Happy(er) days !

[PSA: CK update uses a new BA2 archive format]

This is like the .160 ESL header format all over again ... 

Mod authors who have updated their Fallout4.exe game to 1.10.980 are forced to update their CreationKit to 1.10.943.

CreationKit 1.10.943 uses a new BA2 archive file format which older versions of Fallout4.exe game can not open.

The new 1.10.980 Fallout4.exe can open the old and new BA2 archive format to use existing or new mods, so no problem if you have updated.

If you are not updating your Fallout4.exe for compatibility reasons, you may not be able to use new published mod versions UNLESS the author painstakingly packs the BA2 archive by hand using an old tool. This will significantly affect VR enjoyers (like the old 0.95 file header).

When publishing mods, be clear WHAT version of BA2 you are publishing, example:

(a) SKKSynthVision_002_980 Update 002 using the new BA2 archive format - use this if you have updated Fallout4.exe Apr 2024 1.10.980 

(b) SKKSynthVision_002_162 Update 002 using the old BA2 archive format - use this if you are stuck on Fallout4.exe Nov 2019 1.10.162

 

UPDATE: the BSArchPro utility packed with xEdit 4.1.5f will OPEN the new BA2 format and SAVE the old BA2 format, so workflow can be: Meak new format archive in Creation Kit, drag into BSArch and save old format BA2.  

 

What is INFURIATING is that I partipcate in several bethesda developer early adopter programmes and the first I knew of this is when I published a new mod created in CK .980 on  its release day and some users reported symptoms as if the scripts were missing. Turns out they had not updated Fallout4.exe and could not open the BA2 archives. Hence the hand packing and secondary file publication. GRRRRR.

[Material Swaps Broken After Update]

Use ..\Fallout 4\Tools\Archive2\Archive2.exe which supports Unknown archive version 0x00000007

[Quest alias conditional fills ignoring conditions]

Timeframe is ~ 60 seconds between applying the exclusion keyword+moving the actor to holding cell and then finding it again.

The "finder" quests are not start game enabled and called from a controller quest script using Quest.Start() ... BUT that does not matter, they can be called [ StartQuest ] from the console with Debug.Trace in OnQuestInit() for the same repro.

The keyword is applied direct to the actor ObjectReference.AddKeyword() so it persists past transient alias membership.

Of all ~ 622 persistent ActorTypeNPC in base game and DLC the ONLY actor this affects is   [Actor < (001AC0CF)>] [ActorBase < (001AC0CD)>] 

To clear it from the debug log I am GetFormFromFile on that ObjectReference and removing it from any subsequent found RefCollections so my native scripts can silently remove all actors and quests from the world without hacking a single base game script or object and still generate ZERO debug log output. HA!

[Quest alias conditional fills ignoring conditions]

I have a problem with a quest alias conditional fill.

This is not a n00b thing, I have HUNDREDS of quest condition fills in published CK mods, its likely a corner/edge case defect.

A quest process picks actor ObjectReferences from a FormList (which makes them globally persistent), moves them to a hidden holding cell and marks them with an "ignore for future processing" keyword which works fine and reports in the Debug.Trace log:

SKK_476PrepareWorldQuestScript.PrepareCommonwealth [Actor < (001AC0CF)>] [ActorBase < (001AC0CD)>] [Cell <SKK476HoldingCell (080138BA)>] SKK_476NoDisableKeyword True

A following quest RefCollectionAlias conditional fill that looks for globally peristent actors to fill finds the expected ~600 actors, but also keeps including that specific INVULNERABLE actor EVEN THOUGH the conditional fill has specific exclusions (see picture) for GetInCell SKK476HoldingCell == 0 and HasKeyword SKK_476NoDisable == 0

Debug.Trace on the actor properties sitting happily in the RefCollectionAlias shows that the exclusion attributes are still attached: 

SKK_476ReplaceNPCQuestScript.PrepareNPC [Actor < (001AC0CF)>] [ActorBase < (001AC0CD)>] [Cell <SKK476HoldingCell (080138BA)>] SKK_476NoDisableKeyword True

How the hell is the quest conditional fill still picking the actor ? The ONLY unusual thing is that the Actorbase is INVULNERABLE which should not affect conditional  attribute evaluations. Unless it does.

[[Papyrus] WorkshopParentScript.WorkshopObjectBuilt not triggering for all built objects?]

I have used it for any object that has WorkshopObjectScript attached, so check that. 

 

[Keep Workshop Items From Being Stored]

Use condition GetWorkshopObjectCount on each of the objects to construct exclusion and inclusion recipe logic.

[Keep Workshop Items From Being Stored]

Nope if it has a construction recipe that allow it to be built or moved it can always be stored. 

My workaround is for the main object that can be constructed once (recipie condition GetWorkshopObjectCount == 0)  to detect workshop mode and swap itself out for the workshop movable proxy object that uses the same NIF, then manage that; 

 

;********************************************************************************************

Event OnLoad()

 Self.RegisterForRemoteEvent(Self.GetLinkedRef(pWorkshopItemKeyword), "OnWorkshopMode")

EndEvent

;********************************************************************************************

Event ObjectReference.OnWorkshopMode(ObjectReference akSender, bool aStart)

If(aStart == true)
    Self.Disable()
    ObjectReference MyProxy = Self.PlaceAtMe(pMyProxyObject) 
    Self.SetLinkedRef(MyProxy, None)
Else
    ObjectReference MyProxy = Self.GetLinkedRef(None)
    Self.SetLinkedRef(None, None)

    If(MyProxy != None) && (myProxy.is3dloaded() == true) ; it has not been stored 
       Self.MoveTo(MyProxy)

       MyProxy.Disable()
       MyProxy.Delete()

   EndIf

    Self.Enable()
EndIf

EndEvent

;********************************************************************************************

[Quest alias conditional fill using IsInList]

Great core info as usual.

In this case the map marker ObjectReferences are all persistent as the global finder quest can find them.

The ObjectReferences to exclude are static CK drag n drops into the form list, verified in game with Debug.Trace iteration:

SKK_TarkovQuestScript.GenerateEnableStateList 0 [Form < (0009B040)>].IsInList [FormList < (1C01477F)>]
SKK_TarkovQuestScript.GenerateEnableStateList 1 [Form < (0010196C)>].IsInList [FormList < (1C01477F)>]
SKK_TarkovQuestScript.GenerateEnableStateList 2 [ObjectReference < (0016349B)>].IsInList [FormList < (1C01477F)>]

Unfortunatley console [ IsInList ] does not seem to return >> 1.0  for any form types in my games to validate. 

Appreciate the offer but I cant use any DLL injections

[Quest alias conditional fill using IsInList]

I use a lot of quest conditional fils in object finder quests.

Using IsInList > FormList to exclude base object forms works fine e.g. MiscObject, Weapon or ActorBase forms.

If the FormList is of in game ObjectReferences, they seem to be ignored.

Question: has anyone ever successfully used Condition.IsInList with a list of ObjectReferences ?

 

The usecase: quest confitional fill finds all wordspace mapmarkers (GetIsId==Mapmarker that are enabled IsDisabed==0) fine.

But needs to exclude a static list of those that are known to have EnableStateParents.

There is no known condition or script function to dynamically detect an object has EnableStateParent.

Therefore trying to use (IsInList==ListToExclude) but they are still included in the conditional quest fill.

[Move a load door teleport marker in script ?]

Whilst the MoveTo navmesh "marker" is not script addressible, just for fun I messed around with xEdit overrides of XNDP (Navigation Door Link - Navmesh) records.

Had some unpredictable sucess/failures changing the target navmesh triangle to maintain NPC pathing and map portal targets. Oh well.

[Move a load door teleport marker in script ?]

I can get a handle to a load door ObjectReference in script and move that fine.

Unfortunatley the associated/linked yellow actor teleport marker does not move with the door object (in CK render window or in game with script), the player keeps teleporting to the original teleport marker location.

Before I waste a stack of time on this,  does anyone KNOW absolutley if it is possible or impossible to get a handle to and move a teleport marker in script ?

I was originally using activators with OnActivate scripted Moveto but the game doesnt know about that path for map marker display and npc pathing and I woudl like to have it all.

[Workshop build objects float, not recognising interior floors]

*** THE ACTUAL ANSWER: For INTERIOR CELL workshops ground collision is provided by floor tiles like CaveRmFloor512Mid01 or DCKitMudGround01, building out a layer of them at -1.0 Z below the decorative floor works perfectly.

If anyone knows the specific NIF or HAVOK collison property that makes those objects "workshop ground" let us know. ***

[What's the point of global variables?]

> I can't compare a Global to a global

Yes you can: if(myGlobalVariableA.GetValue() == myGlobalVariableB.GetValue())

> I can't compare a Global to an "int"

Yes you can: if(myGlobalVariableA.GetValue() as Int == IntVariable) OR if(myGlobalVariableA.GetValue() == (IntVariable as Float)) 

Although if your Global actually does contain a decimal you may want to use the Math.Ceiling() or Math.Floor() Int conversions.

> I can't make "int" = Global.

Yes you can: myGlobalVariableA.SetValue(IntVariable as Float)