Player ReferenceAlias

[SAC]

I'm trying to reference the player as a quest referencealias, but with specific conditions (such as isinscene == 0)

 

If I just reference it as a uniqueactor, it works fine, but it selects the player also when the player is in the middle of a dialogue, and breaks the dialogue

 

If I try to reference it as a "find matching reference", it doesn't work, meaning the referencealias doesn't get filled, even without any condition other than "getisid == player"

 

[Guest]

You cant condition the player reference this way, in an alias, with conditions other than GetIsID. Stick with Unique Actor and then put your conditions in the script that starts the quest to fill the player alias.

 

For example:

 

If PlayerRef.IsInScene() == False

     QuestToFillAlias.Stop()

     QuestToFillAlias.Start()

Endif

[SAC]

40 minutes ago, Flashy (JoeR) said:

You cant condition the player reference this way, in an alias, with conditions other than GetIsID. Stick with Unique Actor and then put your conditions in the script that starts the quest to fill the player alias.

 

Ok, thank you, I can do that

 

Got another one. How exactly does this set of conditions manage to return... a bloatfly? I mean, how do the ANDs and ORs combine/stack? Is there a way to group them?

 

This should have been read as (general conditions) AND (race in {A, B, C}), no idea how it actually gets interpreted as

 

 

[Guest]

For the first part, you are only defining sex as male, which bloatflies are (actors need to be male or female, regardless of what they are, so critters are male by default typically).

 

Conditions are funky when you arent used to them. Think about it this way.

 

GetIsRace can be HumanRace OR GetIsRace can be GhoulRace OR GetIsRace can be FeralGhoulRace OR ...

 

Do you see? You left it WIDE OPEN. Try this instead, by closing the OR loop out.

 

GetIsRace can be HumanRace OR GetIsRace can be GhoulRace OR GetIsRace can be FeralGhoulRace AND.

 

Note the use of periods (.) at the end of those conditions. One of them (the bad one) trails off with ... and the other is ., as in, point final, no other possibilities aside from what is within the race checks, as in, OR, OR, AND.

 

As you have it, the final OR is trialing and allows for anything else to be picked up, as it isnt a close to the race check loop. Whereas putting AND at the end, says, these three are the race checks AND the next condition is something different.

 

Make sense? If not, doesn't matter, lol, but do it in this way and your problem goes away.

[SAC]

8 minutes ago, Flashy (JoeR) said:

Make sense? If not, doesn't matter, lol, but do it in this way and your problem goes away.

 

Just fuck me sideways, Bethesda. They are batshit insane over there.

 

Thanks, man!

[SAC]

22 hours ago, Flashy (JoeR) said:

Make sense? If not, doesn't matter, lol, but do it in this way and your problem goes away.

 

Actually, it was probably what you've said but it was still persisting catching bloatflies even after I've AND-ed it and guess what, check out the red mark  

 

This is fun