Search the Community

I've been involved in the TDM community now since before we had a game, since way back when we were arguing over lock picking methods lol Finally, I'm finished with Briarwood Manor - my first Fan Mission for The Dark Mod. I've been hatching this for a year so I'm wrapped it's finally done. Briarwood Manor Crowind - made the Briefing for the mission: This is the HD version. Briarwood Manor is a old manor house built and added on to over the years which gives it it's design. The family part is the original home, and two other parts were added on later. Inspiration came from an image in the TDM Editors Inspiration thread. Available through in-game downloader. - available also in the link below. Update Version 1.93 - Fixed a few issues that surfaced, and added a sign to the Armory because people were missing it and thinking the mission was very thin on resources. Remaining Issue: - DO NOT BE SEEN BY THE STEWARD AT ALL! Update Version 1.91 - Removed an erroneous LARGE file that had accidently been in the mission blow the mission size up dramatically other assorted bugs fixed that were pointed out by the Community. Thank you Also replaced the missing script file that controlled the Drop Key which I accidently deleted. LOL Update Version 1.9 - Fixed a bug caused by roof projecting into the sleeping maids room upstairs. Update Version 1.81 - Fixed a bug caused by a faulty newspaper readable that I couldn't fix, so I converted it to a static model that is no longer frobbable. Update Version 1.8 - Fixed a problem with a patch that somehow got misaligned in the previous version of the level creating a ceiling shadow. Update Version 1.7 - Fixed some brush splitting, and a problem with the stairs. Also fixed a readable problem, and a few other minor problems. Added little more detail around the woodshed. Update Version 1.6 - Fixed problem with Crowleys Diary, and a screwed up shadow in the old well. Update: Version 1.5 - Resolved the problems with the Steward and the Dropkey. They should never be a problem again. Unless you decide to hit him, then you are going to break him from his route lol. Fix an sound issue, and fixed a problem where the player could get into places he shouldn't until the right time. lol Improved the performance for the garden area. It should be playable for low end PC's now. If you get stutter issues, drop your video settings, especially the LOD setting. With LOD set to Very Low, Fog will be gone, and detail will be dropped a lot at a distance. The higher you raise your LOD the more you get. ie at LOW LOD Fog comes back. Experiment so you get a setting your PC is happy with. You can use the console command com_showfps 1 to see what FPS you are getting. 30 and above are acceptable. Enjoy. Update: Version 1.4 - Resolved (partially the drop key issue - save before you go into Stewards room, fixed many other minor problems picked up by Abusimplea. Added a new room, made the map a bit more open, solved some of the difficulty issues people had. The map should now be ghostable. I hope. Should be added to the in game downloader within a day or so depending. https://drive.google.com/file/d/1I_-ZJDGUtK7P4-b5zsGsEcYAH0vYdgnw/view?usp=sharing If you download from this link, top right arrow pointing down, is how you download it. Click it. A few things to note: 1+ Hour of gameplay - Easy Difficulty is intended for new players. Hard/Expert for most of the TDM Community. This is a challenging map for new players. Use your tools Features a custom intro (above) and a few custom sounds, and some voice acting. Warning: This mission is not for low end PC's. The house is fine, but the garden will make lower end PC's grind. The map has been made sensitive to LOD settings. So if it's grinding you're PC drop you're LOD settings for it, then you can return them to normal once you've finished. On my Medium PC gtx 760 with Normal LOD I get 30 to 60 fps in the garden. I upgraded to GTX 1070 and get pretty good 60 fps in the garden. Briefing Video made by Crowind and I can't thank him enough. He did an amazing job of this. I was so lucky to have him do this. Cast: Voice Actors (Intro) : 1St Merchant: Crowind, 2nd Merchant: Mykel19XX Corbin: Goldwell Voice Actors (Mission): Corbin played by Goldwell, Morgan Crowley played by V-Man, Giles MacCadie (Steward) played by myself Thank you to my Beta Testers: Cambridge Spy, OldJim, V-Man, Jaxa, duzenko and Bikerdude. Cambridge Spy and OldJim did most of the hard grind in finding problems, so thank you both so much. If you are stuck or need help, fastest way to reach me is message me on my youtube channel (link bottom of this post). Use the resources you were given and you should have no problems. Otherwise post spoiler free in this thread. TIP: Don't be seen by the Steward, or he might glitch out. Credits: Crowind put my briefing text into a more thiefy style for Goldwell to voice. He also helped with refining the trailer for the mission. Bikerdude (did the coal door for me and let me use his moonbeam method) and sorted the performance side of things out and thereby taught me how to do performance., grayman for providing a script to handle the drop key (Abuseinplea for fixing it from bouncing) and grayman for solving some conversation problems. EHR+ or showing me how to do the double secret door and Fidcal for his Fidcal's A-Z tutorial for Dark Radiant. Without this starting point I would not have started. Changes 1.2 to 1.93 - Added a second way to get into the building - Dining Room and Parlour doors now pickable, to make it bit less linear - Electric Light in Lobby dropped it's luminosity from 240 to 220 Little bit darker. - Door on the landing (catwalk) is now unlocked - Spider no longer walks down to the ladder, or clips into the floor. - Opened up the level more so you can choose more how you want to tackle it; except for family rooms (top of stairs) - Fixed a graphical bug with the back stairs caused by TDM upgrading to 2.06 - Added some plants around bottom of garden wall alongside cart. I don't like seeing planes meeting. lol - Made some changes to the fog in the garden. - Fixed a problem with the newspaper that was allowing the no frobbing bug to occur. Enjoy Neon PS: Why does TAB key no longer tab? It drops to the bottom of the page. I have to say I hate this editor.

Story: Thanks: Thanks to my beta testers datiswous, Cambridge Spy, Aluminum Haste, Acolyte Six, madtaffer, wesp5, SuaveSteve and prjames. Additional thanks to Dragofer and Bikerdude who helped with scripting and assets. Download: Gallery: Thank you for playing! What did you think of the mission? I look forward to your honest feedback! Hints, Tips, Walkthroughs, Spoilers(!): - This mission will greatly reward those taffers who like to explore a mission thoroughly. It is possible to go directly for your objectives, but you will be missing a lot of content. - Many windows are openable, leading to new areas or private residences. - If an area seems hard to navigate due to patrols, chances are you can circumvent it. - Those who like a challenge and some extra replay value owe it to themselves to visit the apartment high above the tunnel entrance at Cobb St. (above the last pic in the gallery) FAQ: Disclaimers, Player Information.

Well, let's explore this a bit. How can this be solved? Currently, creeping overrides running (like you said). Here are a couple issues or considerations: What about players who want to keep the fine control of toggling each one independently? Perhaps some players want to go from creeping to running. At the moment, the code is written in such a way (due to its Doom 3 history) that toggling creep can set the toggled run state, but toggling run cannot set the toggled creep state. The toggle creep key can set the toggled run state to walk but only once. If the player presses the toggle run key again, it will toggle without regard to the toggled creep state. Fixing this would require a lot of code rewriting. Brainstorming: It almost sounds like increase and decrease speed keys are desired. Run key to go from creep to walk and from walk to run. Creep key to go from run to walk and from walk to creep. If you're curious to give this a try, here's a Linux test build that matches beta212-05 (rev 16950-10635) with the following change: The toggle creep key sets the toggled run state to walk but only once. If the player presses the toggle run key again, it will toggle without regard to the toggled creep state. https://drive.google.com/file/d/1osTCQRf7LQ5wPvhGl2uRU4NcFnJPEu9_/view?usp=sharing

If shadow maps support more detail that stencil shadows can't offer, I'm absolutely in favor of enabling them: It makes sense to use them for obtaining new details and effects that weren't possible previously. Geometry based shadows are technically a legacy thing anyway, I imagine that once every player and their hardware work well with shadow maps then stencil shadows may someday be deprecated.

With TDM 2.12, after the credits finished, the "Mission Complete" screen did not display. I found that the screen was black and I could hear my footsteps when I tried to move around. I think the reason for the mission not completing successfully was that the "Do not kill or harm allies" objective was never marked as "1 = STATE_COMPLETE" instead it was left as "0 = STATE_INCOMPLETE". Note, I didn't use noclip throughout the mission. Same as: https://forums.thedarkmod.com/index.php?/topic/18054-fan-mission-the-accountant-2-new-in-town-by-goldwell-20160509/&do=findComment&comment=458491

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

If the "mission fails as soon as stealth score turns non-zero," that would not be good for ghost players. They might need to find out "how" they failed and experiment to avoid alerting guards. They might need to take those score points as a "bust". They might need to take those score points to complete an objective. Then, mission authors would need to encode exceptions into their missions, which would be a lot of work (if they decide to do it at all). However, part of what makes ghosting challenging and fun is when mission authors do not create their missions with ghosting in mind. Please see: Official Ghosting Rules: https://www.ttlg.com/forums/showthread.php?t=148523 Writing code for these rules would be a huge undertaking. Ghost Rules Discussion: https://www.ttlg.com/forums/showthread.php?t=148487 Creating an official mode could alienate these dedicated ghost players, because it would clash with what is considered ghosting in the community. Including the Stealth Stat Tool mod in the official release would be more useful. Or, making the audible alert states of guards quick and easy to recognize could help as well. For these reasons, I don't agree with an official "Ghost" mode. If the dev team were to do it, we should consult with @Klatremus so we get it 100% correct or not pursue it at all. (This ghosting bit should probably be in its own thread.)

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).

I admit that I was skeptical myself at first, but once I tried it in game, I changed my mind. So, I recommend applying the patch to a local build and give it a go in game. It's definitely better experienced than thought about. Regarding the candle puzzle in "Seeking Lady Leicester" (SLL), I agree that this proposed change will make that a bit more difficult, but I disagree on the reason why. The released version of SLL has a flint in the inventory to ignite them, so accidentally extinguishing candles shouldn't be much of a problem. Instead, I think the reason for player frustration would be that the unlit candles highlight, showing they can be frobbed, but when the player does frob, nothing would happen. They might not realize the candles can be picked up with a long-press frob. @Wellingtoncrab and I had a discussion about that exact puzzle during the design of this feature. So, what convinced me that it wasn't really a problem? I tried it in game. Players will learn how unlit candles look and behave when frobbed. Like @ChronA said above: "When most players click a candle 99.8% of the time they don't want to move it, they want to put it out." I decided it was better to optimize for what players expect most often and do most often rather than optimize for rare cases. Players already rage in frustration that they have trouble extinguishing candles or don't realize that they can. Another quote from a player on Discord: "I'd even say the "some players didn't know you could extinguish candles by using them" thing is "almost any new player and a lot of old ones too", since I once had an extended conversation about exactly how immersion breaking and weird it was to have to extinguish candles by dropping them, and literally not a single person brought up the fact that [extinguish candles by using them] was possible." During beta testing, the struggle that some beta testers had with the candle puzzle was not knowing about object manipulation. They didn't know about the "Parry/Manipulate" keybinding, or they forgot about object manipulation because they did the training mission roughly 5 years ago and had not needed to do it in a mission afterwards. So, "long-press frob to pick up" is in the same class of player interaction as object manipulation. In other words, the same problem already exists in TDM v2.11. I couldn't find the original screenshot from one of the SLL beta testers, but here's one similar, showing that the player didn't know about object manipulation: If this is truly in a released mission, I'd like to know about it. We can problem solve for that case if it does in fact exist. I don't think we should concern ourselves with something hypothetical, though. And, I disagree that we should make or keep controls cumbersome for the player in order to add challenge. I agree with @ChronA here. I don't think players are playing TDM for that type of challenge. The patch includes the following cvar: "tdm_frobhold_delay", default:"300" The frob hold delay (in ms) before drag or pick up. Set to 0 for TDM v2.11 (and prior) behavior. When "tdm_frobhold_delay" is set to 0, candles and bodies have the same behavior as TDM v2.11. As of a few moments ago, bodies didn't quite have the same behavior. But based on your feedback, I updated the patch (linked above) to make bodies behave that way. Thank you for your feedback.

Rest assured, I haven't received nothing but praise thus far. Most of the constructive criticism about this FM's design arose during beta testing, and Dragofer in particular gave me a very useful write-up about what can be improved next time. Some examples being that he FM is a bit too spacious at times, its difficulty is rather low (a sentiment shared by thebigh), and the house design is a bit strange or tubular as a result of the FM's more linear nature. It's all been invaluable feedback as I continue to learn DR, and I intend to write up a post-first FM release retrospective near the end of this week going over what I've learned. I'm quite overjoyed about all the positive feedback I've received thus far, but that's not because I'm afraid of criticism, rather I was afraid of how a less traditional mission would be received by the community. I wanted to make something a bit weird with my first mission, and I was wary of how a short, linear mission with a limited player toolset would be viewed. Fortunately, the community has been very welcoming and accepting of weird little ideas, and I intend to take what I've learned into my next project right after my eyes stop burning from all those late-night Dark Radiant sessions. I hope you enjoy the FM, Chakkman!

I had this discussion a lot with my Bloodlines Unofficial Patch and honestly, nobody really knows what an unofficial patch can or should do, because a) it's unofficial and b) many developers add or change features with their patches (just look at CP2077 2.0 or TDM itself). I kept the name because it's similar to the other patches I do and does not stray as far away from the original game as e.g. Snatcher's Mod. Also to me, being able to extinguish candle flames but not oil flames, or enemies getting magically immune just by noticing the player are bugs. If not of the pure computer gameplay kind, then certainly of the consistent world building kind ;).

After playing various Dark Mod FM’s, I become hooked to the game, like I was with Thief (and its FM’s). So, like I do to all games I love, I tried to find ways to improve it. Since my first contact with DM and after playing T1 and T2 with the fantastic “HD Mod”, it became apparent that graphically, TDM struck me strange. Of course, it is clearly a BIG improvement over T3 and it’s not worse then Thief 2014 -- if you remove all those post processing effects, the textures are actually very bad for today standards – but it could be a little bit better. So I started to change a texture here, a texture there, whenever I found a texture that could be improved. Initially, I made this for my own amusement, while i was playing, but as the changes increased, I started to think I it would only be fair to share it with the community. As a note, I really appreciate the amount of work done by the contributors to TDM. It’s amazing how an open source project of a game whose genre is unfortunately condemned to target a niche player base could attract so many talented people to work together and create what essentially is the Thief 4 we never had. So this is in no way a mean to disrespect the contributors and their work. What changed and how Currently, around 530 files were changed. The changes end up in one of the following categories: NOTE: “texture quality” noted below is subjective and represents only my point of view. Again, It is in no way a mean of disrespect for the original author and its work. The texture is good but is in a low resolution – upscale it using AI image enhancement methods. The texture is poor and low res, with poor AI upscale results – try to replace it using various free PBR or raw Image sources (1) or create my own. If necessary, adjust the image using (colors, saturation, contrast, …) The texture has a good resolution and its not quite good but can be improved – improve using gimp (ex: on textures with bur, use sharpen, noise reduction or/and other features) (2) The texture depicts an horrible stew – change it to a decent and delicious stew, because my Portuguese roots forced me to do it. Additionally, specular and normal maps were added to some textures. (1) Free textures and PBR sites already discussed on this forum (texturehaven.com, 3dtextures.me, cc0textures.com and so on). (2) Finding the right texture is not always easy. I always tried to follow the same “feel” and appearance of the original image, but i confess that this is not always the case. Again, very subjective. New version 2021.01.08 * Around 170Mb of textures processed Some tree barks enhanced Stucco change more enhancements on doors, paint paper, fire places, ground textures, curtains .. and much more Screenshots and Comparisons It’s obviously undoable to show the comparison for all changed textures, so keep in mind that the following screenshots are just a very small example of the whole project. Also, very important, keep in mind that there is so much you can do with screenshots and in game the differences are much more clear than what is shown below. Sir Talbot's Collateral https://imgsli.com/MTI2NDE https://imgsli.com/MTI2MzY https://imgsli.com/MTI2Mzc https://imgsli.com/MTI2Mzg https://imgsli.com/MTI2Mzk https://imgsli.com/MTI2NDA WS3: Cleighmoor https://imgsli.com/MTI1OTE WS1: In the North https://imgsli.com/MTI2MTY https://imgsli.com/MTI2MTc WS2: Home Again https://imgsli.com/MTI2MjM https://imgsli.com/MTI2MjQ https://imgsli.com/MTI2Mjc https://imgsli.com/MTI2Mjg https://imgsli.com/MTI2Mjk https://imgsli.com/MTI2MzE https://imgsli.com/MTI2MzM New (version 2021.01.08) Briarwood Manor https://imgsli.com/MzUwNDY https://imgsli.com/MzUwNDg https://imgsli.com/MzUwNTE https://imgsli.com/MzUwNjc The Builder's Influence https://imgsli.com/MzUxNjM https://imgsli.com/MzUxNjQ No honor among thieves: forest https://imgsli.com/MzU0ODE https://imgsli.com/MzU1NTQ https://imgsli.com/MzU1NTk How to install 1) download the pk4 file from here 2) drop it on your TDM game folder (where all the other pk4 files are) 3) Play! Uninstall Just remove z_TDM_HD.pk4 file from your TDM install folder. Disclaimer If you are a purist, please don’t use this texture mod. Don’t bash it for not being “exactly the same as the original ones but hires”. If you find some texture that is copyrighted, please let me know and i will replace it. Fell free to suggest changes, but please don't make requests. Understand that i am doing this while playing and if i start feeling that i'm working instead, i will probably start to loose my interest. PS: I really don't know if this is the right thread to make this post. Let me know if i need to change it to another thread.

Nice - did you find a solution for how to avoid it clipping into walls or other solid objects when coming too close? Off the top of my head there was also a need to handle its behaviour in case the player gets submerged, and various other ToDo's.

I don't consider this an urgent or highly important feature, but found the concept useful enough to ask and may definitely use it on my maps. I actually don't know if it might already be implemented: No FM I'm aware of does this and it's not mentioned on the AI Relations (Editing) page either, however the AI Relations (Scripting) page mentions a gradual sys::OffsetRelation function but doesn't specify if it's also a gradual change in the AI's behavior. When setting team relations you normally have just 3 options: -1 (enemy) 0 (neutral) 1 (friendly). There is one limitation in this system: They seem to be integers and not floats, meaning you can't also express an amount by which the teams should be allies or enemies. Having this ability could have interesting use cases: You may want teams that still oppose the player but don't care that much and will only attack if you get right in their face or stick around for too long. As such you should be able to use values between 0 and +1 or -1 to indicate an interest level in the relationship, as well as values above +1 or below -1 to boost the AI's friendliness or hatred toward another team beyond its normal levels. Consider for instance a FM where thugs protect a territory they own: They don't like the player wandering into their turf, but seeing you is more of an annoyance than an emergency... they aren't as motivated to catch you as a citywatch guard who knows the player is a wanted thief and will immediately jump to apprehend you. In this scenario the relationship between thugs and the player could be changed to -0.25: Now you can walk between thugs for a few seconds and they will ignore you at first, but if they see you for too long you're eventually getting attacked. A super simple implementation would be to merely multiply the AI's alert increase rate from a target with its abs(relationship) toward it: If you set it to -0.5 for instance, AI on that team will take twice longer to be alerted by you until eventually attacking, same for allies who will be slower to notice a friend in trouble... meanwhile if you set it to -2 AI on that team will go alert twice faster than normal. I presume this solution can be done by changing one line somewhere in the alert code, and should have the accurate behavioral effect intended without reducing visual / audio acuity... no existing FM or default behavior should be affected either since I can't think who would be using those values if this feature doesn't already exist.

The target_null is a focus for a func_cameraview entity used in the cutscene (the latter immobilises the player when activated). Looking at idEntity::Event_SpawnBind in Entity.cpp, nothing happens with regards to binding if the bind entity can't be found. Target_null also works without being bound. In the original version the cutscene featured a platform (StormFadeMover) that moves the player down a very long corridor with the aim of fading out the cutscene's sound (my self-taught scripting was very rudimentary). In the updated version I do it properly by calling fadeSound on the relevant speakers.

I don't notice an issue with moving at map start. Do you mean you can't move at all? There are a few small furniture pieces around the player that might cause you to be unable to move further in certain directions. The only time I immobilise the player in that FM is when a cutscene camera is activated, long after map start. I didn't know about immobilisation flags back then. Thanks for the subtitles!

Sorry for digging this out, but, one thing I always wondered: Shouldn't a gamma value of 1 in Dark Mod give you the best experience when you're using a monitor with a gamma value close to 2.2 (which I think is the optimum in terms of realistic colour reproduction)? I have a monitor with very good out of the box colour reproduction, and almost ideal gamma. Yet I have to turn down the in-game gamma to about 0.9 to get a good result. I must say though that I prefer it darker than what the average player probably has, so, that might be the problem here. Still, I usually have very good result leaving the gamma on default setting in most games, which is probably calibrated towards monitors which display ideal gamma.

To cater to both audiences. I mentioned LibreGameWiki as one example. nbohr1more mentioned other uses. Explicitly allowing reuse and spread will help TDM reach a wider audience and would hopefully attract more volunteers. More volunteers which can help improve both TDM versions. There are several benefits for a project of being in the Debian repo. One is that TDM Debian-users can report defects on any package directly to Debian (no need to register on separate forums). Debian may then fix the issue themselves (in their "TDM-libre" package) and will offer the patch upstream to TDM, who can then choose to accept or reject the patch. I envision "TDM-libre" to have the same capability of downloading any mission as regular TDM. The only difference is that "TDM-libre" would come packaged with the regular engine (which is GPL+BSD) and an included mission that has libre media/gamedata. When I play TDM by myself, I want the unlimited-play and can accept commercial restrictions. But if I were to promote it somewhere, or charge for a stream when playing online, or make a video, I would want a version without commercial restrictions (and can temporarily accept limited-play) to make sure I don't violate anyone's copyright. Perhaps. That's what I'm trying to find out.

I dom't use it, i found it here with the filter set to OpenSource. the TOS and PP isn't excluding for an OpenSource app, if they use ads mean that they also need to pay an server for this online service. OpenSource is not synonymous with free either, perhaps after the beta phase it is no longer free, so perhaps you can take advantage of the fact that it is still free to create a series of textures that can be used or search another one in Futuretools. AI generated textures and assets, by definition, don't have any copyright, so you can use them as you want. https://www.futuretools.io/?pricing-model=free|open-source&tags-n5zn=gaming

I suggest you use the term "I", to make clear that it is something YOU want, and that you speak for yourself. But, as wesp5 mentioned, I don't really know what this is about, at all. And, I'm also wondering about all the newly registered people lately, who just arrived at this forum, and already want to revolutionize this mod. This is a thing I noticed 2 or 3 years ago, and which hasn't been present in the 15 years I play this mod and frequent these forums now. Really seems like a common thing these days, to not knock on the door, but kick it in, and stomp right in.

tdm_show_viewpos cvar and screenshot_viewpos command: https://forums.thedarkmod.com/index.php?/topic/22310-212-viewpos-on-player-hud-and-screenshots/

TDM has tons of textures from "free" texture resources that do not allow redistribution and cannot be incorporated into a commercial project. Someone would need to create a huge replacement pack of textures that do not break the look of existing missions and do not infringe on the copyrighted textures. Also, many artists who contributed to this project do not want 3rd party entities to use their work in commercial projects. They intended the models, textures, sounds, animations to be exclusively used for Darkmod content. You would either have to replace ALL assets or contact every contributor and ask them to re-license their assets. Many contributors are no longer active with the project and haven't visited the forums in years so it would be no easy feat. I cannot speak to Debian policy but I think that they treat installers that add non-free content the same as non-free content itself. One could argue that Steam is such an installer but I guess Debian would counter that there are a few fully Libre games on Steam. I think Debian, Ubuntu, or Linux Mint need to consider a repo that allows for games (etc) that include non-libre content but intentionally offer this content for free to the community with no stipulations other than "don't try to sell it as a product".

The gamepad implementation allows for a great degree of flexibility to personalize settings, aside from a few minor issues that I mentioned here: https://forums.thedarkmod.com/index.php?/topic/22337-gamepad-bindings/ I would say that playing TDM with a gamepad works very well, especially considering that it was implemented as experimental and hasn't been changed since then. If I could, I'd go back to 2021-you and congratulate you on buying that gamepad. I notice that your DarkmodPadbinds.cfg looks very different from mine...