Dragofer

You could try to find the problem by first removing everything from 'Enabling Objectives', test whether the Esc objective works at all, then one by one add back the objectives and test every time to see what makes it stop working. Wiki - Doors describes how you can manually place door handling position entities either side of the door which have spawnargs that let you disable the AI's locking behaviour. These entities need to be on ground level.

I'll take that up myself actually, thanks for offering to do this.

The special valuable item: The hint at the end of the game:

Thanks, I'm pleased to hear this. Also thanks to everyone else for the congratulations A little correction for your spoiler in answer to prjames:

@prjames: That bug looks like part of the readables text file went missing somewhere down the line. Edit: I've looked into this again: the mission archive you get from the ingame downloader is identical to the one I uploaded, and when I use the downloader's version that part is working fine for me. I really can't say what made that particular (flavour) readable misbehave, maybe the download didn't fully complete?

The fisheries have had a bad year. Unemployed roam the streets and crowd the pubs. The merchants sleep with one eye open and keep a tight grip on their property amid the unrest. A thief, even a skilled thief like myself, has a hard time finding good, worthwhile work. I began looking for more... unusual tasks. I set my eyes on Thornton Hall, remote and cut off from the outside world. These outlying manors are difficult to find, let alone reach, but they're bound to hold precious trinkets and family heirlooms untouched by anyone. Not few are said to be haunted by one dreadful apparition or another. But it's common for the lords themselves to spread these rumours, to keep unwanted visitors away. This mission is in two parts. Once youre done with the first, on to the next. Download Dropbox- river3In-game downloaderClick continue at the bottom of the login screen if you use the Dropbox link but don't have a login, then place the mission archive in the fms folder of your Dark Mod installation. Changelog, v3, December 14th, 2016: Changelog, v2.5, November 23rd, 2016: Changelog, v2, October 27th, 2016: Notes In response to a question about the relation of this mission to One Step Too Far: This mission started its life as a standalone mission for a Halloween contest, so it takes place in a different setting and begins with its own story. There is, however, a strong link thatll become apparent during the mission. From a mapping perspective it contains areas and ideas that I had originally intended for Of Brambles and Thorns, which is the bonafide sequel, but realised that they wouldn't have space there anymore. So this could be described as being neither sequel nor prequel, but certainly a part of the series that began with One Step Too Far. Solutions Part 1 Part 2 Credits - Inspiration, Story: The Terrible Old Man by H.P. Lovecraft, a short story which leaves much to the imagination. - Inspiration, Setting: Right Up There in the Mountains by Troutpack, a fan mission for Thief 2 which left its mark. - Betatesters Round 1: Abusimplea, ankai, Ryan101, Oldjim, bikerdude - Betatesters Round 2: nbohr1more, bikerdude, crowbars82, jaxa, dunedain19 - Custom voice work: AndrosTheOxen, bikerdude, Goldwell - Custom models: Atheran, epifire, Dragofer - Custom paintings: Airship Ballet - Custom AI path setup: Sotha - Custom ambient tracks: gigagooga, spady, bottle_rocket_fx, dobroide, Dragofer, augustsandberg, bosk1, 01sound - Custom sound effects: kyyrma, cgeffex, speedenza, cabro, joelaudio, robinhood76, klankbeeld, benjaminharveydesign, vate - Bikerdude for not allowing me to stray from the highest standards and perfing troublesome spots - John Atkinson Grimshaw, Ivan Aivazovsyk and William Bradford for paintings used in the briefings and loading screens

You can insert a path_waitfortrigger in the AI's path so that it'll wait for a trigger before it continues. I'd append a 1s-delay relay to the end of your 71s-delay relay for triggering the AI to guarantee that the AI knows the door is open before it starts moving. You could also do s/r Add Target, but this is more cumbersome because it ignores the 'delay' setting. You'd have to make a chain of a 71s-delay relay, a 1s-delay relay and a final relay with the s/r to get the same effect as above. Something to remember for later is that if you're using the conversation editor and want to get the AI to resume their patrols after the conversation you have to use the Add Target method, path_waitfortrigger won't work.

Thank you, Master Sotha.

Thanks, it's appreciated.

While the test reports for Down by the Riverside were rolling in I've been making progress now and again in my other map, Of Brambles and Thorns. It's a large-sized mansion, so I have no qualms with showing a larger selection of images - there's plenty more where that came from. The whole place should have something sinister to it, and the outdoor wilderness should never be far.

Could've been that Goldwell didn't plan his mission well enough and realised that the pit would be straight above the dining hall. Can't have the pit open out onto that, this isn't Dwarf Fortress after all, which puts a damper on how deep the pit can be. Always need to anticipate all kinds of scenarios when people ask questions on the forums.

Looks so far like the custom stim setup is the way to go then. All it does is that the pit entity checks every 2 seconds whether any of the AI are within a certain radius of it, if there is one then the response on the AI will be to kill _self (or if that doesn't work, just directly fail the mission by triggering a set_objective_state entity). Pit entity: - Custom stims tab: create new custom stim - Stims tab: apply the custom stim to the pit entity. Radius i.e. 200 units, time interval 2000ms. AI entities: - Response tab: apply the custom stim, right-click add response effect 'kill' '_SELF'. - Copy-paste the s/r spawnargs from this AI to all the others.

It's not TFix, NewDark is a major unofficial patch that improves Thief 1 & 2's engine. NewDark patch for Thief and Thief 2 on ttlg.com has various ways of downloading and installing NewDark.

I'll add my own observation that when testing my spherelamps I noticed that they'd badly illuminate the brush wall they're attached to, while the other wall in the corner was much better illuminated. If I remember right the stock lanterns behaved in a similar way. I had to put the light origin as far out in the bulbs as possible to reduce this.

Probably more straightforward would be to copy the damage stim setup from Inn Business' furnace, with 'magnitude' turned up to a very high level.

The downside to that is that it takes a while before they die, so the player might walk away from the pit after having done the deed thinking it was fine, then 20s later the mission fails. But I do agree with the concept, that the most efficient solution would be some kind of kill surface. Unconscious ragdolls are still alive and can be killed by normal means (had to test this recently), so this shouldn't be a problem; they also continue using the name of the AI. Though I don't know for sure whether they keep the stim/response settings of the AI.

That looks like you've got the filter for decals activated. Does the same happen if you use i.e. a wood board texture?

One way of doing it would be to setup a custom stim on an entity in the pit, the bounds of the stim defined to be a box that fills the pit, and put responses on the AIs to kill _SELF. If you have a lot of AIs you can speed up the application process by setting up one AI, then copy-pasting the spawnargs when you have all AIs selected. The stim on the pit entity could fire every 2s to keep the load low. And to see how to define a box-shaped stim, take a look at the damage stim on the cellar furnace in Inn Business. Edit: it can just be a simple radius if the pit bottom is separate from other parts of the map, no need then to carefully define a box.

That's not what happened at my end, patches showed up where expected (selected surface, then went to brush -> create decal patches). I'm using greebo's 2.0.5 beta DarkRadiant version. The way I normally create decals is to select the brush, change orthoview so that I'm looking directly at the intended surface, then Patch -> Create Simple Patch Mesh, untick Remove Selected Brush. The popup window lets you choose how many rows and columns of vertices you want to have in the patch.

That sounds great, it'll be interesting to see the thread with your map and schematics you mentioned and the replies it gets.

Terrain can be done with patches. You start with a flat sheet and move the vertices on it around so you can get things like curves, slopes, bumps - it works quite well for streets. I think this is done in the A-Z tutorial. About your changes: - ambient light can be changed dynamically, this is described in the location settings wiki page iirc. - fog can be added by making the fog light inactive at mapstart and then activating it via a trigger (doesn't need scripts) - skybox can be changed by triggering the skybox entity of the appropriate skybox - objects can be removed by targetting them with a func_remove and then triggering that - corpses can be brought in by targeting them with an atdm teleport entity and then triggering that, but it'd be a little tricky because they'd have to fall correctly into place The editor is quite user friendly and has provisions for all kinds of effects without requiring the mapper to be able to script. Usually you can just search the entity list to find one that performs your desired effect. My laptop isn't the fastest either so I've gotten into some habits: - use layers to hide all the areas that you aren't working on. You could go as far as using one layer for each floor of a house so that it becomes like The Sims, quite easy to furnish the rooms then. - there are also filters which hide things you don't need to see all the time like collision meshes, shadow meshes, visportals, nodraw, caulk etc. And if you want to make changes to things like doors, AIs etc. you can hide func_statics as well which is a major fps boost and makes it much easier to see the important things. Maybe you'd have a good chance if you asked whether someone wants to work on a campaign with you, so both contribute maps which get linked up by the story you work out together.

This isn't something I'd be so concerned about, it really is something that you get much better at with time. Here's a motivational story: This is how I started mapping in 2010, a small mansion out in the tundra. The brushwork was as basic as it gets and it would never have occurred to me to put in wainscoting (trim) on the walls, decal patches, particles and such things. Also, my technical work wasn't very good because I liked to use tiny grid sizes to add detail to brushes, which led to that graphical glitch you see. Then I took a break from mapping because it felt like I was getting nowhere and returned in 2014, spent 1.5 months to create my first map One Step Too Far and basically learn the editor, did another few months of mapping afterwards on the sequel, Of Brambles and Thorns, and made this screenshot at the time, which looks more like a real mission: So if your mapping looks basic at the moment and has things in common with my first screenshot, best just keep at it and let your growing experience do its work for you. And something I should add is that, in my experience, people across the Thief and TDM community have always put more value on the story and gameplay than the visuals - that's why Thief 1 & 2 are still as popular as ever with us. So a first map with interesting sneaking puzzles and an imaginative story, which I think is what you have in mind, will be sure to be appreciated.

crowbars did a fine job in testing, in fact I was reminded of Oldjim What I'd add to that list would also be subjective aspects such as difficulty, how well the story flows and such. Betatesters are the first people to see the map besides the mapper, so opinions from their fresh perspectives would also do well for the development of the mission.

The last version's going up later today, then it needs the blessing of the beta testers. (I suspect there's a handful bugs left)