Search the Community

"...to a robber whose soul is in his profession, there is a lure about a very old and feeble man who pays for his few necessities with Spanish gold." Good day, TDM community! I'm Ansome, a long-time forums lurker, and I'm here to recruit beta testers for my first FM: "The Terrible Old Man", based on H.P. Lovecraft's short story of the same name. This is a short (30-45 minute), story-driven FM with plenty of readables and a gloomy atmosphere. Do keep in mind that this is a more linear FM than you may be used to as it was deemed necessary for the purposes of the story's pacing. Regardless, the player does still have a degree of freedom in tackling challenges in the latter half of the FM. If this sounds interesting to you, please head over to the beta testing thread I will be posting shortly. Thank you!

GAMEPLAY * Frob controls have been reworked completely. Previously players were annoyed by having to do three presses to extinguish a light. Also, some player didn't even know that bodies could be shouldered and were limited with dragging bodies. Now simply clicking the frob button performs the action player needs most of the time, and pressing-and-holding the same button performs alternative actions like dragging bodies and extinguishing candles (thread). * Several aspects of mantling has been improved: overhead mantling has become faster, mantling over low obstacles is allowed while carrying an item or a body. Also it is possible to switch weapon while being on rope/ladder or mantling. Pressing crouch button on rope/ladder now starts slide-down immediately. * Some aspects of gameplay can be further simplified. Auto-search bodies is for players who don't want to waste time searching for keys and purses on guard bodies. Lockpicking "Auto" difficulty now indeed trivializes lockpicking (thread). * Leaning animation has been improved with lower head tilt (thread). * Player footstep sounds have been rebalanced. Metal and water sounds were especially painful previously. * Further improvements of subtitles: revised location and font to avoid overlapping with other GUI elements, added directional cue, better slot allocation. Each subtitle is now displayed for at least one second even if the sound is very short. * More settings to reduce camera bobbing/rolling/shaking, which is good for players who feel motion sickness from default camera animations. * Now several script addons can coexist and work independently (thread). ENGINE * Optimized generation of light-entity interactions in rendering frontend. Also greatly optimized shadow processing, especially for moving lights. Unfortunately, many existing missions are not compatible with these changes, so you might see light leaking through walls (mainly with stencil shadows). Please report all such cases, we'll apply workaround on case by case basis (thread). * The "old" and "new" rendering backends are finally merged into one. It is as nice to program as the new backend, and as old-fashioned and reliable as the old backend. Single-pass shadow maps enabled by default and now respect noselfshadow. * Materials with polygonoffset now interact with lights. So static decals can have bumpmap and specular lighting. Note however: dynamic decals still don't interact with lights. * Revised parallelSky lights and marked shadowing parallel lights as deprecated (thread). * PNG image format now behaves equally to other supported formats. In particular, it is not required to explicitly specify its extension, and it can be referenced directly in GUI code. * Added functions min/max to material expressions, which can be useful for clamping. * Fixed minor culling bugs on animated entities and enabled entity scissors by default. * Reduced color banding for fog with some dithering at tonemapping stage. * Finally our C++ code can compress and decompress all texture formats we use, meaning that we no longer depend on occasionally buggy/slow vendor implementations. BUGS * Now both OGG and WAV sounds work the same way and stop playing while in main menu. * Fixed "gui::startSelect" as a feature that allows to choose player starting location in GUI briefing. * Fixed warnings in newspaper_bridgeport0X core readable GUI. ASSETS * Added automatic turrets, to be combined with security cameras (Thread). * Added more covered furniture models (6289). * Added wall models from Seeking Lady Leicester (6293). * New and fixed versions of atdm:lamp_electric_square_3_lit_unattached (6315). * Fixed UV map on Stove models (6312). * Fixed some issues with moor AI (6345).

'ello! As you may be aware I spent the first week of this month remaking La Banque Bienveillante, the first mission of my Quinn Co. campaign I started almost a decade ago. Well, with the help of a bunch of lovely beta testers over a month of feature creep, it's now done! I've made a new topic rather than necroing the old one, because I feel it's come along enough now that it is, essentially, a whole new mission made in the spirit of the original. The goal is to eventually make the existing missions obsolete and put this new campaign in its place, but when that happens I'll include a link to the old .pk4 in here for posterity, since I don't believe in deleting work entirely no matter how mediocre it was! To that end, can this please be entered into the mission downloader as a standalone mission? It can then replace the existing Quinn Co. once the second mission is out, thanks! This is a small, short and sweet bank heist that sets the stage for the larger--and much more difficult--campaign in the works. It's mechanically stripped back a little from the initial release, since I feel I got a bit carried away. It is, however, far prettier as well! Your objective is, of course, the vault, but you can take on extra jobs for people to make money on the side; while the vault gives you money to spend in the next mission's shop, it doesn't count towards your overall loot objective whereas optional jobs do, so it's up to you if you'd rather almost empty the place to make ends meet, or take on extra work if you're less inclined to go hunting for shinies! Screenshots Thanks Big thanks to all the lovely beta testers without whom the mission would probably fail to run! Acolytesix, Datiswous, jaxa, madtaffer, Shadow, thebigh, The Black Arrow, Wellingtoncrab & wesp5 And thanks to everyone who's continued to contribute to the project over the years - I've come back and there's so much more fantastic content to play with! And thanks to you! For playing! I'd love to hear what you think, and feel free to notify me of any issues - provided they're not game-breaking, they'll be fixed when Quinn Co 2 comes out soon! (tm) Download (.pk4)

And yes, tweaking shaders is fast and easy, and has immediate effect, thus there are many people who do that. I believe we also had some external guy recently who did the same in "Want to Help" section. Maybe we should just add these shader tweaks into addon managers and allow people switch between them as they like? Just like people can install a program (don't remember its name) and add postprocessing like FXAA to any game.

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]

Today I was building my map for a game jam and Idk what happened but there is no preview of the models or prefabs. And prefabs and model that I already placed in the map dissapeared. In the preview there are just a few boxes but it not shows the hole model I've already reinstalled TDM and dark radiant, reload models, prefabs.

DarkRadiant does not care about engines at all, it only cares about file formats. Whether you can use DR with your Godot-based game will therefore depend on whether your game's assets are arranged in the same way as TDM. More specifically: Your game will need to read map data from the Doom 3 .map format. If it does not, there will be no way to save your map from DarkRadiant in a form that your game can access. Export to OBJ is available but if all you want to do is produce OBJ models then DarkRadiant isn't the right tool for the job (you should use a proper 3D modelling app like Blender/Max/Maya/LightWave etc). Your game assets will need a tree of .def files defining important entities to be placed in your map, including certain "fixed" entity types which are used directly by DarkRadiant itself. There will need to be a light entity defining light volumes, a func_static entity defining a static model, an info_player_start entity to define the starting position, a speaker entity to define sound sources, and probably several others. If these entity types are not defined, then built-in features like "Create light" and "Place player start here" will not work correctly. Your game will need a tree of .mtr files defining material shaders, referring to image paths which will be resolved to either uncompressed .tga files in a textures/ hierarchy, or compressed DDS files in a dds/ hierarchy. If these material shaders are not defined, no materials will appear in DarkRadiant. DR does not make any attempt to load "raw" image file hierarchies which are not referred to by material shaders. Your game will need to define a hierarchy of 3D models in ASE or LWO format. No other formats will show up in the model selector. These models can be stored directly on disk (there is no "model shader" tree required like with materials).

Contributions downloads are at http://fidcal.com/DarkMod/index.htm Note that there is no dedicated beautiful sortable webpage list. I don't have time and also this means less delays. Just browse the folders and click on readmes and images and grab any zips. If anyone submits anything I can just upload it in a few minutes. ~~~~~~~~~~~~~~ If you wish to offer coding, modelling, or any other kind of help got to the I want to help forum for discussion. If you have any extensive assets you wish to discuss also you can go to the I want to help forum. If you simply want to share an FM, prefab(s), textures, whatever then post details in this thread (there are other websites for FMs too.) Generally these need to be zipped up with a description.txt plain text file and optionally an image, and uploaded somewhere I can get them such as a fileshare website like rapidshare. Any problem with that and if you have ftp I can arrange a direct upload to a private temporary folder on my website. All submissions to this thread should be accompanied by a short description summary to go on the download page and optionally a picture(s). Such submissions will be placed on my website download page (wip) at fidcal.com. Anything suspect for any reason I reserve the right to delete. I accept no liability for downtime or even no-continuance of the download section or even the entire website for any reason. Downloaders: I accept no liability if you download anything you'd rather not: download at your own risk. Oh yes, and I am not responsible for global warming, economic depression, you name it; I'm not responsible. From there, any mappers can download what they want. The Dark Mod Team may or may not assess some items for inclusion in future Dark Mod updates. FMs may be assessed for inclusion on the Dark Mod website. Anyone feel free to mirror the download folder. Any suggestions post in this thread too.

Well some good news for those who have the 2080 ti and no money to upgrade to the 4000 series. Alan Wake 2 runs at > 70 fps with the FSR3 mod on it at high at 4K need to set "m_bLensDistortion": false, in AppData\Remedy\Renderer.ini to get rid of some ghosting effect on the main char when moving, but other than that it looks quite nice. the FSR3 mod is here -> https://www.nexusmods.com/site/mods/738 an alternative is this mod -> https://www.nexusmods.com/site/mods/757 which also supports intels xee models. there is also one for slightly older AMD cards but it is a paid mod and the author got himself into quite a shitstorm due to some rude behaviour so i wont link it here, look for LukeFZ if you really must. The other FSR3 mods require an RTX or Xee card so for nvidia everything from a 20 series and 30 series. The LukeFZ mod also supports the older GTX 10 series. One thing to note is that your card must be able to handle atleast 30 FPS minimum else it will look like crap and if movement is laggy without it it will still be laggy with framegen (this also applies to cards that support it natively like the 40 series).

Yeah it would be cool to see some more detailed statistics and it’s a shame they aren’t really captured. Since we are talking about fan mission platforms, where players also make the content for the game, I feel like the best thing we’ve got is you can look at the number of content releases for the games. Keep in mind the graph counts campaigns as single missions - so for example NHAT and TBP both count as 1 mission. A good year for TDM has has approaching maybe 50% - mostly we’re 25-30%. https://www.ttlg.com/forums/showthread.php?t=152494 You could also look at the number of ratings thief missions get on https://www.thiefguild.com/ vs TDM ones, but that is pretty iffy in that you could chalk that up to more awareness of the site in the thief community than TDM Out of curiosity is there a reason a thief player can’t be a new player? I kind of think a player is a player and new players would be ones who are playing the dark mod who weren't? Is there disagreement the base of players most likely to pick up the game are fans of the thief games? They are certainly the most fruitful place to find feedback on the game beyond the sphere of this forum that I have seen. When we were trying to finish up SLL there was a lot of discussion on the forums about how long it had been since there was a release for the game. I am thankful that the stats show at least some stability over the years in terms of releases for TDM, but the trend for all of the games is decline. Not doing anything is a valid response if that’s what the devs want to do - it is not possible to provide evidence that any effort will slow that inertia. As a player and content maker I would just prefer trying to find feedback where it is offered from players who were willing to try the game but ultimately could not engage with it and see if there is anything that can be done within reason to ease them into the game. The game has a lot to offer imo. All those players are potential contributors - contributions in turn attract players - it’d be nice to see the cycle go on as long as it can.

Dark Radiant includes an entity list. By pressing "J" this should appear on you screen: As already mentioned, everything but each separate brush with the classname worldspan is an entity. The total of all worldspawn brushes is equal to one entity (entity name: "world"). Only sealing geometry should be in the "worldspawn" class. If you have non sealing brushes, you should convert them into func_statics (and surround them with MC when AI can get involved). Converted func_static brushes must not necessarily be linked together - you can also have free space between the brushes. I vaguely recall that someone (maybe grayman) once mentioned, that, If you want to use multiple instances of a func_static (consisting of brushes), then you should convert the grouped brushes into a model and you should not convert the brushes into func_static and clone it. Func_static is also the classname for models in general. The "show help" info for func_static says, that "func_statics are brush models" - not sure what that means, maybe it should read "func_statics are groups of brushes converted into a func_static or models from the models list."

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

No need of piracy https://sketchfab.com/features/free-3d-models https://3d.si.edu/collections https://www.freepik.com/3d-models https://www.blenderkit.com/asset-gallery?query=+is_free%3Atrue&page=2 https://www.turbosquid.com/Search/3D-Models/free/asset https://opengameart.org/content/free-3d-assets https://foxdevart.itch.io/victorian-study-3d-asset-pack Creating easily owns with AI Tools https://charmed.ai etc.

As someone who tends to alert guards often and occasionally stir trouble when going through a FM, I noticed some major issues when it comes to AI realism and awareness during combat or when guards face difficult situations. Everything's fine when AI go about their usual patrols... once trouble takes place however, the illusion falls apart as guards act like they're less self aware than a toddler. Indeed AI realism can't be improved past a certain point as there's a limit to the effort the team can put into something so complex... yet I do believe a few improvements can make AI behavior much more realistic and exciting. After analyzing this issue for a long time, I decided to put it all it into a few main points... I apologize for their length as I wanted to go in a bit of detail on each one, hope folks have the time and patience to read them. Biggest issue is AI are unaware of where attacks are coming from. I recently made another thread on how I climbed on a table and blackjacked two guards to death as they sat there doing nothing, something that also happens when shooting them with arrows as guards only explore the nearby area. The issue seems to be that AI don't account for the direction a hit comes from, they only know something hit them but act as if it must be some mystical force of nature: If you're sitting in a parking lot and an asshole neighbor throws a tomato at you from his balcony, you aren't going to cluelessly investigate the road in front of you when the projectile clearly came from behind and hit you in the back of the head, instead you'll storm into the building and start looking for which of the neighbors facing that side of the road may be the culprit. Despite voice barks existing for this exact scenario, we never see AI running to get help from other AI. NPC's will do one of two things: If armed and with enough health they will attack or search for you nearby, if hurt or unarmed flee to a random location. I've never seen an AI consciously run up to another AI asking for help and bringing them to where they spotted me, even when fleeing the AI seems to go to a random location. They don't share knowledge with each other generally speaking: The only awareness AI spread to other AI is alert level, meaning NPC A becomes alert if it sees or hears that NPC B is alert too... beyond that there's no coherence or actual cooperation, the voices may indicate some form of searching together but friendly NPC's are never seen actually engaging. Another big issue is voices being played (or not played) in disconnect with what's actually going on. There are AI voices for most important circumstances but they're very rarely activated: It's a miracle to hear a guard say "someone's been hurt" or "there's a body here" when noticing someone who's unconscious or dead. What seems to happen is if AI was already alerted by another peculiarity such as a noise, they're no longer surprised by anything else and won't play the voices designated for that scenario, so they'll only mention a body if that's the first thing to alert them in any way. Furthermore AI don't actively talk with each other while searching together, everyone acts as if they're on their own and not a team. What happens after a conflict is over. For this discussion I won't focus on better permanent alerts, that has greater difficulty implications and I think I made a separate thread on it a while back. The problem I noticed is once the immediate alert has gone down, AI return to full normality and act abnormally calm: The idle voices change from saying things like "it's a quiet night" to "we've got an intruder" but that's about it. In any realistic scenario even a trained guard would be shocked after being in a fight or finding a body. Below I'll list the immediate improvements I see to those problems, which without having an understanding the code myself am presuming can be changed without too much effort: When an enemy hits the AI with any weapon, the AI should be alert to the estimate location of the shooter. If you're standing atop a tower and fire an arrow at a guard, the guard shouldn't draw his sword and look around their nearby vicinity like a fool, but instead run up to the tower where you're standing granted they can pathfind their way to that location. If the player is far away the destination should be fuzzy and a random location nearby, thus the guard won't run to your exact location but will still climb the stairs and enter a room near it. AI need to learn how to ask for help instead of fleeing to random places when not attacking. If an ally who isn't already alert can be found nearby, the scared AI should explicitly run to their location tell them where you are then have the ally either run to your location (if armed) or go to another ally to get them to your location (if unarmed). Even if an AI is already alert, finding a body or dropped weapon or broken arrow should result in the AI speaking the voice line for that circumstance, only being engaged in combat should suppress it. I'd go further and support repeating those voice lines: A guard yelling "we have a dead body" several times during the first seconds of discovery would make them appear more shocked. Similarly talking to a nearby guard shouldn't be done just once when the two first meet: When multiple AI are searching for you, they should constantly alternate between single voice lines (eg: "I bet you're right over there in those shadows") and looking at another guard to talk to colleagues (eg: "I know I saw him here keep searching"), this would be a huge improvement since guards currently act like they're completely unaware of each other during a coordinated search. Making guards permanently affected after an incident is a trickier one but a few tweaks could improve it. The most immediate solution would be changing the idle animations: Instead of stretching or blowing their noses or eating candy, AI should be seen randomly cowering or face-palming or even playing the scout animation to look around carefully. One suggestion I'd absolutely throw here: If the AI found a dead body from an ally, have them cry occasionally... I think that would be an interesting and unexpected detail, that will also get players to think and feel more about the consequences of their actions and how they affect the world. There are other ones I could get into, but some would be more difficult and likely not worth trying to solve. Most notable and worthy of at least a mention is how AI walk over the bodies of fallen friends as if they're doormats: Obviously there's no way to have them drag bodies to the side, but maybe an avoidance mechanism so they don't look like jackasses trying to profane their dead friends by literally stepping all over them could be a fix for that as well! Let me know what you think of those points and if there are other AI issues you've noticed yourself or better solutions you can think of: I'm not sure if I got everything here but I definitely believe the problems exist and we could make the world more natural and immersive with some simple fixes.

Replaced in svn rev 16896. The 20 pixel padding was introduce conservatively before the font was changed. Merely applying the 16:9 vs 4:3 correction allows to reduce it to 15. But also the font is significantly smaller now. I tried to edit text in order to see maximum overflow. It seems that capital W is the widest letter in this font, and I can't get a significant overflow (see image below). So I have reduced padding from 20 to 10. Also I shifted everything to the right, so that now subtitle ring and text field are centered horizontally (instead of the background box being centered). This looks much better with frobhelper activated, because previously frobhelper and location ring center we not at the same X position. Finally, I have increased step between subtitles from 50 to 55 to avoid next subtitle box overlapping with previous subtitle location ring. These tweaks can still be changed, since they don't change anything regarding the text layout. Here is how it looks now (blue background shows the text box): My stance on this is still the same: if large empty boxes look ugly, then we can make several possible background boxes and make engine select the best one that text fits into. This way the decision of which box is OK can be made with the very same code that actually renders this text, instead of some external independent computation. There is no reason why smaller background box should be applied depending on verbosity, except that "it looks all non-story subtitles are small enough now". One exception is enough to break this idea. Alternatively, it is quite possible that we switch from background boxes to black outline around text. Both approaches works rather well, and without background we can forget about tweaking the background box. tdm_subtitles_message.gui

Btw. you know that fresnel on brushes and simple models that use tiled materials looks differently than e.g. models with higher geo density, or smooth edges faked on normalmaps? Might be hard to adjust it for all cases. Unless you meant the PBR-compatible calculations, I guess...

Thank you both! I remember running into the func_* entity types during the tutorials, I should dig into those more and see what else I can do with them. Took a little tweaking, but I got my fan rotating.

I was thinking of creating new libre assets that will complement existing NC assets. Not necessarily replace them. I'd be interested in hearing more about what the licensing issue on Steam was. If it was the NC assets, then a TDM-libre with a basic libre mission released initially could encourage a mapper to create a more developed map, also with with libre assets, that may qualify for inclusion on platforms currently not allowing NC assets. Perhaps. Or perhaps a developer decides to join the project because they like the idea and want to work on it. In that case this thread will provide a good overview of different aspects of this.

TDM Latch Pack (Beta) By Frost_Salamander and wellingtoncrab with special thanks to Dragofer Tired of picking another lock or hunting for that missing key? Imagine The City is itself an elaborate lock, and you are the key. Embrace progression through careful exploration and navigation of the environment. Embrace the latch pill: Included is a new entity type and scripting for a door mounted toggle lock, or "latch", as well as new CC0 assets and prefabs. https://github.com/thedarkmodcommunity/test-latch/wiki Example Video Asset Pictures All models and textures in this pack are released under CC0 license and may be used freely without need of attribution. We waive copyright to the extent that possible, but aren’t lawyers. Latch Lock Features Supports single and double doors across all cardinal directions, as well as trap doors Uses the location system to handle context sensitive frob highlighting of the latch and the doors Automatically determines the correct latch state on map start based on the targeted door's "locked" spawnarg Options for rotate, translate, or both with unique sound slots for each Supports any model or func_static To get started head over and grab the latest release (available with or without demo content) and read the getting started guide. This is a beta release - so your feedback is appreciated!

I agree with @OrbWeaver, IMO DR is not the right tool to make models for Godot or any other engine using triangle mesh's only, if anyone wants a simple and relatively easy 3D tool (but still very powerful in the right hands) to make models, I personally recommend Wings3D instead, is free as Blender, way less complex (no animation/bones support) and it supports obj, collada, and other formats.

It's funny you should ask that because I've been thinking about this a bit and am now wondering if my use cases 2 and 3 (more dynamic in-game readables) are actually possible with the existing system. I'm not sure you would want to actually override the existing scripts but more likely add in new scripts into the existing system. I might have a go at at this weekend.

Merry's Magnificent Mapping Co. Delivers Again! Chase Mercantile Screenshots Title: Chase Mercantile Theme: Bank Release: 2015/02/04 Mapper: Airship Ballet Special thanks: Nobiax for the custom loot models and textures, Melan for his textures and Xarg, Kyyrma, Oldjim, Phi, Melan, Cookie and Bikerdude for beta testing the map for me! Vault and courtyard ambiences made by me using this and this respectively. Build Time: 1 month and 13 days. Well, here it is! We're about 2/5 through the campaign provided I don't decide to extend it. While going back to change things with La Banque I was really enthused to see how much better I am at mapping already, so hopefully you will be too! This is the same deal as La Banque but bigger and better. It's physically about twice the size and a fair bit more complex with regards to objectives and the like. As a result, you get a ton of notes if you buy a lot of things! Having the notes in your inventory is integral to the system itself working, so hopefully you won't mind reading then discarding a bunch of pieces of paper. I've got plans for a somewhat cooler way to introduce the notes to the player, but you're stuck without for now. This is, of course, bundled with La Banque so all that gold means something now! It'll be on the mission downloader as Chase Mercantile so delete La Banque from your FMs folder because it's obsolete. I tweaked the former mission somewhat, spawning some new guards on expert and implementing a 500G/1000G KO/Kill penalty to your loot total across all difficulties. I also wrote a new briefing that hopefully doesn't show how bad I am at English anymore. It was only ever intended as a tutorial, however, so don't expect crazy difficulty there. There's tons of loot to be had, but even more if you're sneakier about it! The same goes for Chase, albeit far moreso: expert difficulty has pretty much 100% guard coverage, so good luck with that. Erm, what else... oh! I recorded the building process, so if you're curious or just fancy zoning out to some timelapses, you can see the map's construction from start to almost-finished here, although hold off until you're done to avoid spoilers. Note - Noclipping around like a mook will skip triggers that change things based on what you bought. It will completely negate the system in some cases and often brick your playthrough. Don't do it unless you've no desire to be able to finish! - As the note you start with says, you can bag up the loose loot in the vault into bags. Dropping these out of the starting window in the basement or at the alternate loot drop (if you buy it) will net you 3000 per bag, which translates directly into 3 gold for the next mission's asset shop. - Knocking people out will cost you 500 gold on Expert, and killing them will dock you 1000 on Medium and Expert. - Optional objectives will pay you gold immediately on completion. - It is impossible to acquire all of the loot in the map: there are variants of some that get swapped around depending on what you buy. Don't sweat it: there's tons anyway! Cheats Come to the thread because you can't find something? Look no further you casual! Obviously don't expand spoilers if you don't want spoilers. Where are the vault keys? How do I get into Chase's vault? How do I turn off the steam? What about the electrified gate? ...and the gas? Where is the sword? Where is the necklace? Where are the client records? Where are the financial records? Where's Turk Malloy? Look, you made a system I despise. The least you can do is tell me what to buy. Download links The Campaign Available on the in-game mission downloader as "Quinn Co." The Single Mission chase.pk4

As of v3.8 and as reported in 5467, DR only supports prefab tooltips for prefabs that contain a worldspawn entity (at least one brush or patch that's left as worldspawn) with an editor_description spawnarg. This is problematic because most prefabs don't contain such an entity, so if a prefab creator desires to include a tooltip something like a brush cube needs to be added to the prefab (see for instance 6267). This is a little messy as the mapper might not understand its purpose or forget to remove it after placing the prefab. It's also tricky to create a series of prefabs with descriptions in a single map because there can only be one editor_description spawnarg in the map at a time, so the creator has to store each tooltip in an external file like a Notepad .txt. I think an ideal solution to this would be that DR prompts for a description when exporting something as a prefab. The prompt window could already be populated if the mapper is overwriting an existing prefab with a description, or if the selection contains a worldspawn entity with an editor_description spawnarg. More flexibility in making tooltips for prefab would imo certainly be a valuable quality of life improvement.

I'm definitely interested in this. In the past it used to worry and upset me that some of the assets are CC-BY-SA-NC: Not because I'd care to sell them in any conceivable format, but because it made the project seem less libre and FOSS and Linux friendly. I remember my only disagreement was with some developers being against FM authors taking donations for their own work on their personal maps and stories, I think that's more problematic but ultimately accepted and respected it since to me that's secondary and I'm just happy TDM and DarkRadiant exist for us all to create worlds with. As stated before, many of the existing assets would need replacements that look the same way. Since the authors of old FM's can't be expected to re-texture all of their maps, those replacements would need the same names or an automatic conversion script, and have to look in such a way that they fit the old textures just right at any transformation. This isn't impossible but something I find unlikely as few people willing to do the effort may find it useful enough to work on one. Such a transition could perhaps be considered if we ever switch to high-res textures: Many of the images could be upgraded with replacements someday... maybe this time we can avoid going for semi-libre assets and use fully FOSS compatible ones. I've also been dreaming of a cyberpunk conversion for years, to have a TDM that's less Thief and more DeusEx taking place in a futuristic environment... also unlikely to happen but the hope in my attempt was to ween off of the stricter assets.