Search the Community

Who I am is of little importance, what matters is the job I am offering. Though the item in question may be simple, I can assure you that the reward is anything but. The task, to those brave enough to follow through, is this: During the peak of Braeden's Harvest Festival, break into Lord Alister Squashbottom's manor and steal that which is most valuable to him: his prize-winning pumpkin. This is the very pumpkin he intends on submitting to the judges of this year's competition, and you are to ensure he has no choice but to resign in failure. It may be dangerous, to which you will be amply compensated, but I have little doubt you will be able to weather all obstacles and keep your eye on the prize to complete this task. For those brave enough to accept the job, start here. Cordially, E. Siltstone Gameplay Notes TDM version 2.12 is required to play this mission. Mines are pickable; simply approach them with lockpicks equipped to frob-disarm. A moss arrow can be shot at glass to make it break more quietly. I recommend playing all three difficulties, as they are very different. This FM may be more hardware intensive than normal. LOD settings can be set below "Normal" to improve performance on low-end machines. Download Version 1.0 - This FM is available here via Google Drive, and will soon be made available via the in-game mission downloader. Promotional Screenshots ThiefGuild Release Page Credits A huge thanks to my beta testers Goldwell, WellingtonCrab, Kingsal, Baal, and Rezar for all of your fantastic feedback Voice Credits - Goldwell! Asset Credits Kingsal Wellingtoncrab Goldwell Sotha Bikerdude Refle3cks Arcturus +++And thank YOU for playing!+++

I'd say it goes into the first case.

It goes without saying that I appreciate your comments and I respect your work, eh. We all want the best for TDM. The frob highlight doesn't work well in some situations: difficult to detect in small objects or in large objects in some conditions, frob fighting in bodies and containers... The frob outline initiative failed to provide an alternative and the Frob Helper was supposed to complement the frob highlight but it did it partially, and we ended up with blinking mods, container-disabling mods, auto search bodies... and a questionable Frob Helper. Perhaps madness is the better word. I know people don't like the idea of corsshairs in TDM but a Frob Helper with tdm_frobhelper_ignore_size = 0 would have settled many things for good from day one. I think we agree.

I couldn't help thinking of another realism related suggestion, don't know if it was discussed before but it seemed like an interesting idea. If this were to be changed on existing lights by default, it would have minor gameplay implications, but the sort that make missions easier in a fair way. So... electric lights: Like the real ones of the era, they're implied to use incandescent light bulbs... the kind that in reality will explore and shatter upon the smallest impact, and which like real lamps are encased in glass or paper. In any realistic scenario, shooting a broadhead arrow at a lamp or even throwing a rock at it would cause it to go through the glass and break the light bulb inside. Is it wrong to imagine TDM emulating this behavior as a gameplay mechanic? Just as you can shoot water arrows at flame based lights to put them out, you'd shoot broadhead arrows at electric lights to disable them... you must however hit the glass precisely, there's no room for error and it must be a perfect shot. As a way to compensate for the benefit, AI can treat this as suspicious and become alert if seeing or hearing a lamp break, or finding a broken lamp at any time if that's deemed to provide better balance. A technical look at implementing this: Just as broadhead arrows can go and stick through small soft objects such as books, they should do the same if you hit the glass material on a lamp, while of course still bouncing off if you hit metal: Lamp glass would need a special material flag that sends a signal to the entity upon collisions but allows arrows to go through, unlike glass in other parts of the world which is meant to act as solid and changing that everywhere would break a lot of things. When pierced by an arrow, the lamp should immediately turn itself off while playing a broken glass sound and spawning a few glass particles. The glass material should be hidden if the model is a transparent surface, or replaced with a broken glass texture in case the glass is painted on a lamp model without an interior... obviously this would be done by defining a broken skin for the entity to switch to. This does imply a few complexities which should be manageable: Existing lamps supporting this behavior will need new skins and in a few cases new textures, the def must include a new skin variable similar to the lit / unlit skins in this case a broken skin. Any electric light may be connected to a light switch, we don't want toggling the switch to bring the light bulb back to life... as such a flag to permanently disable triggering the light from that point on would be required. For special purposes such as scripted events to reset the world, we should allow an event to unbreak lamps, setting their state back to being lit / unlit while re-enabling trigger toggling. What do you think about this idea and who else wants it? Would it be worth the trouble to try and implement? If so should it only be done for new lights or as a separate entity definition of existing ones, or would the change be welcome retroactively for existing missions without players and FM authors alike feeling it makes them too easy?

The map files in NHAT v4 were too large to diff in Notepad++ or Meld ( etc) so I decided to test out the old I18N.pl script and it still works fine for me. Caveats? It doesn't understand campaign packs so you have to split the maps and xdata and create a fake darkmod.txt without the "mission 1 , mission 2, etc" part. Then you have to renumber the "#str_xxxx" entries in the other maps so they don't collide. Luckily find and replace can easily fix that. A lot of work to get this working with the latest NHAT version, phew!

Darkmod.cfg yea i'm on 2.12. i remembered to turn off soft shadows too and it seemed to help in some smaller areas thus far. not sure if it's just the scale of things as i venture into the next outdoor area

Already configured: https://github.com/stgatilov/darkmod_src/blob/11165752178aa59f507ae6bd8781f7a4fe81d250/CMakeLists.txt#L88 The problem is allocating more than 2GB during level load. Win32 has a hard limit for processes.

I moved the frob helper and the frob outline options onto the gameplay difficulty page in the Unofficial Patch, because the other options page is indeed very crowded.

So path_follow_actor actually DOES work if you want it to follow the player. You just need to target the player entity dynamically in game. It doesn't work if you target the player_start entity. I can't remember if that's what people were doing (or even if that's what I was doing), but that won't work because the player_start entity and the player entity aren't the same thing. You can use a atdm:target_changetarget entity to do this, or a script: $path_follow_actor_1.addTarget($player1); Both can just be triggered by another path node, a atdm:target_callscriptfunction, whatever. Also you need to add the player target to the path_follow_actor node BEFORE the AI gets to it. If the target gets added after the AI reaches that node, it won't work. Video where the AI hits a node that triggers a atdm:target_changetarget entity: https://drive.proton.me/urls/A3DJW5EYFM#0WgYnCVOU6nv test map attached as well. EDIT: I have no idea why just manually setting 'target' 'player1' on the path_follow_actor node in DR doesn't work. I'll try to look into this. UPDATE: It appears the the player1 entity simply isn't there during initialization when the path_follow_actor's targets are evaluated. As a result, the 'actor' is null and the node does nothing. I didn't mention it before, but when I used the script method I just stuck in the map script's main function like so, and this works too: void main() { sys.waitFrame(); $path_follow_actor_1.addTarget($player1); } UPDATE 2: Wiki updated: https://wiki.thedarkmod.com/index.php?title=Path_Nodes#path_follow_actor path.map

Currently if you are implementing EFX in your map, you need to maintain an .efx file: https://wiki.thedarkmod.com/index.php?title=Setting_Reverb_Data_of_Rooms_(EAX) If you are using presets only, all this is is simply a 1:1 mapping of location entities to an EFX preset. Doing this in a file is kind of tedious and error-prone, as you have to check each location entity in your map, and then check the file to make sure you got the location entity name correct, or didn't leave one out, etc. Would it be a worthwhile feature request to be able to just set the EFX preset with a spawnarg on the location entity itself? Something like: "efx_preset" "WOODEN_SMALLROOM" Also, the location entity has other zone-related information, like ambient sound, ambient light, etc. It would just make sense to have the EFX here as well. This would only make sense for the presets, since you just need the preset name. If you wanted to do anything more complicated, the file could still be used. If both are used for the preset, one could take precedence over the other (the spawnarg pehaps). I don't think anything would need to change in DR either, as it's just a new spawnarg on the entity.

"May his iron mold the current as we were molded. May his instrument expel all obstruction as we are his instruments." - Collected Sermons of Master Plumber Roto Rooter Few would dare cross the Bridgeport Plumber's Guild. Fewer still could glimpse their secrets and live. CC0 POLYHAVEN PLUMBER PACK BETA Includes: Fully modular pipe kit with optimized shadow mesh, two skin variations and near perfect grid snapping at grid level 4 Moveable plunger prop which is fully compatible with the AI weapon system Worry free CC0 license All credit to the great polyhaven.com for the original mid poly meshes - consider supporting them on patreon. I just decimated and then rebaked the assets as well as converted the maps from pbr and made the additional model and material variations.

A Readable? I invite you to read the documentation, experience mods first hand and draw your own conclusions. It's ok. You did the right thing. Fair point but the Blow removes the need for Water Arrows which mission authors might provide for their stories. Justifying our decisions is a tricky business. Ok. No idea but I can tell you item sorting, except for weapons, is messed up: you have 4 keys and pick up another one: the 5th key gets listed first in the inventory but last in the inventory menu. Why? Who knows.

The mission has been added to the mission database and wiki.

congrates & thanks looks like you need a break !? I was near to give you a "Haha-Smilie" or a "Confused-Smilie" Why do you offer the secrets right with the release ? (next time perhaps by EDIT - some month later ? )

finally beat forbidden west but jeez that stearing scheme is atrocious... so you happily stroll along at a mountain side then want to steer past a big boulder but instead of strafing it does a dodge move throwing you a gazillion kilometers from the mountain side fallling to your death yeah well... the shield shute sometimes fails to inflate when jumping down so pretty much the same as above ouch... then when you need to dodge an incomming attack the damn bots cheat and hit you anyway groan... nice story though, but they need to do something about the steering on PC we do not use force sensitive mouse and keyboard ffs .

About the chest sounds, I wasn't aware the Modpack does change them too. Would it make sense for the patch to use your way or would it produce another duplicate script? I can set the blinking to another frequency, but are you sure this is not due to the game trying to apply two blinking scripts at the same time? It looks fine if I only use the patch. Your blow skill is just a last resort for mission unique lights that can't be extinguished by my frob script. Also my version does not include free relighting so it is inferior to yours ;)!

Another issue is that in Always On mode the helper turns into a static crosshair and it no longer helps detect frobs. Let's mod the Frob Helper.

You're on TDM 2.12 correct? Please post your current Darkmod.cfg Also, the performance wiki has been updated recently: https://wiki.thedarkmod.com/index.php?title=Performance_Tweaks

For the people eager to play with the latest state of development, two things are provided: regular dev builds source code SVN repository Development builds are created once per a few weeks from the current trunk. They can be obtained via tdm_installer. Just run the installer, check "Get Custom Version" on the first page, then select proper version in "dev" folder on the second page. Name of any dev version looks like devXXXXX-YYYY, where XXXXX and YYYY are SVN revision numbers from which the build was created. The topmost version in the list is usually the most recent one. Note: unless otherwise specified, savegames are incompatible between any two versions of TDM! Programmers can obtain source code from SVN repository. Trunk can be checked out from here: https://svn.thedarkmod.com/publicsvn/darkmod_src/trunk/ SVN root is: https://svn.thedarkmod.com/publicsvn/darkmod_src Build instructions are provided inside repository. Note that while you can build executable from the SVN repository, TDM installation of compatible version is required to run it. Official TDM releases are compatible with source code archives provided on the website, and also with corresponding release tags in SVN. A dev build is compatible with SVN trunk of revision YYYY, where YYYY is the second number in its version (as described above). If you only want to experiment with the latest trunk, using the latest dev build gives you the maximum chance of success. P.S. Needless to say, all of this comes with no support. Although we would be glad if you catch and report bugs before the next beta phase starts

anyone else having low performance in some indoor areas? i can understand some when starting outside but in a fairly confined space like the lower ship decks or administration building i'm not sure what would be tanking things to a noticeable effect

Welp it's about that time again to wheel out The Lieutenant for another mission and I could use some help making sure it's at least somewhat playable. Please register your interest here and I'll start a new beta testing thread soon. Due to custom assets the file size is quite large (about 500 MB). Potato users welcome. Some screenshots:

Use the following console command to switch between different versions: r_frobOutlinePreset X (X being a number)

It seems like I missed this mission somehow. I'm down in the crypt with the slow match, but I can't get the torches on each side of the gold statue to light. How do I remove the gold statue?

I have numbered your suggestions because I find it hard to multiquote here. As for calling blow and whistle tools and not skills, this was just done to not confuse the player with another inventory class. Also what would the Numbers scroll be? 1) Is there an advantage of your method vs mine? If the result is the same, nothing needs to be changed. 2) I don't know what you mean with blinking being out of sync. Should all loot blink in the same rhythm? 3) It removes the need for slow matches and flints which mission authors might provide for their stories. 4) This is what it looked when I copied it from you, but I had to rename it to avoid duplicate definitions!