Steam 社区 :: 讨论

Shadowrun: Hong Kong - Extended Edition

Shadowrun: Hong Kong Steam Workshop

Using the Shadowrun: Hong Kong Level Editor, you can expand your Shadowrun expereince with new missions, stories, characters, and more! Share your work and your experience here on the Steam Workshop.
了解更多

主页

讨论

关于

创意工坊> Shadowrun: Hong Kong - Extended Edition> 所有讨论

Bort

拥有 Shadowrun: Hong Kong - Extended Edition

2020 年 5 月 23 日下午 1:44

Trigger Not Working

I have a trigger, set up like this:

When an item is picked up

If triggering prop has the tag 'ABC' AND variable < X

Do add 1 to variable; update screen progress bar.

But, it's not working. Only thing I can think of is that's using the item given to the player as the triggering prop, not the prop on the map itself. Is there any way of tagging a quest item, or can anyone think of another way of doing this that I've missed?

< >

正在显示第 1 - 4 条，共 4 条留言

DaveOfDeath 拥有 Shadowrun: Hong Kong - Extended Edition

2020 年 5 月 27 日下午 8:23

On item interaction?

What is the when condition you're using?

Does the item have the tag? I believe tags are case sensative...

Triggering prop likely isn't correct. Triggering target prop is more likely.

Where is variable x set? Variable <= x might catch it...

Without seeing your trigger it's tough to trouble shoot... Is it set to retain? Fire only once?

Start with just a when and an instant response trigger (like a screen shake)

Then check the variables and tags for the item...

Bort

2020 年 5 月 28 日上午 4:27

When: "When an item is picked up:"

If:
Triggering Prop has the tag "Cyberwear"
AND
SamplesCollected is less than 19

Do:
Add 1 to SamplesCollected
Set Screen Label (SamplesCollected) to display progress using SamplesCollected of 20.

Bort

2020 年 5 月 28 日上午 4:35

All of the items in question have the tag, even down to case sensitive.

Triggering Target Prop is not given as an option. I'm offered "Get Actor's Matrix Prop," "Last Created Prop," "Nearest tagged prop to actor," "Nearest tagged prop to prop," and "Triggering prop."

The variable SamplesCollected starts at 0 when the mission loads, and updates only as part of this trigger, and another set up for when the variable equals 19.

The trigger retains after firing. I've made that mistake before :)

I suppose I could have a 20 part When statement, for each object involved in the mission (When object 1 is interacted with, When object 2 is interacted with, and so on), but that seems really unwieldy, making me think it might be a bit of a memory hog.