Alright, so I decided to learn to read and post this thread on the correct forum. I'll use this thread as a general depot for my Deus Ex Nihilum coding needs. *sigh* It appears this is the beginning of a long long thread...

You could make a trigger?

It wouldn't be too hard to make a trigger that upon touch, checks it's been touched by a player, and then checks player.inhand.isA('YOURTHING') or player.carrieddecoration.isA('YOURTHING') (depending on what your thing is) and if so, maybe..sets a flag?

Or simply activates the device?

Or even have the device, when frobbed, call the trigger above, and then propagate stuff onward if the player is carrying the right stuff.

Thanks, I got the trigger working to the "decoration Y reacts to being activated with Thing X active in the player's hands" part. However, I can't see if my results have brought any progress because UCC gets stuck at "Error: Call to 'SetBool':" part.

So what is the correct way to make the code change flags? I've tried both "player.flagBase.SetBool(flagName, flagValue,, flagExpiration);" as in the FlagTrigger as well as the usual MissionScript "flags.SetBool('MS_DestroySub', True,, 15);" stuff.

Any clues?

Probably it's griping about a variable you haven't declared properly or something. Unrealscript can be so fussy sometimes...

Post the code, I'll have a look.

Yeah, that confused me even though MissionScripts don't seem to define it that properly either, even though I left out all the !flags(GETBOOL) stuff. I had something like that on at some point and it still didn't work... But anyhow, here's the trigger, to fix the issue once and for all!

Ah, just change TorsoReunited to 'TorsoReunited', in both your setbool functions.

It's a name, so needs to be between ' characters.

Names are 'like_this' : always between ' characters and can't contain spaces.
Strings are "like this" : between " characters and can contain spaces.

It's a weird unreal thing: names are special, and get entered into a nametable (for ease of lookup, presumably). There are thus things you can only do with names, not strings. Strings are just standard text. This is why if you look at missionscript.uc you see the hoops they have to jump through to generate a unique name for the missionstarted flag: compiling a string and then using the rather hacky stringtoname function in deusexplayer.

Anyway, alternatively, you could define a variable at the top (var() name flagname) and indeed one for the deco (var() class<decoration> carrieddeco) and then you'd have a trigger you could use for other purposes, rather than one hardcoded for a single task.



Now you can add that to your map and put torsoreunited, class'alistairtorso' and 70 into the new variable boxes.

>.<

Oh man, just a few apostrophes! Urgh! Thanks! I think I spent like 4 hours trying to figure that one out >_>

Thanks a lot, let's see when I'll have some new problems again :]

Hello again! Here's a new problem!

Okay, so my UnrealScript skills are just not adequate enough and I get lost in reading the DX .uc files >_> What I want to do is this: after a certain flag has been flagged 'True', a character named Yakedo would teleport to the spawnpoint named 'Yakeport'. Now, it took me a while to get the actual code to compile properly and now that it actually does compile without any warnings... well, it just doesn't work!

Here's the code



Any suggestions, fellas?

GetSpawnPoint is a shitty function that never really worked terribly well. It might work here, though, but the main problem I'm seeing is that you haven't put your mapname in caps.

Yes, seriously. God knows why, but they coded it up to require a CAPS mapname.

60_HongKong_Streets won't work.

60_HONGKONG_STREETS should work.

Hot damn. It did work! However, he also keeps on being teleported into the same location over and over again. Any clues?

Yeah, you need to add a flag that tells the MS it's successfully done it.

So

... Bah! So easy! I think I need to figure out some kind of a cheap tactic with UnrealScript, with JK I pretty much ran everything through "if thing X is in frame Y, do stuff".

Thanks a million! :]

*sigh* It appears this is the beginning of a long long thread...

Okay, so this time there's an Infolink which triggers an event named 'Launch'. The dispatcher has 3 OutEvents, the first one activates several 'ParticleGenerators', the second one's a DamageTrigger and the third one's a DataLinkTrigger.

So the first one runs properly but the DamageTrigger doesn't start, well, damaging. Of course, I'm not sure if the trigger's even supposed to be toggled like TriggerLight for instance, but the thing is that the third DataLinkTrigger won't be triggered either. Even if I take the DamageTrigger out.

I did some additional experimenting and came up with this code



So I replaced the separate DamageTrigger with a FlagTrigger and expected the timer to work properly. This time I even got the level name right! >_> But of course, the FlagTrigger worked properly but the damage didn't start (the DamageTrigger has a 4000 radius) and the final DataLinkTrigger doesn't get triggered at any point.

Maybe 'bInitiallyActive' isn't the key here but I'm all out of ideas! Seems like I've already spent over 2 hours on this stuff... but eh.

Hope you can help soon!

Damagetriggers are iffy: they do a lot of stuff on touch(), called when someone enters their radius, this stops them wastefully trying to damage things when nothing is within damage range.
Of course if you make them active when someone's ALREADY within their radius, this doesn't necessarily get called, and thus weirdness ensues. They also only damage one thing, so if two pawns walk into radius of a damage trigger, it will only hurt the last one to touch() it.

Secondly, your missionscript doesn't actually go looking for the damagetrigger at any point, which will present problems.

Thirdly, I'm not entirely sure whether it's safe to call a datalink from within a datalink, even if via a dispatcher.

Fourthly, triggering a flagtrigger from within a conversation is a little obtuse when you can simply set the flag in the convo itself. Unless we're talking a substantial delay between infolink and 'start of damage'?

So. Short of posting up a revised damage trigger (I'm not sure if I included one in the sheep's moretriggers thread, have a look?), let's do it all via missionscript since you're doing that already.



So, here we have the damagetrigger as usual, except in firstframe() we disable it. We're not actually going to use the damagetrigger code at all, because it's silly. Instead we'll use it to store various properties (damagetype, damageAmount, radius, location) that we'll then directly apply via the missionscript.

So now, as soon as the flag 'YoonDamageStarts' is set, either via infolink or flagtrigger or whatever, the missionscript looks for that GettingHurt tagged trigger, and then hurts all actors within the trigger's collisionradius. It does this once a second (since that's how often timer() is called in missionscripts) so assume your damagetrigger has an effective damageinterval of 1.

Once you set the flag 'YoonDamageDone', it will stop doing this.

Yay! I also managed to fix the DataLinkTrigger problem by utilizing the MissionScript in that situation as well... kind of funny, though. Starting from the moment when the 'YoonDamageStarts' flag was flagged 'True', the datalink just wouldn't start no matter what. I tried to see if it worked before that moment by using the 'legend' command and it did...

... oh well, at least now it works. Thanks again!

Yet I wonder how long it will actually take for me to finish this thing, considering all the problems I've only encountered in these 7 days alone! >_>