Search the Community

Keep in mind also that mission size, and complexity have increased dramatically since the beginning. For a lot of veteran mappers, it can take over a year to get a map made and released. The last dozen missions have for the most part been pretty massive, with new textures, sounds, scripts, models etc. We seem to be long past the point of people loading up the tools, and banging out a mission in a few weeks that's very barebones. We still do see some of those, but I noticed in the beta mapper forums and on Discord, that mappers seem to make these maps, but don't release them, and instead use the knowledge gained to make something even better. Could just be bias on my part scrolling through the forums and discord server though.

There is no SS3, how can they do a remake? And thank god they got rid of unity, that engine is total trash garbage on anything over 60 fps. Just spend 5 minutes on steam forums for Unity project games, and there's just thousands of people complaining about poor performance, stuttering etc.

Probably the .script file that's needed, but unfortunately can't be included with a prefab. Maybe there's a comment somewhere in the prefab (or in the wiki or forums) that says what script it needs and where to find it. (The similar combination setup I used earlier doesn't involve "slot", so clearly uses a different script that I what I have.)

Thank you for a great puzzle fm! I'm having real trouble with the TDM v 2.10-64bit on Linux Mint 21.1 Link to the guide supplied by V-Man339 https://forums.thedarkmod.com/index.php?/topic/15844-fan-mission-the-gatehouse-by-bikerdude-goldchocobo-updated-02112014/page/7/#comment-429405

I agree. I'm copying this idea over to the https://forums.thedarkmod.com/index.php?/topic/21741-subtitles-possibilities-beyond-211/ thread. Related: I'll probably do some more experiments with the current TDM font & size, to understand max char count versus field width.

Some years ago i succesfully downloaded the wiki with wget, for TDM dvd. I dont know if this method wikl work now. https://forums.thedarkmod.com/index.php?/topic/19998-tdm-collection-dvd/#comment-437887

It's the duration that matters. If the clip exceeds 6 seconds, use srt. Individual segments within srt should be 1-6 seconds long. There's more to it than that. I'll DM you later today with a Word doc, a draft fragment of the style guide under development, that delves into this. Specifically, if there's too many words to read in the time that a subtitle is shown, you may need to edit out some words. That is, move away from a verbatim caption. The fragment has quantitative guidance on this.

@datiswous, made that correction fm_test.subs --> fm_conversations.subs @stgatilov, about srt naming and file location, would you be OK with the following edit? New/changed stuff in italics: srt command is followed by paths to a sound sample and its .srt file, typically with matching filenames. An .srt file is usually placed either with its sound file or in a "subtitles" folder. The .srt file format is described e.g. [1]. The file must be in engine-native encoding (internationalization is not supported yet anyway) and have no BOM mark. It contains a sequence of text messages to show during the sound sample, each with start and end timestamps within the sample's timeline. It is recommended to use common software to create .srt files for sound samples, instead of writing them manually. This way is more flexible but more complicated, and it is only necessary for long sounds, for instance sound sample of a briefing video. It's a simple enough standard that it can be shown as an short example, demonstrating that subtitle segments can have time gaps between them. And the example can show correct TDM usage, without requiring a trip off-site and picking through features that TDM doesn't support. Specifically, the example shows how to define two lines by direct entry, rather than using unsupported message location tags (X1, Y1, etc.). And skips other unavailable SRT font markups like italics, mentioned in the wikipedia description. The example would also show the TDM-specific path treatment. The example could be inserted before the sentence "It is recommended to use common software...."

I guess the best image-to-normal conversions I've seen here in the forums are via njob. I am curious about this AI thing though: https://github.com/HugoTini/DeepBump has to be installed into Blender as a plugin?

@stgatilov, in the Subtitles_decls section of the Subtitles wiki page, you show example code, that includes an srt reference. Wouldn't it be better to guide people to place the corresponding .srt files within the "subtitles" tree (where their .subs live), rather than the "sound" tree? Also, should FM authors be encouraged (if not required) to prefix .srt files with "fm_" ? Like "fm_sound8_long.srt" ? Finally, in the "displayed text" section, under the srt command, there's a desperate need to see example .srt content, in this case, something made up for sound8_long.srt (or fm_sound8_long.srt) like: 1 00:00:06,612 --> 00:00:10,376 Something's wrong with this crystal ball. 2 00:00:15,482 --> 00:00:20,609 Bugger me! It's not showing the right dream. 3 00:00:25,336 --> 00:00:28,167 Ah! Here we go. --end

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.

Subtitle capabilities available in 2.10/2.11 are described in the wiki "Subtitles". For info about one new project using these capabilities, see the thread "English Subtitles for AI Barks". That project includes development of a TDM subtitle style guide. The thread here is mainly focused on ideas that would require future engine changes to implement. A. Automatic Switching Between Subtitle Languages Based on Settings This is a follow-on of a forum discussion between datiswous and Geep. It is desirable to have a standardized method for: subtitles to be authored in multiple languages, and so packaged and distributed as part of TDM and its FMs a gamer to dynamically select subtitles in a desired language The subtitle language choice might be controlled by the existing TDM language choice within Settings, or a separate "Subtitles Language" setting. B. Other Possible Improvements Requiring Engine Changes Most of these involve allowing the subtitle code to know something about game entities, and convey that to the gamer. Examples of useful knowledge: the ID of the speaker (or other source) the location of the speaker, relative to the player, the player's view, and other speaking AI. This type of information helps to disambiguate when there are multiple voices present. There are lots of ways such info is visually conveyed in other subtitle/caption systems, and might be added to TDM. C. Providing Subtitles for Existing FX These would have the "verbosity effects" subtitle tag. Beyond 2.11 capabilities, some of the location aspects of (B) would be pertinent.

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.

Introduction A project is underway, led by Geep, to eventually provide English language subtitles (or if you prefer, "closed captions") for all the non-story phrases (e.g., barks) of the stock AI characters. The non-story phrases are identified by the "verbosity speech" subtitle tag. The hope is that these subtitles would be distributed as part of the future TDM 2.12 core and so available to all FMs, both old and new. Since there are 5-10K such phrases in total, this project will take a while. Let me know if you'd like to help. This forum thread can be used for project coordination, and to provide info about - What subtitle sets (e.g., for particular AI) are underway and completed Emerging tools or methods for bulk testing Style guidance for TDM subtitle authors. To support this project, a style guide will be developed as experience accumulates. While motivated by providing some consistency to English speech-tagged subtitles, it may be of some interest to FMers creating story-tagged subtitles, and those subtitling in other TDM-supported languages. Potential improvements to TDM's subtitling system - particularly those that would involve engine/GUI changes - can be discussed in this companion thread: Subtitles - Possibilities Beyond 2.11 Current Status - Subtitles for Barks All TDM vocal sets planned for TDM 2.12 have been delivered. New: Fixup Needed to Run These Under 2.12 Beta 3 The Thug - Update May 6, 2023 released as testSubtitlesThug2 FM. This takes advantage of new 2.12dev features and changes to style guidelines. The Lord - Update May 4, 2023 released as testSubtitlesLord2 FM The Wench - Two postponed April versions - Nov 25, 2023 released as testSubtitlesWenchOriginal and testSubtitlesWenchPatched FMs. Two versions because of Bugtracker 6284. IMPORTANT: See final version at end of this list, released Jan. 14, 2024. The Young Builder (Builder 4) - Update May 30, 2023 released (again) as testSubtitlesYoungBuilder FM. (Corrects error in briefing syntax of original May 17 release.) Average Jack - June 8, 2023 released as testSubtitlesJack FM. The Pro - June 23, 2023 released as testSubtitlesPro FM. The Maiden - July 8, 2023 released as testSubtitlesMaiden FM The Grumbler - July 24, 2023 released as testSubtitlesGrumbler FM The Mature Builder (Builder 3) - August 15, 2023, released as testSubtitlesMatureBuilder FM The Lady (aka Noblewoman) - Sept 9, 2023, released as testSubtitlesLady FM The Moor - Sept 14, 2023, released as testSubtitlesMoor FM The Commander - Sept 30, 2023, released as testSubtitlesCommander FM The Simpleton - Oct. 21, 2023, released as testSubtitlesSimpleton FM Builder 1 & 2 (shared vocal set) - Nov. 8, 2023, released as testSubtitlesBuilder1and2 FM The Critic - Nov. 25, 2023, released as testSubtitlesCritic_FM Manbeast - Dec. 10, 2023, released as testSubtitlesManbeast FM NEW! Lady02 - Dec 21, 2023, released as testSubtitlesLady02 FM. Assisted by datiswous. NEW! The Drunk - Jan 6, 2024, released as testSubtitlesDrunk FM. Assisted by MirceaKitsune. NEW! The Cynic - Jan. 13, 2024, released as testSubtitlesCynic FM. Incorporates early demo subtitles by Dragofer. NEW! The Wench, Final Revision - Jan. 14, 2024, released as testSubtitlesWenchFinal FM . Assisted by Dragofer. See also original May version (released in November) in the list above. All TDM vocal sets planned for TDM 2.12 have been delivered. Thanks, @nbohr1more, for integrating these into the release. All AI vocal sets, including additional ones for future consideration - perhaps as "verbosity effects" - are listed here. Current Status - Utilities buildSubtitleShader.exe - Latest release of April 10, 2023. This program fabricates a TDM sound shader file specifically for the testSubtitles... series of FMs used here. It does so by wrapping each sound file name in a directory into a sound shader with uniform incremental naming. While limited to a single directory, the latest release simplifies merging runs from multiple directories. @datiswous reports that this Windows console program also works under Linux/wine, where it is used with similar "testSubtitle..."-derived FMs for verbosity "story" subtitling. checkDurationsInSRT - May 6, 2023 Update (bug fix) This Win/console program scans a directory for .srt files, examines the subtitles, and warns about those phrases/messages that are potentially too short or too long in time, or that seem to require too high a reading rate, expressed in characters per second. It also looks for within-file subtitle messages that overlap in time. soundDurationsCSV.exe - March 7, 2023 Release This Windows console program scans a directory of sound files, reporting their names and (using pre-installed ffprobe) durations with millisecond resolution. The resulting .csv file can then be imported into a custom Excel spreadsheet for subtitle editing. For more, see also Feb 20th comments . findTooLongSubtitles.exe - Minor update, June 23, 2023 Release This Win/console program scans a directory for .subs and .srt files, checks the length in characters of each subtitle line, and reports those that exceed a specified maximum. analyzeFieldWidth of April 27, 2023 (release not scheduled; too idiosyncratic). Used to determine, for 12pt Carleton font, and a representative sampling of bark subtitles, how many characters might reasonably fit within a given gui field width. Later, parts of this code were used to build calcStringWidth.exe discussed next. calcStringWidth.exe - Oct. 11, 2023 Release. Calculates the display width of an input string, for 4 candidate subtitle fonts Carleton and Stone, uncompressed or 16:9 compressed. statsForSubtitles - June 25, 2023 Release. Starting with The Pro vocal set, this Windows console program automates the gathering and reporting of the basic statistics included with the announcement of every vocal set release in this forum thread. Current Status - Spreadsheets and Related Explanatory Documents, including Workflow and Templates Work by Geep on each vocal set starts with instantiation of a pre-configured Excel spreadsheet. This is used for subtitle editing and to do automatic calculations to help manage constraints and decision making. The announcement of each AI subtitle release here includes a link to the corresponding spreadsheet. At first, the spreadsheet's columns, formats, calculations, and highlighting (and its distillation into template form) would change quite a bit between each AI. As of June, 2023 and AverageJack, it has largely stabilized, and is now documented: June 10 Documents Explaining Workflow and Excel Spreadsheet/Template (for AverageJack) The v5 template was used for vocal sets from June's Average Jack to November's The Critic. Further clarifications are now available: Dec 7 Update of the "Explained" Doc for Spreadsheet Template v5 Subsequent vocal sets, through to 2024's The Cynic, use template v6: NEW! Jan. 10, 2024 "Explained" Doc for Spreadsheet Template v6 Current Status - Style Guide for Barks As of Sept 2, Subtitle Style Guide - Part 1 is now available. NEW! As of Jan 16, 2024: Subtitle Style Guide - Part 2 with more discussion and references. Current Status - Third-Party Tools For editing of "story" SRT files, datsiwous found "kdenlive" particularly helpful [to do: link to how-to below]. Geep has been working with the simpler, audio-only "Cadet" for barks.

As someone new to contributing, this has been an incredibly frustrating and stressful experience. I've felt like I'm racing towards an unknown deadline. I've lost track of how many hours I've put into TDM testing and code writing this month. One of the biggest sources of stress is not knowing the beta release schedule. TDM 2.10 was released March 2nd, 2022. So, my thinking was that these could get in this month (January), and then February would be mostly frozen. These are small changes compared to other patches I've seen made, and I don't consider them at risk of breaking the game. The "mantle while shouldering" code change is simple, but the hardest part is agreeing on its behavior. That changed behavior will affect both players and mappers. At least some players want that change, so I don't understand the hold up and big controversy. The main reason I saw against it was that an existing mission might have a mantle trap, so this change would break their mission. But no example was given of even a single case of this. The other source of frustration is not knowing what the internal dev communication is. I've been doing my work mostly in the dark. Also, sometimes I get surprised by a message like "the group has decided X" without a reason. And, from my point of view, my changes have been mostly bug fixes uncovered during beta testing. It would be a shame for players to have to wait an entire year for these bug fixes. And, I'm writing a TDM getting started guide for Thief players, incorporating these recent changes, because I know veteran Thief players would likely enjoy these changes. Again, not knowing the release schedule, I'm also racing to finish that guide against an unknown deadline. I wanted that guide's release to be the same day as TDM 2.11's release.

Edit: in post 5 I discovered Whisper which does this task MUCH better. So don't use vosk. Some of the info till post 5 is still relevant for subtitle editing in Kdenlive in general. I previously posted about this in a status update. To make it a bit more in-view for the future I post the info also in this topic. I recently figured out how to make subtitles work for missions following this wiki guide: https://wiki.thedarkmod.com/index.php?title=Subtitles You can type in the subtitle-text manually either in the .subs or .srt files (in a text-editor) or use an video editor for that (recomended for .srt). What is also possible on some advanced editors including the free and open source multiplatform (Windows, Linux and Intel-Mac) Kdenlive editor is to auto generate the subtitle text for you from the audio or video file. You can then export to an .srt file that works directly in tdm. If you want to use the subs files for shorter sentences, you can just copy text from the .srt files. In Kdenlive you can install speech to text libraries from VOSK. For this to work you have to download and install Python. Info how to do the process of installation and usage can be seen in the following video (6.5 minutes): To sum it up: Configure first time: Install Python. (on Windows) During setup, you have to select Advanced Options and there mark Add Python to environment variables (super important!). In Kdenlive go to menu settings, click on configure Kdenlive. In that configure window, click in the left menu on Speech to text. There you click on the link to download speech models. On the website ( https://alphacephei.com/vosk/models ) you can click on a model download link, but keep the click pressed and move your mouse with the link to the configure Kdenlive window. Kdenlive then asks to install the model from url. vosk-model-en-us-0.22-lgraph is probably decent for most use cases. but you can install and test them all. To use it: First load an audio or video file into the view by dragging the file in one of the audio or video bars at the bottom (video: v1, v2 or audio: a1, a2). Click on menu Project > Subtitles > Edit Subtitle tool. You see an extra Subtitles bar on top. Now you select the audio or video file (it is sellected when it is outlined with an orange border) in the specific bar and then click on menu Project > Subtitles > Speech recognition. In the Speech recognition dialog, you select the correct language model and choose option Selected clip. After generation, you can preview the generated subtitles via the top right window. Make sure it is at starter position for playback. Using an audio file, you see a black background with the subtitles on top. Now you can tweek the position and edit the text directly in the Subtitles bar. This takes up the most time. Unfortunatelly the generation is not flawless, so you have to correct some words. Tweeking the subtitles for Requiem took me hours, becouse I wanted them to line up differently. Usually the subtitles are not generated as full senteces. This looks sloppy. If you want to add subtitles quickly without spending much time on it, it can be done this way. If you want to do it right, it still takes a lot of time in my experience. To export to .srt is shown in the following video: Although actually it's just one step: Click on menu Project > Subtitles > Export subtitle file. Alternativelly you can just save the kdenlive project and then the srt is exported as well. Every save will update the srt file. I might create a wiki article about it later. Kdenlive edit window:

It'd be great if there was a download counter on the missions page (https://www.thedarkmod.com/missions/), or ratings, to guide a newcomer towards which missions would be a good idea to try first. But hats off to everyone that contributed, as always!

@stgatilov Could you please take a look at this? It would be nice to get this in during the 2.11 beta, because I plan to include it in a "getting started with TDM for Thief players" guide I'm writing.

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?