Search the Community

Yuletide Boon The idea behind this mission was to again show, what can be built in a small amount of time and with help from other community members. It also showcases the new church modules that I don't think have been used all that much in previous FMs. Enjoy Notes: - TDM 2.13 or later is REQUIRED to play this mission. - Build time roughly 50hrs. - I have created serveral new custom models and prefabs for mappers to use, based of the church models. Download Link: - (v1.1) - https://drive.google.com/file/d/134U40o6wh659wzad7fWqm6wd_dOIQfVa/view?usp=sharing Credits: Special thanks: - Springheel for creating the church modules. - Jack 'mozart' farmer for the briefing video and menu music. - datiswous - subtitles. - Goldwell - voice acting and briefing additions. - Dragofer - pagan statue from http://www.cadnav.com/3d-models/model-40413.html - Misc - Melted candlewax texture from - www.pexels.com/photo/close-up-of-wax-of-a-melted-candle-17959695 beta testers: -Jackfarmer, datiswous, CambridgeSpy, DavyJones, Mat99.

If I try to rotate a model, only the Rotation option is available in the transformation window. No option to scale: Is this normal? Also not able to do so in NetRadiant-custom. Found a solution: https://wiki.thedarkmod.com/index.php?title=Model_Scaling Mods, please delete. Sorry about being dumb.

Yes, I also couldn't install it into a fresh directory for the fm. My "patch" process was opening the old .pk4 and new .pk4 in 7-zip, and copying the new contents over the old ones. I only thought to do this because I noticed that the new .pk4 was smaller than the old one. Oh, hey, I didn't notice this until you pointed it out but I have this problem too! Windows 10, en-us locale. EDIT: This also tracks with me being on Windows 10 and not experiencing the water texture bug.

Merging mission archive isn’t supported or recommended, what operating system are you on..? And regarding the bugs - - engine bug, when you resize models. I have now exported as model. - The railings are non-solid and a no-draw solid brush is in place. So what your likely seeing is the limits of the physics & collision detection that I cant do anything about unfortunately. - Fixed, that was a minor oversight by me. - Short of exporting the whole thing as a model in the hopes it might fix it, this is a known quirk of the engine. Both parts of that support column and the capitol are func_statics, so this should not be happening. - it looks fine for me, so I don't know what the issue is.

I just tried v1.1. The new intro area looks really nice and prevents any anticlimactic "insta-KO" approach. Well done! However, I also had to merge the old and new pk4's, otherwise v1.1 would not install. This is how the water looks for me in v1.1: And while we're still in bug fixing mode...

Back in the day, Tels managed a squad of volunteer translators for TDM. I am not Tels, and could never do that. Nowadays, language translation using AI, either traditional machine learning (ML) models or large language models (LLMs), is common and increasingly fluent. It is often used as an adjunct to speed the work of professional human translators. By itself, AI translation can be imperfect but usually sufficient. Can this "sufficient" approach be used for TDM, to expedite translations? Let's see. I gave some initial thought to a bulk-translation daemon that might range across FMs and fill in all missing translations, without necessarily involving mappers. In the future, possibly AI could tackle that whole enchilada. I was at first visualizing something more modest: a backbone in a standard programming language (I sketched out C++ and C# projects, but lots of other possibilities) that would make calls to an API (I looked at those of Google Translate and ChatGPT). However, I changed focus due to certain concerns... Different FMs, and subsets with each FM, would likely have far better translations if they were properly grouped, ordered, and translated separately, with an appropriate context (e.g., phrase engineering) added. The FM's mapper is best placed to provide this grouping and context. I'll detail what I mean in the next few posts. The mapper would not be expected to know any TDM-supported languages besides English. Instead, each translated phrase could be back-translated to English and examined. Is the "round-trip" meaning OK, even if the English words have changed? Problematic translations could have their context tweaked and rerun. Many AI systems, particularly for API access, require a billing commitment (e.g., credit card). For a professional translator, this is no problem, and subscriptions allow access to more (and putatively better) models and higher quotas. This seems less appealing for TDM. A few paid AI systems have a no-subscription, pay-as-you-go account tier. The cost per translate is typically pennies. But it does introduce quota- and expense-management, and may exclude API usage. Access via API requires an API key (or at the higher end more elaborate security regime), with attendant key-security headaches. Which AI model is thought "best" for translation? Doesn't matter too much, because we can't afford the best. Furthermore, there's endless churn among AI models, with antidotal reports that a given model fluctuates in quality over time, and successor models can be worse than their predecessors. So, with these concerns in mind, I looked for public web-based AI sites that require no billing and provide low-quota but adequate AI. The mapper would enter and retrieve data manually. I will focus on ChatGPT in this exploration, after a quick preliminary test confirmed some promise. Also, as this exploration proceeds, I hope to propose changes to TDM to make it more viable for "sufficient" quality machine translation. Problem areas are incomplete fonts, space-constraints, and layout issues for translated strings. My proposals will likely surface as separate forum threads. That's enough for now. I'll be trying for 1 or 2 substantive posts per week, as I tackle a particular FM.

You can ask people to test your mission here, but the beta tresting should be in this other section: https://forums.thedarkmod.com/index.php?/forum/59-tdm-mission-beta-testing/ Read also: I think it's so that there are no spoilers in view for new regular players.

Downloaded the new version to look at the new intro area (felt like I ought to do so because... I asked for it). Looks nice! Also, starting the player out there gives the builder priest time to get a bit through his patrol path so he becomes much more of an interesting AI to deal with, and there is some context for why he instantly attempts to wallop the player on sight. I did not notice any issues with the water texture in the cave - but I had to do a slightly weird process to update. Krampus_1_1.pk4 by itself didn't seem to correctly load for me in TDM, and I noticed it was about 10mb smaller when I downloaded it off google drive. Seems like you forgot to reupload the briefing video or something? So I dragged and dropped the contents of the 1.1 pk4 into the original .pk4 and then everything worked. Maybe I just managed to preserve the functional water texture somehow or something. I was still able to open the offetory box from the wrong side, but I had to really try to make it happen so I'd say your attempts to block it are good enough. If I wasn't frantically frobbing every pixel of the box to try to break it on purpose, I doubt I would have noticed on a casual playthrough. Another tiny nit I found, while I was trying to see if I could bug out the cave water texture somehow: there is a patch for dirt underneath the water in the cave that obviously ends a little bit too early. I've attached a screenshot of the seam I found while I was swimmin' around lookin' for loot.

I guess this is basic stuff for you talented model-boys but now I've trudged for several hours without results and from what I have read in several forums/threads, it's even not that trivial. Therefore I dare to start a thread... I've download some models from the web but these come in some new and fancy format; (FBX, USD etc) not exactly the old and brittle format that we use in TDM So to import these into DarkRadiant I need to convert these to lwo or ASE, right? How do people go about this? I have tried to: - install Blender 5.0 and added an ASE-exporter plugin. Blender actually puts out an ASE-file but as I try to open it in DR, the model is only showed as that checkerboard error-box. Do I need to tinker with the model in a text editor first? I read something about changing something about a BITMAP-line... - use an ancient version (7.0) version of Lightwave but that program cannot even open the files (Not surprising)...

Unreal tournament (99) mod "Thievery UT" and "Thieves Guild" mod for Rune (2000) are using the same Unreal 1 engine. Things can be re-used, after some changes. The other things he can use in his mod, that i loved in TUT: the missions with guard-bots, the environment, the guards behavior, sound and music. I know this because, in my spare time in the early days, i edited maps for both games. For example, i converted Unreal1 map illhaven to Thievery UT. (And i chnaged unreal 1 - intro map to an thievery tutorial map.) I can remember that i did this also for Rune with the same Illhaven map. And also converted the deus ex 1 new-york map to Duke nukem forever restoration project. (In short: Export the mission to t3d, import the T3D and re-texture)

I wish you all a happy new year!

Happy to hear you found a solution! I'm glad you posted this though because I actually learned something new about model scaling with that wiki article you just linked. I didn't know you could scale models in one dimension only

http://i1049.photobucket.com/albums/s390/sirtaffsalot/vfat3_2015-02-16_18.15.48_zpsdf13cqmi.jpg UPDATE: This is now a Campaign Pack courtesy of Datiswous: https://www.thedarkmod.com/missiondetails/?internalName=vfatc What is The Complete Vengeance for a Thief Campaign? The Complete Vengeance for a Thief Campaign is a three part campaign with a brand new installment at the beginning called The Angel's Tear. The other two installments are the previously released A Pawn in the Game and The Art of revenge with new areas, additional story plus bug fixes and performance tweaks. What are the new areas in A Pawn in the Game and The Art of Revenge? Pics The Angel's Tear: New areas for A Pawn in the Game and The Art of Revenge: Download links: http://www.mediafire.com/download/c2p0myxp32hb8sb/The+Complete+Vengeance+for+a+Thief+Campaign.zip Installation instructions: Unzip the zip file and extract the three pk4s to The Dark Mod's FM folder. Load up TDM and play them in order. Thank you to the following: Bikerdude for help with visportals in the original A Pawn in the Game, visuals in The Angel's Tear plus all the mapping advice and tech support he has kindly provided me with over the years. Beta-testers for The Completer Vengeance for a Thief Campaign: AluminumHaste, Oldjim and Cookie. Beta-testers for the original A Pawn in the Game: Grayman, Bikerdude, Nbohr1more, Ppoe and Xarg Beta-testers for the original The Art of Revenge: Gnartsch, Obttorte, Lux and Jaxa. Everyone who helps me out in the Edtors Guild of this forum. Special shout out to Sotha, Grayman, Obsttorte and Bikerdude. Apologies if I've forgotten to mention anyone. The TDM team for providing me with countless hours of mapping and gameplay fun. Everyone who contributes anything to TDM to help make it the awesome mod that it is.

. THIEF'S DEN! Thief's Den is a re-release of the first Dark Mod tiny demo mission converted by greebo to work with the main Dark Mod release. Steal back your loot and incriminate the thief who double-crossed you! This was the first of the Thief's Den series in which you play Farrell. Read the notes below while you ... DOWNLOAD HERE. (3MB) Play time maybe 30 minutes to an hour first time. This FM needs Dark Mod Update 1.02 or later. This version has been modified to work with the Dark Mod released assets but is still essentially the same. The thief and thug models are updated and there is extra loot to find. IMPORTANT: If you already have the original stand-alone demo version of Thief's Den installed in the same Doom 3 installation then you must delete or move away the folders: doom3\thiefs_den and doom3\darkmod\fms\thiefs_den BEFORE you install this re-release. The original is still available as a stand-alone demo (needs Doom 3 but does not need Dark Mod installing) from http://wiki.thedarkmod.com/index.php?title=Thief%27s_Den

I've created a new topic (linking to this one) over here. Thanks for letting me know, and the warm welcome!

Hello everyone! I'm completely new to mapping and wanted to get some quick experience by making a tiny (10-20 minutes of playtime) mansion map over the course of an extended holiday week. Feel free to break this mission right over your experienced knees and tell me (kindly, please) how I should improve. You can find the pk4 here. (Google Drive link) Screenshots:

Hmm. The water surface effect in the cave seems to be broken in the new version?

I've read about this before here on the forums, even when the contest had just recently concluded, but reading about it in greater detail years later is certainly interesting. Thank you. It's a pity that it was mostly the marketing people who were involved on the Square Enix side, as I had the impression it was also the devs at EM that had played Requiem and all the other submitted missions and really liked them. I suppose it was as well, but the TDM team mostly heard from the marketing people. Yes, I wanted to note that as well. I even remember how the people over here in the TDM forums were sort of laughing at the fact that the results of the contest were favourable to TDM and had, in a sense, "proven" TDM as a worthy freeware successor to the Thief IP, with all the modding and mapping tools at one's disposal and so on, whereas Thief 4 or Thi4f or whatever Square Enix were calling it at that point, offered no such possibilities. The entire contest, while no doubt declared in good will and something I actually appreciated seeing, was such a self-own for Square Enix, ultimately to the detriment of them trying to bring back and market the reboot of an older IP. Even if Thief 2014 was a terrific reboot (which I doubt it would ever be), it would still have been hampered by people learning about modding being impossible, and looking to the trilogy and to TDM instead, to make new Thief-style stealth gaming content. Still, I appreciate they recognized the quality's of Moonbo's Requiem FM. Given many retrospectives I've seen over the years, gradually, on the 2014 Thief reboot attempt, one thing a surprising amount of them shared was noting how the game didn't feel cohesive in concept and execution, at any point. Not only not to the same level as the Thief trilogy, but also not even at the level when you consider it as an individual game, a new game on its own. Errant Signal, who's not some deep Thief fan, replayed the older games and played the reboot back when it came out, and made this exact observation already a decade ago. The reboot was just all over the place, in every department, felt clearly unfinished or rushed, and the most interesting story would be the behind the scenes at Eidos Montreal, on how mismanaged the entire project became over the course of several years. I think it's telling that, while even heavily discounted on GOG.com, Thief 2014 hasn't been selling well there, nor attracting much interest, whereas the original trilogy sells for figurative (and sometimes literal) cents on that same site - you can buy the whole trilogy for a smaller price than the reboot, which is kind of hilarious - and continues to have great sales and is considered one of the all-time bestsellers. Same here. I concur with demagogue that the actual Eidos Montreal devs behind Thief 2014, at least those who cared enough to make it at least somewhat presentable and playable - even if the actual game directors never got their act together and never decided on a consistent design apporach - those would have been much more interesting to be in contact with, even regarding the fan mission contest. The sad truth of the matter is that all too many big publishers these days, especially those formed through larger mergers, like the Eidos buyout by Square Enix, are often marketing-first, interest in developers, and veteran players and new players alike, second. I still remember the sheer amount of money spent on pointless external marketing for Thief 2014, all the while that reboot attempt never really coalesced into anything that felt consistent (rather than throwing everything at the wall, in a panic, hoping something would stick), and was also plagued by all manner of technical issues. Just an overall embarassment, and I'm not surprised that even very lenient-leaning game retrospectives of that reboot attempt. The fact that the Thief IP has been sold away to Nordic Games and Embracer in more recent years, with Square Enix no longer caring about it and other older game IPs, also says a lot. Given the Embracer Group's own woes and bad decisions, I'm not sure any new development team will ever attempt another installment of Thief, even if it was a second reboot attempt.

I'm happy to announce the release of my third FM: Year of the Rat. This is my first city hub map, focused primarily on story characters and environment. It's my most complex project to date, taking its fair share of effort to make which was a good learning experience. As an experiment I opted to use no scripts and rely solely on the default entities, as well as no custom assets apart from the map and splash screen hence the small pk4. It features a few special elements, such as factions that are hostile only when the player commits crime or a decoder lockpick used to open electronic doors. The beta testing thread can be found here, thank you everyone who helped find the most obvious problems. You play as a famous thief nicknamed Black Jack: A man who's pulled many crazy jobs in his life, only to be hired for an absurd and insulting task by an anonymous employer. The objective is pretty straightforward: Be kind to the mice and feed them some cheese! Your silly quest takes you to the Lantern Light district during the Lunar New Year celebration, a place where gangs and corrupt nobles do their dirty deeds together. What ulterior motives and unexpected twists could your adventure entail? While the most obvious problems were patched during beta testing, some issues can't be easily resolved due to the complexity of the entity setup and objectives, meaning you may encounter a few inconsistencies. Most notably surrounding AI, which may float above chairs and not react to alerts or oppositely send the whole map into a panic: This is mostly due to how the engine handles AI and alarms. The map is small since I wanted to add more detail without having to work on large areas, as such some places can feel cramped while the skybox may be visible up close. I'll be busy so further updates are unlikely unless I decide to add new content later... you're welcome to report any issues you encounter, but keep in mind that if something wasn't fixed it's likely known but difficult to address or due to engine functionality. Spoilers for objectives and secrets as follows: Download 1.2: Google Drive, Mega. Screenshots with minor spoilers for the various areas:

Afternoon So I have fixed all the remaining issue (that I was able to) that were reported and added some new bits as per some suggestions, enjoy. see the OP.

Very nice little mission for in between, straight forward gameplay and also a easy mission for new gamers. Congrats.

Lately I have started to play some of the more recent missions and some of these have lots of "own"/unique textures. Is it okay to use these assets (from released FMs) in one's own FMs? I'm referring to models/textures and sound etc, of course not chunks of the mission geometry or blatant plagiarism of readables etc. I guess some people have designed or bought assets for themselves but is it okay to use these textures/models as long as there is no explicit note in a readme etc, that opposes such "borrowing"?

Edit: Given the challenge from Wellington Crab below and looking at the license, I'm going to change this post. I'm putting my original post, which I'm now deleting, on a Google Doc here for reference, so you know what he's talking about. But I'll disown it now under scrutiny. I think some of the same points will come through, but they have to be put in the correct context with the TDM license as the baseline. The main question is what to do as a default when the potential re-user doesn't know the status of an asset. But to talk about that, you first have to talk about the baseline of the license. So here's the relevant TDM license text. So clearly if the author makes a different license explicit in their FM, then that other explicit license will apply. That's the baseline. It also adds this extra clause which goes beyond CC, "Without explicit permission from the mission authors, you may not redistribute, modify or reuse (parts of) these missions or the assets contained within them." This means FM assets are under a stricter license than the CC license mentioned above, with this extra clause. That also creates the default, if you have no information or unclear information, don't use the assets. This may add some practical complications in some cases when, e.g., if the author is using assets from a 3rd source and they mistakenly misrepresent the license (they think it's redistributable when it's really not), or if the author has made statements where it's a little ambiguous about when it can be redistributed, it's a partial statement (the default should probably be assume it's no unless very explicit though). I would say practically speaking, a lot of these issues can be addressed by asking the author directly for permission and getting explicit permission, or if they've made some explicit statement in their readme or a post or somewhere giving explicit permission, and if you can't find that explicit statement, it's all around best to not use the asset and just use some replacement that you know 100% is in the clear. The catch still hanging is when the asset is represented as redistributable when it really isn't. (The original mapper thought it was, but they made a mistake.) In that case, I think it's worth the mapper that wants to use it to do a little of their own due diligence to confirm that it's really redistributable, and again if it's not 100% clear, if there's any hints it might not be, it's best to not use it and use one you know is 100% clear to redistribute. Edit: Okay I guess there are a few more little technicalities. Because of the new clause, one could argue if the CC additions also still attach, especially Share Alike and Attribution (SA: you shouldn't change the license when you redistribute it, and A: you should give attribution in your readme). I think these may be implied, but even if it's unclear, it's common courtesy to do that anyway, and Share Alike probably includes that you have to get permission from the original author, not the redistributor, or if they modify it, both. Just try to be in good faith & respect everyone involved. Another possible little technicality is one might try to distinguish old FMs before the new clause and new ones after (do the old FMs also get the new clause), but anyway aside from the license, it's also probably fair to say it's TDM policy, so it's good to apply it to all FMs no matter what.