Search the Community

DarkRadiant 3.8.0 is ready for download. What's new: Feature: Support new frob-related material keywords Improvement: Mission selection list in Game setup is not alphabetically sorted Improvement: Better distinction between inherited and regular spawnargs Improvement: Silence sound shader button Improvement: Add Reload Definitions button to Model Chooser Fixed: Model Selector widgets are cut off and flicker constantly on Linux Fixed: DarkRadiant will not start without Dark Mod plugins Fixed: GenericEntityNode not calculating the direction correctly with "editor_rotatable" Fixed: RenderableArrow not drawing the tip correctly for arbitrary rotations Fixed: Light Inspector crashes on Linux Fixed: Models glitch out when filtering then showing them Fixed: Skin Editor: models not centered well in preview Fixed: "Copy Resource Path" includes top level folders Fixed: Skin Editor: internal test skins are shown if Material Editor was open previously Fixed: Changing Game/Project doesn't update loaded assets correctly Fixed: Model Chooser: initially hidden materials aren't revealed when enabling them Fixed: Choosing AI entity class 'atdm:townsfolk_commoner_update' causes crash Fixed: Sporadic assertion failure on shutdown due to LocalBitmapArtProvider destruction Fixed: Prefab Selector spams infinite error dialogs on Linux Windows and Mac Downloads are available on Github: https://github.com/codereader/DarkRadiant/releases/tag/3.8.0 and of course linked from the website https://www.darkradiant.net Thanks to all the awesome people who keep using DarkRadiant to create Fan Missions - they are the main reason for me to keep going. Please report any bugs or feature requests here in these forums, following these guidelines: Bugs (including steps for reproduction) can go directly on the tracker. When unsure about a bug/issue, feel free to ask. If you run into a crash, please record a crashdump: Crashdump Instructions Feature requests should be suggested (and possibly discussed) here in these forums before they may be added to the tracker. The list of changes can be found on the our bugtracker changelog. Keep on mapping!

TTLG? That's Through the Looking Glass Forums. A looking glass fan community. Has been around for a long, long time. https://www.ttlg.com/forums/

No, not really, have only seen him on the forums many years ago. He deserves a lot of credit for providing the SVN infrastructure in the beginnings of the project, it's been only later when we transferred this to a hosted server. Memory is blurry, but I think my time working on TDM and his don't overlap that much - I had been getting more active, and he pulled back a bit. He bootstrapped quite a few important systems, IIRC he's been working on light gem and the first Stim/Response and Inventory implementations. From what I recall, he gave the project an organisational backbone in the technical department which is crucial to keep things together. Folks like Spring and NH who have joined long before me could give more insights, I guess. (Looking at my join date makes me feel old either way. From TDM's current view point, the year 2006 seems like right at the beginning, but actually the mod had already been existing for two years by that time I joined. With the first release in 2009, 2006 is rather in the middle. Heck, I haven't touched the mod code for at least 10 years - and I can still remember a few things, which is a testament of how much it occupied my thoughts back then).

There are other complications though. How much fall damage should player take, if they decide to jump off a rope with the body? Should the player let go of the body or not? Also, right now it's much harder to jump off the rope with the body than without it. Why? And last but not least, how would you teach players these things, possibly without much hand-holding and text prompts explaining the rules? I guess I'm with @STiFUon this one, if you restrict dropping the body, you'll save yourself (and mappers) a lot of headaches. But even that doesn't solve all the problems, I know I'm in the minority in these forums, but as a player, I really appreciate the beauty and efficiency in simplicity of the design. Not overthinking everything and adding more and more rules for the sake of realism (or anything else).

In a private message on Monday (2022-01-16), I asked about some patches. Then, I was asked why I waited until the second half of beta testing. My reply was "(1) I recently shared some config with Thief players and some expressed interest in TDM. So, I decided to write a guide. (2) I've been beta testing a mission, so I've uncovered these recently. (3) I don't know the beta release schedule, so I don't know where we are in the process." In a private message on Tuesday (2022-01-24), I was asked when I would be done with my patches for 2.11. I gave a list, and there was no definitive communication from the dev team that they would not be considered for 2.11. Just that patches would need to stop soon, because the dev team was deciding when to end beta testing. It seemed that I was given the go ahead. I didn't want to hold up the beta's (unknown) schedule anymore, so I put in extra time and effort to get all of my patches in no later than the next day (Wednesday) to give the dev team time. In a private message on Wednesday (2022-01-25), I told a developer, "I've submitted all the patches that I've planned: 6241, 6231, 5892. I'm ready for feedback and fixing any issues with those patches. That'll be it from me for 2.11." I was given some feedback about (5892), and there was no mention that my patches would be excluded from 2.11. This week's work getting into the next beta was going to be my personal triumph and moment to be proud of, because my hard work was going to be done for 2.11. My patches were already submitted, after all. Now, it's ending in a bust. After my post yesterday, I found out that one of my patches that had already been accepted in SVN for both code and assets will be reverted and postponed until 2.12. No reason given. I had checked SVN to make sure it was applied correctly and made sure the core assets were correct. I've been playing with the latest SVN code and haven't encountered any issues with that patch. Now, I don't know the state of that code. (As an aside, I don't have read access to the assets SVN, so I had to request the changed files from a dev.) The patch is for (6242). That patch fixes a bug that can be read about on (thread). Does the dev team think those players are going to be happy that this patch was reverted and won't be available for an entire year? I fixed that for the players, not myself. For (5892), a feature requested by Bikerdude. This was a reason given for not allowing mantle while carrying a body: On Saturday (2022-01-21), the "tdm_mantle_while_shouldering" cvar was accepted and merged into SVN. Bikerdude replied: Now, if I'm understanding right, that cvar will be removed and not included in 2.11. Bikerdude is one of the most prominent mission authors, is he not? Now, Bikerdude's feature is being taken away. A less prominent contributor, myself, is getting his contributions reverted. It's a shame, because my fixes and suggestions mostly come from listening to the community and dev feedback. Submitting patches is a lot of effort, and I could keep those changes to myself instead. My work is for the players, not myself. Usually, I don't propose something or act on something unless I see other players having the same issue as I've experienced. I think TDM is mostly fine as is. It's not like I'm suggesting new arrows, how doors work, rewriting AI, or something like that. I'm at a tipping point of losing trust in this project, because this situation is fixable. Miscommunication happens. How it's handled matters. I did my best to communicate and hold true to no more patches after this week. Also, the dev team could have told me something like "any patches submitted after X date will not be considered until after the beta cycle." From my point of view, the dev team suddenly changed course from Tuesday's "deciding when to end beta testing" to Thursday's "still unknown but sooner than before, I guess?", and the proposed solution from the dev team is "Tough. Deal with it." or "Don't like it? Fork it." instead of "Let's do one additional beta release" to get everything worked out (whether or not patches get included). I think one more beta release to get these completed or decided on is fair, because that's what the agreement seemed to be, as vague as it was. I'm doing this for free as well, and it sure doesn't feel good to see my work handled in this manner.

I think the reason the dev forums exist is to provide a place where the implementation of features can be discussed without getting mixed up with other debates when someone believes what the devs are doing is wrong. We often post public discussion threads for features with subjective elements like the frob outline, because community feedback is very important. But there will always be vocal defenders with strong views for or against certain features, or how exactly it should be implemented in their opinion. At some point a decision has to be made and be carried through, which is what the dev forums are for. Almost all of the threads are very technical, basically explaining and discussing recent or potential code changes with other devs. Its hard to say. Its a hobby the devs do in their spare time, so people come and go when they're in the mood and when they have the time. The team page is mostly accurate except for some relatively newer additions like myself.

This is basically "do include my work ASAP because I worked so hard, or else *sulk*". This is similar case: https://forums.thedarkmod.com/index.php?/topic/21679-beta-testing-211/page/10/#comment-482352 This is neither a commercial product, nor a phishing email. That sense of rush and pressure is artificial. These releases typically do take long, and even then, there are often many things broken by mistake or omission. Often there aren't enough people to test stuff, or they're not competent enough, etc, etc. There's little point in hurry.

Allowing mantle while carrying a body was originally proposed by Bikerdude one year ago (January 2022). https://bugs.thedarkmod.com/view.php?id=5892 I agreed with him, since that is how Thief 1 & 2 work. I've submitted patches, and due to feedback, I've submitted three patches each with a different behavior, starting in August 2022 (5892) : (Patch v1) Always enable mantling while carrying a body. (Patch v2) Only enable mantling while carrying a body if "pm_mantle_while_shouldering" cvar is set. This is already available in 2.11 beta 7. (Patch v3) Restrict mantling at the waist. There is no agreement about how this should work yet. I've spent over 12 hours of work and testing on (v3) so far, so it would be incredibly discouraging if a final decision is not made between versions (v1), (v2), or (v3) for 2.11. Personally, I think patch (v1) always enable mantling while carry a body is best. This matches Thief 1 & 2 and does not require a cvar. If (v3) is chosen, the rules need to be decided. Could you all please answer the following questions? (Please copy and paste the questions below when answering.) Do we really need to restrict mantling while shouldering at all? Is there a mission with a mantle trap? If so, which mission? If we restrict the player while shouldering, what should the rules be? While shouldering, what's the tallest object that can be mantled? While shouldering, should there be different object height requirements between crouched and standing? While shouldering, can the player mantle during a fall or jump across to another ledge? While shouldering, what mantle types are allowed out of: push, pushNonCrouch, pull, pullFast, hang? (Are there other rules to consider?) Resolved Patch v3 is included in 2.12 dev builds, starting with dev16778-10275, which is open to feedback during the dev release cycle. pm_mantle_while_shouldering cvar. pm_mantle_while_shouldering, default: 1 Which restriction for mantle while shouldering? 0 --- no mantling while shouldering a body (TDM original) 1 --- restricted mantling while shouldering a body 2 --- unrestricted mantling while shouldering a body (Cheat Mode) pm_mantle_maxShoulderingObstacleHeight cvar. pm_mantle_maxShoulderingObstacleHeight, default: 41 The maximum height of obstacles allowed for a shouldering body mantle Note that mantling above eye level is disabled regardless of this value

I've spent a lot of time recently submitting patches to fix some bugs and working on a few things that I think would really improve the feel of TDM for 2.11. They are very small changes, and they are meant to polish what's already there without changing or breaking anything for anyone. (Available 2.11 beta 7) Added player "tdm_toggle_sheathe" cvar and "Toggle Sheathe" setting (6232) (thread). Renamed "New Missions" to "Missions List" in main menu (6230). @nbohr1more cleaned up my original patch. Originally, proposed by @snatcher (post). Fixed initial difficulty highlight on Objectives screen (6229). @stgatilov cleaned up my original patch. Fixed Objectives title slightly cut off on low text scale (6234). @stgatilov cleaned up my original patch. Made it possible for the player to change "pm_noclipspeed", so noclip speed can be set (6237). (Available in next beta) Make "tdm_toggle_creep" work like other toggle cvars, and add "Toggle Creep" to the settings menu (6242) (thread). (Not available) Make the inventory parchment background (dds file) separate from the "Missions List" parchment background (dds file). Without the patch, if you change the inventory background, it will also change the main menu. Patch submitted (6241) to decouple the inventory background from the main menu. This is meant for players who want to edit the inventory background (dds file) themselves (e.g. reduce its brightness without affecting the main menu). When you drop a long distance and land in a mantle, damage is shown after the mantle animation is complete. Partial fix submitted (6231). I think I'll need @stgatilov's help on this one. Bikerdude was very kind and provided a test map for this, which helped to expose an issue with my original patch. ("pm_mantle_while_shouldering" cvar available in 2.11 beta 7) It was requested by Bikerdude one year ago to allow mantling while carrying a body. Due to feedback, I've submitted three patches each with a different behavior, starting in August 2022 (5892) (thread) : (Patch v1) Always enable mantling while carrying a body. (Patch v2) Only enable mantling while carrying a body if "pm_mantle_while_shouldering" cvar is set. This is already available in 2.11 beta 7. (Patch v3) Restrict mantling at the waist. There is no agreement about how this should work yet. I've spent over 12 hours of work and testing on (v3) so far, so it would be incredibly discouraging if a final decision is not made between versions (v1), (v2), or (v3) for 2.11. Personally, I think patch (v1) always enable mantling while carry a body is best. This matches Thief 1 & 2 and does not require a cvar. If (v3) is chosen, the rules need to be decided. These are the final issues / bug trackers I have for 2.11. I hope they can make it into the final release of 2.11, because I think it would make TDM feel more polished and give a better first impression for newcomers. And, Thief players would have a better first time.

Looking at the source code and the core pk4 asset files, I don't see any changes that would make a difference. Does this happen with a single FM? Does the FM pk4 file include an "autoexec.cfg" file? From the source code, here's the load order of config files. exec default.cfg exec Darkmod.cfg exec DarkmodKeyboard.cfg exec DarkmodPadbinds.cfg ==> exec autoexec.cfg <load language> <exec command-line arguments> <init input> <init sound> <init OpenGL> <init ui> <load DLL> <init session> ==> exec autocommands.cfg Details about the addition of "autocommands.cfg" are at https://bugs.thedarkmod.com/view.php?id=3199 I thought "autocommands.cfg" was the right way to do it, because that is what I've read on the forums. It seems that "autocommands.cfg" was originally designed for one use case: running "dmap". However, maybe over time "autocommands.cfg" became the de facto config file for user commands and "autoexec.cfg" became the config file for FM authors to use. I don't know. Does anyone know for a fact whether or not this is the case?

For what it's worth: I saw in some old tdm-campain map that bikerdude tagged his name as a spawnarg in everything that he build in that map. I guess it's good for filtering. So I think if the script can add the map file as a spawnarg to everything (brushes, entities, etc.) that is build in the map file automatically before merging, then in the merged map file you can easelly filter everything out that is build from one map file. Except if there is a better way.

So I think we can count 12 or 14 missions depending on our opinion of La Banque Bienveillante and Sneak and Destroy. If these two reissues are counted as new missions (as JarlFrank did here: https://www.ttlg.com/forums/showthread.php?t=152035), then we have 14 missions. If not, then 12. Personally, I don't consider them new missions, so 12 in my opinion. Have no problem with other opinion. In any case, last year was productive!

My dream is for forums.thedarkmod.com to link to thedarkmod.com

Bikerdude is the main author ( other than grayman ). JackFarmer keeps in contact with him off-channel so he offered to assist with this post before Amadeus or Dragofer were available.

Beta Testing: "Seeking Lady Leicester" As most people here know, grayman, longtime lead coder and mission designer (best known for the "William Steele" series), passed away in the spring of 2021 from cancer. According to grayman's will, his son has subsequently donated two unfinished missions to our community. These two projects are completely independent of each other and there is no relation to grayman's well-known "William Steele" series. The mission "The Black Mage" was completed by me last fall and released on Christmas 2021. Bikerdude along with Amadeus and Dragofer have worked for almost 18 months on the second incomplete mission "Seeking Lady Leicester", ready now for beta testing. This is a mansion mission, but it also includes outdoor areas. The playtime is about an hour if you run through it quickly, but if you want to see all the locations and secrets, you'll be busy for several hours. From the feel of it, I would say that this is an advanced mission, so it's surely above "The Black Mage" in terms of difficulty. I haven't played it myself yet, but I've looked at it, and it looks damn good, just like everything else Bikerdude has produced in the last few years. Please sign up here for beta testing, if you can test on 2.11 b4 or higher as this will be a 2.11 release. I then will provide you with details for testing via PM which will take place via Discord. It would be very nice if we could get a lot of testers for this mission, because this release will be the last one that will include graymans name in the authorship. He was very meticulous about testing, so let's not let him down. Jack

Purah also worked on Dishonored: https://www.ttlg.com/forums/showthread.php?t=136214 One of my neurons knew it started with a 'P'

We got TDM VR, for a start. https://forums.thedarkmod.com/index.php?/topic/20468-the-dark-mod-vr-210-alpha-is-now-available/

Yes, it does. Which makes it interesting that you yourself explicitly said that it's interesting nobody had complained here on the official forums: I did, which is why it stood out to me so much that even though you yourself had personally been involved you would reply claiming nobody had complained here on the official forums. I'm not colorblind at all. Does that make people pointing out that almost no modern games have proper colorblindness support hyperbole? Just because it doesn't affect you, or you choose not to pay attention to the discussion of something, doesn't make it hyperbole. Pick pretty much any modern FPS and you will find plenty of discussion about the near universal disregard for FOV and camera movement as accessibility issues. Denigrating those as hyperbole because you personally don't feel the affects is as bad of a look as demeaning people who bring up the importance of valid allergen warnings like gluten or colorblindness and deafness support.

I literally registered just to point out that people HAVE been raising this as a serious accessibility issue since as far back as 2008. It's been repeatedly brought up over and over and over again. And that is just here on the official forums. If you really mean what you've said I think you should find it genuinely concerning that one of the single most widely discussed accessibility issues in gaming has been repeatedly brought up for over a decade with your game and apparently this is the first you've heard of it... even though it's even been subject to multiple issues in your issue tracking system according to these threads and other google results.

here use this link and never miss again its my startpage https://forums.thedarkmod.com/index.php?/discover

You can find a test map here. Note that I remember not being too happy with it. https://forums.thedarkmod.com/index.php?/topic/19825-negative-spectrum/&do=findComment&comment=432949

DarkRadiant 3.7.0 is ready for download. What's new: Feature: Skin Editor Improvement: Script Window usability improvements Fixed: Hitting escape while autosaving crashes to desktop Fixed: Def parsing problem in tdm_playertools_lockpicks.def Fixed: DR hangs if selecting a lot of entities with entity list open Fixed: Float Property Editor's entry box is sticking around after selecting a float key Fixed: Spline entities without model spawnarg are unselectable Fixed: Entity window resets interior sizing forcing resize each time it is opened Fixed: Spline curves should not be created with a model spawnarg Fixed: Newly appended curve control vertices aren't shown at first Fixed: Light entities are zoomed out in preview window Fixed: Entity inspector spawnarg fields not always updated by UI windows such as Model Chooser Feature: Skin Editor (see video) Windows and Mac Downloads are available on Github: https://github.com/codereader/DarkRadiant/releases/tag/3.7.0 and of course linked from the website https://www.darkradiant.net Thanks to all the awesome people who keep using DarkRadiant to create Fan Missions - they are the main reason for me to keep going. Please report any bugs or feature requests here in these forums, following these guidelines: Bugs (including steps for reproduction) can go directly on the tracker. When unsure about a bug/issue, feel free to ask. If you run into a crash, please record a crashdump: Crashdump Instructions Feature requests should be suggested (and possibly discussed) here in these forums before they may be added to the tracker. The list of changes can be found on the our bugtracker changelog. Keep on mapping!

Would it be at all possible to do this from the "main" website? I mean the one you first see when you look up "Dark Mod". Cuz it is a maze in these forums, goodies strewn about here and there but few resources that are intuitively accessible. Also @SeriousToni, what are you planning on uploading?

Originally the mug was created by @LordSoth https://forums.thedarkmod.com/index.php?/topic/13257-tdm-beginners-contest/&do=findComment&comment=287897