Search the Community

I've added new royalty-free music to my main post.

Welcome to the forums Ansome! And congrats on making it to beta phase!

Looks great, thank you! That looks even better: It's where DeusEx had its player status screen, feels even more like TDM with DX characteristics now I think I placed it above the light gem as that's where player info was technically being stored, with the new subtitles covering that position the move is a great decision. By the way: If anyone wishes to continue and improve this mod, I'd appreciate seeing your remixes of it. I had it mostly finished last time on my end; I think the main issue was upgrades require items to be placed on maps, augmentations may not work on every FM without a way for them to automatically spawn in random places... my imagined solution was to also offer upgrades based on loot gathered or other achievements but I never got around to adding that.

Of course not AFAIK you can't have multiple values for a key, it would just overwrite the last value if you tried adding a new one.

New version is up. Here's what's new: A high quality version of the intro video Subtitles made by datiswous Kingsals new footstep sounds (from his excellent Volta missions) are included (with his permission) Background image and ambience (music by Gigagooga) in the main menu The climbable vines were made more noticeable Removed the absence markers from all the loot. Guards wont be seemingly randomly alerted anymore Better textures in a few selected places Some model updates/improvements made by Bikerdude 3 new hidden loot items A lot of unnecessary files where removed from the package A lot of smaller fixes

(I apologize for the odd poll question layout. I wasn't able to add five yes-no questions, because polls are limited to three questions.) Hi everyone, I've recently been working on some patches for issues that I've read about from players on the TDM and TTLG forums — and Discord. My goal is to make it as easy as possible for players, especially new players and those who need usability/accessibility options, to find what they need in order to have a better TDM experience. I've already written the GUI and game engine code for these settings, which I've been using in my personal build. The reason for this poll and discussion is to both guide the finalization of my work and collect data to help inform the dev team. Which patches I submit depend on the outcome of this poll, discussion, and what the dev team agrees to accept. Once decided, I can coordinate with the dev team. I've attached screenshots of what the new settings menu would look like if all of the settings are accepted. Below, I have detailed each menu setting, so you can have an easier time understanding each one. Very important to keep in mind: None of these settings change TDM default behavior. They are all opt-in. If you are already happy with the behavior of 2.10, 2.11, etc. and these menu settings are accepted, nothing will change for you. Rename "Always Run" to "Run Mode" with options "None, Always, Toggle" After 2.11 was released, @i30817 requested that "toggle run" be added to the settings menu. Its cvar is already in TDM as "in_toggleRun" (same as Doom 3). I propose renaming the "Always Run" setting to "Run Mode" with options: "None", "Always", and "Toggle". None = in_alwaysRun 0; in_toggleRun 0 Always = in_alwaysRun 1; in_toggleRun 0 Toggle = in_alwaysRun 0; in_toggleRun 1 Show Blackjack Helper @Wellingtoncrab suggested that the new blackjack helper be added to the settings menu. Its cvar was added to 2.11 as "tdm_blackjack_indicate". More info: It's the new blackjack helper added to 2.11. When the game detects that the blackjack can be used for a successful hit or KO, the blackjack will rise slightly. I propose a "Yes/No" setting for this. Slider for "View: Head Bob" @ChronA requested a way to disable head bobbing, because a viewer watching him play was having severe motion sickness. Also, there was a bug in TDM that made setting the head bob in the console not stick after loading a saved game. (Even with 2.11, if a mission overrides the "tdm_player_thief.def" file and sets "pm_bobroll", "pm_bobpitch", "pm_bobup", and other cvars, it will override player preferences.) As far back as 2008, players have had trouble setting head bob. Another one from 2018. At the end of 2022, @Shadowex3 registered just to voice the need for a way to control head bob. I propose that a slider be added to adjust the amount of head bob. This would use a new "pm_headbob_mod" cvar with a value between 0.0 and 1.0 (default 1.0, no change). The "pm_headbob_mod" would be a multiplier for "pm_bobroll", "pm_bobpitch", and "pm_bobup". The advantage to this approach is that missions like Volta 2 and Hazard Pay would not need to adjust their "tdm_player_thief.def" files for head bob to work properly. And, the player can still adjust "pm_bobroll", "pm_bobpitch", and "pm_bobup" as they like. Slider for "View: Mantle Roll" This is similar to head bob for those who are sensitive to motion. Its cvar was added to 2.11 as "pm_mantle_roll_mod". A Thief player on Discord said, "2.11 will have a cvar to tune down the mantling animation at last." I propose that a slider be added for "pm_mantle_roll_mod". Auto-Search Bodies @Zaratul requested the "auto-search bodies" feature from Thief 1 & 2. Its cvar was added to 2.12 dev16783-10307 as "tdm_autosearch_bodies". I did a poll on the a Thief Discord server and roughly 20% of players there use the Thief auto-search bodies feature. I propose a menu setting for this, so that players coming from Thief 1 & 2 can easily find it.

In the latest build dev16256-9358, the code for holding objects and dragging unconscious bodies has been changed. It is possible to switch between the old and the new code (e.g. to compare them) using cvar: "tdm_drag_new 1": use new code (the new default). "tdm_drag_new 0": use old code (was the only option in TDM 2.09 and before). With the new code, there are three modes of dragging/moving objects: Moving items (candles, apples, crates, etc.) around in normal/"messy" mode. Moving items around in "silent" mode. Dragging bodies (ragdolls = articulated figures). The long-standing problem with moving items was that it was very hard to stay silent. An object could instantaneously reach high velocities from minor mouse movements, colliding with surrounding objects, sending them to fly all over the room and produce noise. Regular noise from bumping into the table/wall when you push an object into it was also a problem. As the result, grabbing something from a table was risky and required a lot of concentration. The new code keeps item velocity bounded, so even if it collides something, it should not cause too much chaos. Also, if you push an item into floor/table, it won't cause continuous noise anymore. The silent mode is the radical solution to the noise problem. When you move object in silent mode, it does not produce any noise and does not push surrounding objects at all. So you can be sure you won't attract nearby guards and won't topple nearby candle. However, there is a cost too: if the manipulated item is blocked by something, you won't be able to move it. For example, if a crate has a candle on it, you won't be able to move crate vertically unless you remove the candle. So while this mode can be very convenient, it is not intuitive. We have not come to conclusion about usefulness of the silent mode yet, so there is a cvar which controls when silent mode is enabled: "tdm_drag2_rigid_silentmode 0": never use silent mode. "tdm_drag2_rigid_silentmode 1": use silent mode if creep button is pressed. "tdm_drag2_rigid_silentmode 2": use silent mode when run button is not pressed. "tdm_drag2_rigid_silentmode 3": always use silent mode. Feedback is welcome As for dragging bodies, this is an entirely different mode. The new code should make it a bit smoother and more natural. For example, if you try to push a body into a wall/floor, you will see horrible convulsions with the old code. The new code does not have this problem. Another issue happens when you try to lift the body up. With the old code, it feels as if the body is stickied to the floor with magnets. The new code is more physics-based, and you won't have problem with lifting torso, head, and arms off the floor, although you will never have enough force to lift whole body and keep it in air.

The devs didn't title this thread, and @datiswous said they're attempting to mislead people by using Russell's name and a retro style to make it resemble Thief, which is cynical. I grew up on forums like I'm sure anyone who likes a game from '98 did. I actually left the Discord immediately after joining it because it was more off-topic doom-posting than anything relevant to the mod. I thought the forums might be better, but it's mostly just grown men yelling at clouds and telling strangers how mature they are, and a few brave souls actually developing anything. Depressing place, I'll just stick to enjoying new missions every 6 months without an account.

I've also added new links to royalty-free music in my other external music database thread. I've covered the historical music fairly in-depth, but the royalty-free tracks were lacking in numbers, so I searched around for some interesting ones. There's more to come in that other thread in particular.

With TDM 2.12, after the credits finished, the "Mission Complete" screen did not display. I found that the screen was black and I could hear my footsteps when I tried to move around. I think the reason for the mission not completing successfully was that the "Do not kill or harm allies" objective was never marked as "1 = STATE_COMPLETE" instead it was left as "0 = STATE_INCOMPLETE". Note, I didn't use noclip throughout the mission. Same as: https://forums.thedarkmod.com/index.php?/topic/18054-fan-mission-the-accountant-2-new-in-town-by-goldwell-20160509/&do=findComment&comment=458491

Our friend Skacky ( and his team "Feuillade Industries" ) has released a full sized Thief expansion \ campaign "The Black Parade": https://www.moddb.com/mods/thief-the-black-parade t is finally here! After 7-ish years of development, The Black Parade is finally released. So, what awaits you in this campaign? - 10 huge, open-ended and meticulously crafted missions with varied themes packed with content. - A brand new protagonist thrown into a dark, intricately woven story of crime and conspiracies. - 4 new tools happily supplied by the undermarket, at a price. - Many tweaks to the AI to make the game a bit more challenging but still fair. - A brand new "banter" system where AIs greet each other during their rounds and nightly life. - 28 voiced characters totaling roughly 1,800 new lines of dialogue. - 30 minutes of gorgeous hand-drawn briefings and cutscenes. - Brand new AI motions making the denizens of The City look more alive. - Full English subtitles. In The Black Parade you play the character of Hume, a hardened criminal who was sent into exile as a punishment for his crimes. The year is 833, you are now back in The City, a sprawling metropolis of soot-caked brick, greasy fumes and noisy machinery, with many a sinister conspiracy whispered behind closed doors. Lost and without a penny to your name, you are back to your life of thievery and must find your old associate Dahlquist. Shadows and silence are your allies. Light is your enemy. Stealth and cunning are your tools. And the riches of others are yours for the taking. The Black Parade aims at being a love letter to Thief: The Dark Project, and we hope we succeeded! It is recommended to have played through Thief: The Dark Project and/or Thief 2: The Metal Age at least once beforehand, since these missions are overall tougher than the base game. The Black Parade also comes with a few tweaks to the classic Thief gameplay formula: - Hume is not a Keeper and thus never received Garrett’s training: AIs will now notice you if they bump into you or vice versa, sometimes even in a perfect shadow. Be careful! - Hume can move banners aside instead of having to slash them. - Hume has additional footstep sounds for chains and pipes; these are metal sounds that aren’t as noisy as regular metal (about as noisy as stone/wood). - Water arrows can now be used to expand moss patches. - Servants will re-light extinguished torches on higher difficulty levels. - Servants may clean moss on the floor if they notice it on higher difficulty levels. - Zombies now smash wooden doors open instead of simply opening them. - Electric lanterns carried by guards can be turned off. - A few guards in the campaign are outfitted with heavy armor and helms so they cannot be knocked out using the Blackjack. - Hume can pick up small creature corpses such as spiders or sweels. DOWNLOAD (912 MB) MIRROR 1 MIRROR 2 Here is a very handy guide by nicked on how to set up Thief Gold for Fan Missions. !!!IMPORTANT NOTES!!! The Black Parade requires NewDark 1.26 or above! Make sure you use the latest version of TFix/TFix Lite before playing! The Black Parade should be launched with FMSel, NewDarkLoader or AngelLoader. It is not recommended to launch this campaign with DarkLoader or GarrettLoader. Note that mods such as Thief Gold HD Mod, NecroAge or Enhancement Pack are not compatible with this campaign. Remember that this is a campaign for THIEF GOLD, not Thief 2! Known issues: - Due to the complexity of the missions, there can be cases where some NPCs might get stuck walking against walls. There is unfortunately not much that can be done about this. Happy 25th anniversary to Thief: The Dark Project, and have fun taffers!

This thread is for discussion and feedback on the xray feature, which has been developed further for 2.10 and is now considered feature rich enough to be publicised and wikified with X-Rays and X-Rays in GUIs. See below for the main wiki article's introductory section: As well as some screenshots from the demonstration map found in the main wiki article: (Note that various assets mentioned in the article are currently only available in the demo map and will become part of the second 2.10 beta build).

This pinned thread's purpose is to collect links to all the discussion threads for new features in 2.10 so that they no longer all need to be pinned. [2.10] Beta testing new main menu GUI [2.10] Volumetric lights [2.10] X-Rays [2.10] Dmap locations diagnostics [2.10] Dmap optimizations [2.10] Entity limit removed [2.10] Subtitles TDM security cameras

It was a weird mission, that's for sure. And you put a lot of original ideas into it. I appreciate that. The machines were very convincing. I don't know if you made them or if they're part of the new edition, but they are excellent quality. The game needs dirty water texture for its canals. And dirty building blocks. It's very cool that the doors consume the keys. The floor textures look strange on walls and ceilings. It took me a little bit more than 9 hours to finish it.

I plan to gradually try out all or most of the different path node types and adjust them depending on the interaction. Though I don't plan to use it in this particular mission, I have a keen interest in the follow type, as I'll want an NPC to follow the player character in another, future FM I'd like to create. Never too soon to try out various functions while I'm already learning new FM-building skins after a long hiatus. Thank you for the suggestion. I completely forgot about the location system ambients as an option ! A few years back, when I was testing various stuff in DR, I did actually use that approach instead, once or twice. I haven't used DR much in recent years, so I eventually forgot about setting it up that way. Acknowledged, and I'll look into it. It'll save a lot of time concerning the audio side of the mission. My first few missions won't have much a natural environment, they'll largelly be small and focused on buildings or urban spaces, so I won't need to bother with detailed audio for rivers yet. I have an outdoor FM planned for later (it's in the pre-production phase), and I'll have a good reason to study it in greater detail. It's actually okay, I don't reallt need rectangular speakers. Given that I've been reminded I can set a main ambience for each room - something I did know before, but forgot, after not working properly with DR these past few years - I'll do just that, and use the speakers for more secondary ambience concerns. Handy indeed. A rectangular shape would be easier to remember. I'll just use the filters in the editor to put away the speakers if I ever the get the impression they're blocking my view. Also, I don't actually mind the shape all that much. As you and the others say, the size/radius of the speaker is the actual key aspect. I'm a bit disappointed it's seemingly not possible to resize speakers the same way you can resize brushes or certain models, though you can still tweak the radius numerically, manually. As long as I can work with that, the actual shape of a speaker isn't really important. My main concern is expanding the minimum and maximum radius areas to an extent where they'll be audible for most for all of the respective areas the player will visit, rather than fading away quickly once the player leaves the hub of the speaker behind. As was already said above, I'll use the different utility to set the main ambient for the individual rooms, rather than a manually placed speaker, and I'll reserve the speakers for additional sound effects or more local ambience. I've already added some extra parameters to the speakers I'm testing out in my FM, so I'll take a look at those soon, though I'll deal with the main room ambience settings first. I'd like to thank everyone for their replies. While I'm not surprised by the answers, I'm now more confident in working with the path node and speaker entities. On an unrelated sidenote to all of this, the same in-development FM where I'm testing the speaker placement and range was tested yesterday for whether an NPC AI can walk from the ground floor all the way to the topmost floor, without issues. Thankfully, there have been no issues at all, and the test subject - a female mage, whom I won't use in the completed FM, sadly - did a successful first ascent of the tower-like building that'll serve as the main setting. (That's all your getting from me for now, concerning the FM contents.)

I agree that "New XY View" isn't a great description, since the 2D view is not necessarily oriented in the XY plane. Other candidates would be "New 2D view" or "New ortho view".

In that case I could indeed use a pk4 with the name Unofficial_Patch. If the last one wins this or Wesp5 should be good :)! P.S.: I have released a new update where all loose files are in tdmup.pk4 now. Also I included nbohr1more's new torches...

Yes, I considered this idea. But it won't help much, I believe. If several mirrors are allowed, you can split your surface into individual planar polygons and hope for the best. But if you have 10+ polygons, then I suppose the best won't happen Internally, the material has "mirrorRenderMap" keyword which triggers rendering of subview. This subview is than copied into a texture. In the main view, the surfaces with mirror material should be rendered as any other surfaces, it can just use this dynamically generated surface. I'm not sure what exactly you want. If you want the mirrored view to be distorted by normal map, then yes: this is definitely not supported. The reflected texture is generated as if reflected by a perfect plane. Maybe we can add some kind of warp shader that deforms the image mathematically according to the normalmap, but this would be a new feature.

Included in the beta for 2.12 is a new companion to security cameras familiar to Thief players: the automatic turret. It will become active as soon as an enemy is detected by a targeted security camera, firing projectiles to fend off the intruder. Similarly to the security camera and the camgoyle sentry, turrets are highly customisable in their behaviour and appearance. There are two main variants of turrets at the moment: the cannon and the flamethrower. Thanks to Goldwell for digging up custom sound effects and Bikerdude for creating the models. Both were originally written as scripts, and meanwhile the cannon has been converted to C++ and integrated into the core assets for 2.12-beta1. One of the aims of the 2.12 beta is to test the readiness of the turret for release, given that it's a brand new and complex entity. The question of whether it's released with 2.12 or pushed back 2.13 is decided based on feedback by testers, so plentiful testing is of the essence and can be posted here. At the time of the 2.12 beta, the flamethrower is available as a script-based downloadable addon [here]. Its mode of action is to fire a lance of fire at its target, a novelty in TDM. While the scripting engine is powerful, there are some significant potential benefits in a C++ version. The main one is access to array variables to store and process data about all emitted flames, which would allow the flamethrower to spray fire in an arc instead of firing a single stream at x position. For this reason the flamethrower isn't offered as a core asset yet. Another feature of 2.12 is the refurbishment of Doom-era code for guided projectiles, tricky for even the nimblest players to dodge. Switching to guided projectiles only requires changing a projectile's spawnclass from idProjectile to idGuidedProjectile, and more spawnargs can be found in the new entity base class for guided projectiles. A guided version of the cannon turret's projectile is available in 2.12-beta1. Work was also done on introducing Thief-style bouncing projectiles but, as a hybrid between projectiles and moveables, these aren't part of 2.12 because changes to existing code at a deeper level are needed.

Yeah, it loads about 80 percent there and crashes. Its hard to diagnose because I havent touched the mission in a while and afaik, I havent added anything new to it in a while. This might just be the first time Ive noticed the crash and its just been hiding in the mission.

I did play Thief and FMs, but I don't play it any more, except for major things like Black Parade. The clunky movement and antiquated Dromed editor is what discouraged me from interacting with it over the years. I regularly play and sometimes make content for TDM, because it has much better movement model than Thief. I know that most missions don't use it well, but if you construct your geometry (gaps, ledges, distances) using power of two measurements, movement and mantling feels fast and snappy. There's no need for regression in that regard, in my opinion, there's a need for assets and missions made with the movement model in mind, to showcase its strengths properly. Even if TDM originally intended to "simulate the stealth gameplay of Thief, many things will be familiar to veteran Thief players" the actual mod history was a bit different. The team came up with a mission platform that has its own identity when it comes to mechanics. The way assets were made might have been a huge mistake, but that didn't prevent the platform from growing. Since you like anecdotal evidence, noone other Skacky once said that TDM movement model was super clunky, after playing The Painter's Wife. It was really hard to convince him that if a mapper places geometry this poorly, and isn't aware what spatial measurements play to the strengths of a movement model, no movement model will save his mission. And there is no fixing of this problem on the engine side, although it's not the first time when TDM team tries to address the asset problem with engine changes, which I suspect will ultimately lead to even more problems down the line. In game development, things like core mechanics and player tools are locked-down first, in one of the pre-production phases, because all the levels will be constructed around them. Making changes in core mechanics in a project this mature is very risky, I assume you don't plan on going through all playable spaces in all released TDM FMs to check for errors. Instead of making incremental changes in fundamental mechanics, I'd encourage you to create a fork, or some kind of major version bump candidate, like 3.0, where all things could be revamped: movement, player tools, UI, new frob mechanics, perhaps with UI contextual icons, new training map to incorporate all that, etc. Once all new elements fall into place and create something new, with a map or maps to back it up as relevant changes, it will be easier to convince existing player/author base that it was worth it. I assume the existing fanbase is already fragmented, as a result of all those heated discussions around the topic. But with multiple versions available for download, the transition to hypothetical "TDM 3.0" should be easier. It could be similar to UE2 and UE3, and you could also use this as an occasion to draw the line for backwards compatibility. I know there are old systems and variables kept in place just in order not to break existing missions. This way you could e.g. redo the LOD system, implement lights using math functions instead of textures, etc.

As my custom assets work has increasingly shifted from models towards scripting, I'll open a new thread here to contain any scripts that I write which can be reused in other missions, starting with the A ) Presence Lamp This is a Lost City-style lamp that brightens and dims depending on the presence of the player or an AI. It fades between 2 colours and can trigger its targets whenever it switches fully on or off, so it should also be viable in various other situations. The standard setup consists of the following: - a trigger_multiple brush. The spawnarg "anyTouch" controls whether AIs, too, are able to activate it - a presence lamp, highly recommended with a colorme skin - one presence light, or any other light with appropriate spawnargs The targeting chain is trigger brush -> lamp -> light When the player or an AI stands in the trigger_multiple brush, the lamp switches on and starts a short timer. Subsequent triggers reset the timer. If the timer runs out because no one's standing in the trigger brush anymore, the lamp switches itself off. Notes - Multiple trigger brushes can target the same lamp, and one trigger brush can target multiple lamps. However, each presence lamp can only target one light, so if you want i.e. a bouncelight you'll need to hide an additional silent presence lamp somewhere and target it from the same trigger brush. - The lamp and the light use their own colour spawnargs respectively, since setting 0 0 0 on a lamp would make it appear pitch black. - Technically the trigger brush can be exchanged for anything else that triggers the lamp every 0.5s (this number can be changed via "update_interval" on the lamp), i.e. a trigger_timer. - This was originally named the proximity lamp and was one of many scripting jobs for The Painter's Wife. I've renamed it to "presence lamp" because the mapper may place the trigger brush(es) wherever he wishes: proximity to the lamp is not a factor. Credits go to Bikerdude for putting together the crystal lamp models. Download Presence Lamps - Google Drive Place or extract the .pk4 into your FM archive, then look up the presence lamp prefabs. If you already are using other custom scripts, remember to add the presence lamp's .script to your tdm_custom_scripts file. B ) Teledoor This is a Skyrim-style door which opens just a bit into a black_matt "void" before teleporting the player to a different area of the map, which may represent the other side of the door. This is used for connecting physically separated map areas with each other, such as when there's an exterior/interior split of a building or ship to allow for more mapping freedom. [Full Thread] C ) Mass Teleport This is a teleportation setup designed to seamlessly teleport the player and any moveables between two identical-looking areas. This allows the mapper to link 2 physically distant areas with each other while maintaining the illusion that they're connected. The teleportation zones should be free of AIs as they can't be teleported like this. [Post] D ) Automaton Station A station for Sotha's automatons (includes the automatons) which can be switched on and off by patrolling automatons. (Part of core assets as of 2.10) [Post] E ) Camgoyle A sentient turret originally made for the FM Written in Stone. It's based on the new security camera entity and augmented with scripting to allow it to fire magical projectiles at the enemies it detects. People are more than welcome to use it and to convert it into something else, such as a mechanical turret. [Post] [Download] F ) Audiograph The audiograph is an Inventor's Guild device for playing back recordings stored on spindles, which are small metal cylinders the player can pick up and store in his inventory. [Post] G ) Turret A new companion to security cameras familiar to Thief players. It will become active as soon as an enemy is detected by a targeted security camera, firing projectiles to fend off the intruders. Similar to the security camera and the camgoyle sentry, turrets are highly customisable in their behaviour and appearance. [Thread] G ) Fog Fade Dynamically change fog density depending on what location the player is in. [Thread]

It's enabled by default in 2.12. Most players will keep it, I guess. On second thought I think we better not. The text on frob servers three purposes: Get to know the name of AI (if any) without the need of shouldering. Get to know the status (KO/Dead) of AI without the need of shouldering. Get to know if something is in the grabber, but this is minor, and it could only be considered a feature if all objects had a proper name. The player triggers the text with his/her actions. If we do it on highlight then it is us who is triggering it, and the player may or may not want it displayed at that moment. Back on topic, Yeah, this is something I noticed too. I like this idea very much. I think it could work. Also, a new arg for mappers: on_death_tongue_out.