Search the Community

New script for mappers: my flavour of a fog density fading script. To add this to your FM, add the line "thread FogIntensityLoop();" to your map's void main() function (see the example in fogfade.script) and set "fog_fade" "1" on each foglight to enable script control of it. Set "fog_intensity_multiplier" on each info_location entity to change how thick the fog is in that location (practically speaking it's a multiplier for visibility distance). Lastly, "fog_fade_speed" on each foglight determines how quickly it will change its density. The speed scales with the current value of shaderParm3, using shaderParm3 = 1000 as a baseline. So i.e. if shaderParm is currently at 1/10th of 1000, then fade speed will be 1/10th as fast. Differences to Obsttorte's script: https://forums.thedarkmod.com/index.php?/topic/14394-apples-and-peaches-obsttortes-mapping-and-scripting-thread/&do=findComment&comment=310436 my script uses fog lights you created, rather than creating one for you. Obsttorte's script will delete the foglight if entering a fogfree zone and recreate it later more than one fog light can be controlled (however, no per-fog-light level of control) adding this to the map requires adding a line to your void main() script, rather than adding an info_locations_settings entity with a custom scriptobject spawnarg in my script, mappers set a multiplier of fog visibility distance (shaderParm3), while in Obsttorte's script a "fog_density" spawnarg is used as an alternative to shaderParm3 smaller and less compactly written script fogfade.scriptfogfade.map

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]

Surrounded by greedy noblemen and treacherous siblings, Lady Kamila Leicester gets more than she bargains for after acquiring an ancient tome and performing the dark rituals within. Bikerdude, Wellingtoncrab, Dragofer, and I proudly present Grayman’s FM “Seeking Lady Leicester.” Notes - TDM 2.11 or later is REQUIRED to play this mission. You can get the latest TDM version via the installer or here. - Seeking Lady Leicester was originally a work-in-progress given to the Dark Mod community per Grayman’s wishes after his passing and was initially adopted by Bikerdude before Dragofer, Amadeus, and Wellingtoncrab joined to complete the FM. -This FM does NOT support any unofficial gameplay patch or mod. The use of such a patch and/or mod could break things in this FM. You've been warned. - "Story" subtitles are available for this FM. Simply go to Settings --> Audio and select "Story" or "On" for the subtitles setting. - This FM may be more hardware intensive than normal. LOD settings can be set below "Normal" to improve performance on low-end machines by disabling certain features. - This FM implements the func_peek mechanic, allowing players to peek through any door that has a keyhole on it by leaning forward. PLEASE NOTE: This function has been known to cause crashes for a small number of players in the past, likely due to using the 32-bit version of TDM. At no point in this mission is it required to use the func_peek mechanic; it is purely optional, so feel free not to use it. Download Version 1.1 This FM is available for download via the in-game mission downloader, or here via Google Drive. Promotional Screenshots ThiefGuild Thread Credits A big thanks goes out to Noelker and Goldchocobo for their wonderful voice work with the briefing and conversations, JackFarmer and itsPapiD for their fantastic briefing video, and nbohr1more for his story contributions and writing one particular gameplay feature that I won’t spoil here but you can read about in the readme.txt. An even bigger thank you goes out to our beta testers: nbhor1more, Daft Mugi, Silverwolf, Havoc, Datiswous, Cambridge Spy, Aluminumhaste, Thebigh, Ate0ate, Acolyte6, Kalavi, JoeBarnin. Thank you all very much for your fantastic feedback and tireless efforts as this FM evolved throughout the course of development! Asset Credits - Arx EOS’s Fish - Epifire’s models - Kingsal's Assets and Textures - WellingtonCrab’s assets and textures - Obsttorte's frob loot script - ZergRush's custom Grayman painting ===================Rest In Peace Grayman. You are missed=======================

I guess I want to be sure I understand the context of entity "death" - both purchasing the glasses and picking them up adds a atdm:xray_glasses item to the players inventory. You mentioned basically the inventory slot which should be the be pointing at atdm:xray_glasses is pointing at nothing So it probably got "killed": -In the process of being added to inventory (in this case it was a purchase) -Upon the first attempt at using it (it sounds like it immediately did not work) -Or in the very small window in between Unless the entity in an inventory slot can be "dead" prior to it ever being added?

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.

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.

True, but, 1. this thread is called "Western stealth FPS with Stephen Russell", and, 2. nothing you said changes anything for me. The gameplay still doesn't look like something I'd enjoy. And, if you really think this forum is cynical, then you don't visit forums much. Actually, the majority of the users are are pretty mature, unlike in other forums.

Bikerdude has made a few updates to this mission so we are looking for a few testers to make sure nothing was broken or overlooked. As far as I can tell this is ready for release but it's always good to ensure nobody encounters unforeseen issues. Lowend players are probably the best target just in case there are any performance regressions too. Mini beta:

We didn't make the holidays (such a busy time of year) so here's a New Year's gift, an unusual little mission. Window of Opportunity Recover an item for a regretful trader out in a wilderness setting, and discover more! Available within the in-game mission downloader or: Download: http://www.thedarkmo...ndetails/?id=79 Alternative: https://drive.google...WTMzQXZtMVFBSG8 Some unorthodox gameplay on regular/ghost difficulties. (Arachnophobes might prefer short mode...) Please expect to need your lantern in regular and ghost modes! Short ("easy") mode is a smaller map, so if you are looking for areas others reference below, or 100% of the loot, you'll need to play on another mode. I wanted to create my first mission before I became influenced by too many others' ideas, and limited myself to what has been done before. As such, this mission is not set in a city/town, and has some features that are likely to be provocative. There's a section some really like, which others don't, either way I kept it short to not last too long. That being said, I hope you do find it fun! :-) Special thanks to those who provided valuable testing and feedback: Goldwell, Kyyrma, plotzzz, 161803398874989, PPoe & Bikerdude (who also contributed a sound). (Please remember spoiler tags to not expose things meant to be discovered by playing.) Like so: [spoiler]secrets[/spoiler] If you are having trouble finding the main objective, here's what to pay attention to in the mission for hints: There is a spot it's possible to get stuck on the ground in the corner by the cliff/rockfall where there's a rope laying on the ground, please take care if you poke around there!

Here are my thoughts on version 20-Oct: Consideration: as a general rule, the vast majority of players will never know what a cvar is, much less how they work. I don't consider cvars an option because after a while, people forget what they changed, how and probably why. - Snuffing out candles feels very natural and I don't personally perceive players could unintentionally put them out often. The risk is there though, especially for people with especial needs. - In my opinion, the probabilities of unintentionally dropping bodies while operating doors is considerable, specially when the frob distance of doors is reduced. - Moving a leg of a body aside is ok but dragging or toying with bodies is no fun anymore therefore the feature is gone for (old and) new players. I personally see more cons than pros and I don't feel I can do anything new, faster or better. It actually is a little confusing that I can do a same thing in different ways now. I am convinced this is a missed opportunity and a common place exists but... Having said all that, if I was a new player I guess I would have to do with what I am given and there's no way for me to tell if I would have felt that something was off or missing therefore: if this change is to take TDM to new heights I will rewire my brain. I would just appreciate that the shortcomings are properly and honestly acknowledged, instead of telling tales. Fun fact: we now have three different keys to drop bodies.

Beta 11 Fix finished-on state auto-update was unreliable Slighty improve scanner title/author detect Tags are now named some whatever regular-version-looking thing to force GitHub to put the newest at the top

Extensive customization options are appropriate during the pre-release testing or early roll out of a new feature. The people testing the feature can't know yet what configuration will work best for them, much less the people making the patch. My expectation is that by the time you have to make a final decision about including this patch in the next official update of TDM, there will be a rough consensus about the optimal parameters for the new mechanics, and you will only need one toggle for the new behavior. Or, preferably, there would be no need for an option at all if we can only get over our OCD about preserving arbitrary semantic grouping in our key-bind allocations; and embrace a superior control scheme that's not designed around highlighting an old gimmick feature whose trendiness expired with the Half-Life 2 era of FPS. But that's a pipe dream. Maybe instead we can just all agree that the general>gameplay options are getting a bit crowded. Perhaps we could split some of them off into an "appearance" or "accessibility" tag. As more people make their own mods and we modernize our accessibility options it is going to become a problem regardless. Best to get ahead of it. I agree, and that is one of TDM's strengths. It borrows and combines many of the best features from the three beloved Thief games, but it also gives FM creators tools to expand their creative vision in new directions. To some Thief purists that will never be an enticing proposition. But I don't see this feature as throwing a bone to those Thief players specifically, but just player in general who are bouncing off our game because it deviates from some genre conventions for no obvious reason, which makes them think this is an unpolished product. It is true that Thief was what set these conventions, and (shockingly/s) it is mostly Thief players who are interested enough in TDM to give it a try... but our responsibility to address these problems (if we can) is the same as if AMD or Linux players were having technical problems with TDM. They are people who we want to be part of our community because we never know if one of them might make the next FM like Iris, or do something crazy-innovative with TDM that we can't even imagine!

Shouldering bodies on frob is a legit proposal worth discussing. I won't however take as a valid argument that "players" are dismissing TDM because "you cannot shoulder bodies in TDM" or "shouldering bodies in TDM requires two clicks". We know what kind of players we are talking about and these players won't embrace TDM for what it is for as long as they have a place in their current universe. It is my impression that all this started on the wrong foot with a single goal in mind. No second thought or regard for anything else.

Hello. There's one suggestion I wanted to make in regard to potential new entities and assets. I noticed there are now rat and horse NPC's, which can be placed on maps and offer a nice touch. Since the action usually takes place in towns, and players can break into people's houses or encounter civilians, I was wondering if cats and dogs could ever be expected. I think they'd add some nice extra detail to towns, and could even have a few roles in regard to gameplay. I was thinking of something among these lines: Cats: Can run about as fast as rats, and have the ability to somewhat block the player (slightly impede movement). Additionally, they can jump and may bump into objects... causing a noise that can alert guards, just like the player throwing objects at walls does. Obviously it should be a very small alert... we wouldn't want an entire army / gang running around the place because a cat bumped into a vase Dogs: Slower than cats and rats but still faster than players, blocks movement like a human NPC. I believe there should be two categories: Dogs that attack, and dogs that only bark (potentially attacking if attacked first). An enemy dog that barks can make a lot of noise, and alert guards from afar to your location.

In the current user addons system, only one addon could ever be installed at a time. This was because every addon would try to overwrite tdm_user_addons.script, and only the one in the alphabetically latest .pk4 would win. Merging addons was not a practical solution for most since this required a similar level of proficiency as actually creating the addons. Coming to the next dev build for 2.12, this limitation has been lifted by automatically including or calling all script files or functions that start with a specific prefix. Addon creators will need to choose unique names, however, which could for example include one's username. For now, backwards compatibility with the old style of addons will be maintained so they will still work, but they will need to be updated before several can be installed at once. Note to creators: as this may result in a surge of popularity of user addons to "mod the mod", it feels like some remarks are necessary: it's important to communicate to players downloading the addons that these are to be used at one's own risk and there's no certain way to ensure that no mission will break. releasing a stable mission with the default TDM package is hard enough. Addons create another layer of complexity that is out of the authors' hands. So while it's okay to ask, please respect the authors' decision not to support addons. savegames will only work with the exact combination and version of addons that they were created with. Updated instructions for creating addons can be found here: https://wiki.thedarkmod.com/index.php?title=A_to_Z_Scripting:_Script_addons_for_players

@lowenz @chakkmanit's not a bug, it's a helmet that protects against blackjacking. From the wiki: blackjacking: That's why the bj doesn't rise. Though if it still doesn't hit the guard, then that's a bug, I suppose. I think the game lacks a proper way to inform players about these helmets. The Training Mission doesn't include any guards with protective helmets, so currently the wiki is the only place one could learn about them... In my opinion, the "low back" can be deceiving. The guard in the screenshot doesn't have it, and some guards have it but can still be blackjacked.

Some folks have been asking about the new tdm_show_viewpos cvar and screenshot_viewpos command, so I thought I'd make an thread about it as a reference. The purpose of the cvar is to show the viewpos on the player HUD, and the purpose of the command is to add the viewpos to screenshots in order to help with troubleshooting and beta testing. Bug tracker: https://bugs.thedarkmod.com/view.php?id=6331 tdm_show_viewpos tdm_show_viewpos is a cvar to show/hide the viewpos on the player HUD, which can be set to the following: 0 --- hide 1 --- gray font color 2 --- cyan font color screenshot_viewpos screenshot_viewpos is a command that takes a screenshot with the viewpos added to it. screenshot_viewpos screenshot_viewpos <gamma> screenshot_viewpos can be typed at the console or bound to a key. The "gamma" is an optional argument, which as of 2.12 Beta is the r_ambientGamma value. Some mission authors prefer to have screenshots (from players) that are brighter, so they can see what is in the screenshot more easily. Setting the "gamma" argument is a convenient way to temporarily adjust the gamma just for the duration of the screenshot. For example, I have the following bound: bind "F12" "screenshot" bind "F11" "screenshot_viewpos" bind "F10" "screenshot_viewpos 1.3"

Hi, good taffers. I'm new player. I never played Thief series. I looking for maps for newb like me. Easy map, not hard quests, patrol men without lamp, no many light, etc. Good maps for nabs, which I finished and I recomend for new players: 1. Mission 1: A new job 2. Thief's Den 1 3. Thief's Den 2: Chalice of Kings (Thief's Den 3: Heart of Lone Salvation is yet hard for me ) 4. Coercion Any suggestion, pro players?

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

How about using TDM automation framework (and maybe pcem/qemu)? More info see: https://forums.thedarkmod.com/index.php?/topic/19828-automation-features-and-discussion/

I am 100% on board with optional bonus challenges (mutators) you can activate before launching an FM. Could be a nice project for me for 2.13. As posted in the "Hazard Pay" thread, my idea for a save restriction mutator is that you pay for each save with some resource like a water arrow or a health potion. Something that hurts, to make players who seek the tension think twice about saving. Another mutator idea was "Ghost", i.e., mission fails as soon as stealth score turns non-zero and blackjacking is disabled. I wonder why everybody jumped on the save restriction topic, instead of this mutator, which would be really useful for quite a few players, wouldn't it?

Because you learned to adapt to the nuisance. It doesnt make it less of a hindrance to new players. An argument from experience to correct a issue, New players getting frustrated and not knowing useful mechanics is kinda the point of the change. While at the same time keeping minimal hud.

The way I see it is that when playing a game for the first time players always play the vanilla version. Exceptions are when a game is known for critical bugs or old enough that requires a fix or patch to run properly but regardless, players don't mod games on their first run. Now, playing a game a second time opens up a whole new scenario and here is where mods spice things up: play the same but differently. Here is an idea. The Augmented are qualified players from a future, cyberpunk era. Augmented participate in simulations by impersonating a character and in the Mircea complex the Augmented line up for the upcoming Tournament: The Dark Module. Equipment, mechanics and rules differ from module to module but all games share the same, single goal: complete a simulation as fast as possible. Now, if you like this premise then the Augmentation Mod must be built around the one rule: get to the Mission Complete as fast as you can. In order to make the most out of the limb damage system I suggest a kind of weak character with outstanding healing capabilities. And since the mod is about speed I suggest players level up or level down in accordance with how much they run.