joebarnin

Really, really, really looking forward to this!

Perhaps this is simply a matter of how we define "closet". The six items in the dining room, I would call them "cabinets". To me, a closet is a small room for storage, either just shelves, or walk-in. The room in question is 9x9 feet, perhaps a bit large for a closet. I'll change the hint to say "small room", to be clear.

I’m glad you persevered! Sorry about the frustration; it seems like this mission has something to piss off everyone

Thanks for the subtitles. I'll add them to the mission, along with fixes for the issues you found. I usually like to have the map be vague, but I am sorry that it misled you about that street. I guess I should make it more clear when areas are unreachable. That's a charitable way of looking at it.

So close on the loot! Thanks for playing.

For the song thing (clever idea, btw), I have no idea if there is anything built in to do this; I doubt it. You might have to implement something along the lines of this: https://wiki.thedarkmod.com/index.php?title=Ambient_Sounds_-_Zone_(using_triggers). It would have to be smart enough to start both songs at the same time, but have one of them start at zero. Then when you transitioned, it would fade the volumes up/down as appropriate.

By Any Other Name

Unfortunately I’m out of town for the next week but I’ll take a look when I get back.

Yeah I think that the /script folder is the way to go here. Create my_campaign.script in the /script folder and add it to tdm_custom_scripts.script (i.e., #include "script/my_campaign.script"). And if your script needs to know which campaign mission is being played, don't forgot https://wiki.thedarkmod.com/index.php?title=Setting_up_Campaigns#Scripting.

Excellent, that works great! void testDeathScript(entity ele) { tdm_ai_elemental elemental = ele; elemental.onDeath(); }

I've got an atdm:ai_elemental, and I want to augment its death behavior. So I implemented a script and set the "death_script" spawnarg to "testDeathScript". Works fine, my death script gets called. But, this bypasses the base death script functionality, which I want to have happen as well. Is there a way to call the base function that I've overridden? I tried a few ways. Among others, I tried: void testDeathScript(entity ele) { ele.onDeath(); } results in ERROR:Error: file maps\rock.script, line 81: Unknown value "onDeath" void testDeathScript(entity ele) { atdm:ai_elemental elemental = ele; ele.onDeath(); } results in ERROR:Error: file maps\rock.script, line 81: Unknown value "atdm" I worked around it by copying the content of the onDeath script into my script. That functions correctly, but it seems like perhaps not the best programming practice. Is there a way to call the 'base' function in this case?

Great phrase!

It was happening in one of my missions. I worked around it by adjusting the position of the ai, the chair he was sitting in, and the table he was near, until it didn’t happen anymore. But, since it was an intermittent problem, I was never sure that I actually eliminated the issue. It just never happened again in my testing.

Sign me up!

I have a trigger_multiple, and I want to be notified whenever the player is within it. The trigger_multiple targets an atdm:target_callscriptfunction. I also set wait=1 on the trigger. When the player is within the trigger area, the script gets called once a second. This happens if the player is moving or stationary. So everything is working great. I also want to be notified if any other AI is within the trigger area. So I added the anyTouch=1 spawnarg. Now, when a guard walks into the trigger, the script function gets called. As long as he's moving, it gets called (once a second). But as soon as he stops, the script is no longer called (I assume becase the trigger is no longer firing). This is true if he is just standing there, or is stationary because of a path_wait. Summary: a trigger_multiple will fire each time the player is within the trigger. But a trigger_multiple with anyTouch=1 will only fire for other AIs if the AI is moving. If the AI is stationary, the trigger no longer fires. Intentional, or bug?

I think you want to use a func_rotating. Not sure how. Check out @JackFarmer's 'Hidden Hands: The Lost Citadel' mission - there are objects that rotate when you push a button.

I haven't tried this myself yet, but I found some script code in another project that fades a light from one color to another: // Transition vector delta = col2 - col; float starttime = sys.getTime(); float endtime = starttime + fadeSeconds; float nowtime = sys.getTime(); while ( nowtime < endtime ) { float frac = ( nowtime - starttime ) / fadeSeconds; theLight.setLightParm(0, col_x + (frac * delta_x) ); theLight.setLightParm(1, col_y + (frac * delta_y) ); theLight.setLightParm(2, col_z + (frac * delta_z) ); sys.waitFrame(); nowtime = sys.getTime(); } // Finalize colour theLight.setLightParm(0, col2_x ); theLight.setLightParm(1, col2_y ); theLight.setLightParm(2, col2_z ); 'col2' is the new color, 'col1' is the old one. 'fadeSeconds' is how fast to fade. Give this a try?

func_pendulum IIRC (I don’t have my computer in front of me). Set it up and bind the visible object to it. There’s one in my mission Now and Then

There's such a fine line between a good deed and bad deed...

I was going to say 'no', but I decided to hunt around on some old backup disks, and lo and behold, I found the original mission (the beta, not the additional changes). I opened it up in DR, and man is it ugly. Simple, plain, nothing clever or interesting. I can see why the beta testers wanted changes. I'm glad I threw it away and started over.

Hmm. Just tried it again, and it all works fine. Maybe one of my keyboard keys was stuck or something. Or maybe I was dreaming. Anyway, all is well now. Sorry for the false alarm.

I like this feature - especially because it allows you to select and manipulate objects that are in a group, something I just complained about a few days ago. Good timing! I played around with it for a few minutes, didn't see any issues. However, I did notice something in this version of DR. The Camera view does not behave as expected. Examples: In Camera view, the ESC key no longer deselects. In ortho views, ESC deselects fine, but in the Camera window, it doesn't do a thing. Undo doesn't seem to redraw in the camera window either. Selecting an object in ortho view doesn't highlight it in the camera window. Are these known issues?

I'll definitely investigate and see what's up - those fireballs are heavily customized. Thanks for identifying the problem.

@MirceaKitsuneI installed the latest dev version of TDM, and this problem happens for me too. So it is definitely related to that. I'll take a look at it, but I think your best bet is to restart the mission with the 2.10 release - that's the only release it's 'certified' on.