Search the Community

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.

I was able to reproduce this in 2.12 beta as well as 2.11. Start mission setviewpos -5727 974 292 24 -57 0 Wait for new objective setviewpos 3795 5676 -3164 18 160 0 Wait for objective complete Shoulder body setviewpos -1643 3574 -1903 4 180 0 Drop body on elevator platform Press elevator button Setting "logFile 2", I was able to capture some console messages before the crash. "MISSION COMPLETED" displays twice instead of once. I haven't had a chance to look further into this. WARNING:idClipModel::Handle: clip model 0 on 'bellero' (dc8) is not a collision or trace model WARNING:idClipModel::Handle: clip model 0 on 'bellero' (dc8) is not a collision or trace model WARNING:idClipModel::Handle: clip model 0 on 'bellero' (dc8) is not a collision or trace model MISSION COMPLETED MISSION COMPLETED ----- idRenderModelManagerLocal::EndLevelLoad ----- 0 models purged from previous level, 1031 models kept. --------------------------------------------------- Regenerated world, staticAllocCount = 0. Getting threadname failed, reason: No such file or directory (2) --------- Game Map Shutdown ---------- ModelGenerator memory: 133 LOD entries with 0 users using 2128 bytes. WARNING:idClipModel::FreeTraceModel: tried to free uncached trace model (index=0) --------- Game Map Shutdown done ----- Shutting down sound hardware idRenderSystem::Shutdown() ...shutting down QGL I18NLocal: Shutdown. ------------ Game Shutdown ----------- ModelGenerator memory: No LOD entries. Shutdown event system --------------------------------------

My own take on the beta process is that devs on one side commit to adding and improving features, but also to ensuring that the new releases are, as far as reasonably achievable, free of bugs and that the new features aren't broken on release. To balance that we have a general policy to freeze the code when the beta starts, where code changes should primarily be fixes to issues detected in the beta. Exceptions are made on a semi-regular basis for changes that go further if they can be justified. That's mainly the case when there's still enough time left in the beta to get the changes properly tested and reviewed, or the risk of breakage is low i.e. because you're adding, but not changing things. For example, I worked extensively on assets this release cycle and didn't manage to get all the work done before the beta, so I was still busy until about the middle of the beta phase. However, I prioritised my work so that asset changes were ready ahead of the beta, while asset additions (which won't break anything) were made during the beta. I also treaded particularly carefully when adding the new assets to compensate for their shorter beta testing time. I might not have been around as much lately, but I only heard of Daft Mugi's slew of patches when we were discussing whether the next beta build should be the release candidate, which gets released as-is if no significant issues are reported. At that point any changes will either prolong the beta testing phase, or carry the risk of not working as intended. The plan was to reach this point at the end of january (if this was not prominently communicated somewhere it was a mistake). Personally I definitely see the value in trying to accommodate as many of these changes as possible because they make TDM more attractive to Thief players, Daft Mugi is even standing ready to introduce them to the TTLG community, and it looks like they're fairly simple changes. However, prolonging the beta comes with its own drawbacks. One is that players and mappers are delayed in getting access to all the other new features. Another is that the beta phase is a relatively draining part of the release cycle for the devs because new projects are mostly on hold while the focus is on getting to a stable build. One of the ideas behind dev builds was to shorten the beta phase by spreading out the testing. Ultimately, we've designated Stgatilov as the project lead so it's his task to call the shots on how to balance these demands.

Beta 11 Fix finished-on state auto-update was unreliable Slighty improve scanner title/author detect Tags are now named some whatever regular-version-looking thing to force GitHub to put the newest at the top

The problem does not show up with all related dev builds. However, I cannot test with the last build (16854-10518), which I simply cannot start and get the report EDIT: As per our friend dragofer's suggestion, I made a blank script file in this build and removed the turrets from the WIP for a test. Then I can start the game and the mission and can save/load without problems. Summary: 16842-10488: no problems 16854-10518: cannot test (see above) 16854-10518 (modified scriptfile, no turrets) : no problems beta 1: problem appears

Yes, however, did more tests now. The problem already starts with the first beta build. When downgrading to 2.11, everything works fine.

@taffernicus Weird, I can't reproduce this. What version of DM are you using (2.11 or 2.12 beta)? And what platform? Thanks.

Lets test some bats! You'll need at least version 2.10b5 for testing (Dragofer added "animal_patrol_wait" which is needed properly behaving bats). I've tested the bats in my testmap and now they are ready to be let loose and tested in your maps to see if everything works as it should. Think about free roaming in (very) large spaces and small spaces. Also maybe have them follow paths, I didn't test that, and other things you can think of. The bat can by default be killed but has no ragdoll, instead it has a deathScript that makes the bat disappear with a visual effect. Maybe someone wants to make a ragdoll for it? Set spawnarg "noDamage" to "1" to have invincible bats. The blender files can be downloaded here: https://cdn.discordapp.com/attachments/815315205483397142/936191315845206046/Bat2.0_Blender_Files.rar The files needed to have bats in your map are in the attachment. There are 2 different sized bats and there is also a red test skin for both. I added the original tdm_mage_effects.fx file in the fx folder as an example how it works so you can easely make your own visual effect for the bats deathScript, if you wish. Update 2.01: Fixed aas,size,mins,maxs in the .def. Should work fine now, I hope. Bat2.01.rar

Yes, made a "standard" save game with a name and made quick saves in the latest beta.

I cannot load saves/quicksave in one of my project maps anymore. When starting quickload/load the mission loads a tiny bit, but crashes to desktop then. Can't say whether this was already a problem with the previous beta versions. Checked all other WIPs and it works fine there. qconsole.log Darkmod.cfg

No, you are right, that was my mistake. Thank you for asking that, cause this would have caused me problems during beta testing as every AI must be on the same team in this mission. Anyway, this happens when both are on the same time (tested three times, each time the same result): https://streamable.com/0n3yqg This is much better...but far from perfect. During the second try the other guy returned, but did not assist his friend.

New fresnel mod: https://www.moddb.com/mods/the-dark-mod/addons/fresnel-mod-212-beta-3 Probably not needed. I don't think anything in the previous base pk4 changed but I built it just in case.

The "peculiar lenses" don't work for me. Neither the ones I bought, nor the second ones I found in some tower. Every CInventoryItem (C++ object) stores pointer to entity in m_Item. In my case, this pointer is dead, i.e. it points to an entity which was removed some time ago. I guess for the glasses to work, it should point to the "atdm:xray_glasses" entity. The reason why it works for some people is either because the glasses don't die for them, or because they die but not completely and no other entity created afterwards takes its entity number. So the main question is: who kills the glasses entity and why? UPDATE: Just to add some more detail. I think I'm playing clean latest version with latest TDM beta. I got lost pretty quickly, so I completed all the objectives and explored most of the map first. Then I returned to the starting area and went to buy a sword. There I noticed the glasses, bought them and tried to use them instantly: they did not work. Then I explored some more and found second glasses in the tower + a piece of advice to use them. Now I have two items, but they don't work anyway.

Biker is working on a small update that incorporates volumetric lights and other fixes. He is asking for a few beta testers:

Bikerdude has made a few updates to this mission so we are looking for a few testers to make sure nothing was broken or overlooked. As far as I can tell this is ready for release but it's always good to ensure nobody encounters unforeseen issues. Lowend players are probably the best target just in case there are any performance regressions too. Mini beta:

"The Threepenny Revue" https://www.thedarkmod.com/missiondetails/?internalName=threepenny "I've been in the business of other peoples' valuables for as long as I can remember, so I'm no stranger to breaking and entering. But until today, I've never done a robbery on commission. I guess there's a first time for everything..." Randal Cartier, a local theater owner, thinks himself above paying protection money to the local gangs. You've been hired to prove him wrong. "The Threepenny Revue" is a first attempt at a Dark Mod Fan Mission. After playing TDM for ages and loving it, I wanted to try my hand at creating one of my own. As such, this is a short, simple, and relatively straightforward mission made to learn the ropes. The experience was very enjoyable, and I'm planning to work on another one in the future. In the meantime, I hope you enjoy this one. It's available now in the mission list, but in the event anybody wants or needs a backup source I'm hosting the files on my own site here. Special thanks to @Cambridge Spy, @thebigh, @Shadow, @wesp5, and @boissiere for Beta Testing and giving feedback, which helped enormously in ironing out problems in DarkRadiant

New script for mappers: my flavour of a fog density fading script. To add this to your FM, add the line "thread FogIntensityLoop();" to your map's void main() function (see the example in fogfade.script) and set "fog_fade" "1" on each foglight to enable script control of it. Set "fog_intensity_multiplier" on each info_location entity to change how thick the fog is in that location (practically speaking it's a multiplier for visibility distance). Lastly, "fog_fade_speed" on each foglight determines how quickly it will change its density. The speed scales with the current value of shaderParm3, using shaderParm3 = 1000 as a baseline. So i.e. if shaderParm is currently at 1/10th of 1000, then fade speed will be 1/10th as fast. Differences to Obsttorte's script: https://forums.thedarkmod.com/index.php?/topic/14394-apples-and-peaches-obsttortes-mapping-and-scripting-thread/&do=findComment&comment=310436 my script uses fog lights you created, rather than creating one for you. Obsttorte's script will delete the foglight if entering a fogfree zone and recreate it later more than one fog light can be controlled (however, no per-fog-light level of control) adding this to the map requires adding a line to your void main() script, rather than adding an info_locations_settings entity with a custom scriptobject spawnarg in my script, mappers set a multiplier of fog visibility distance (shaderParm3), while in Obsttorte's script a "fog_density" spawnarg is used as an alternative to shaderParm3 smaller and less compactly written script fogfade.scriptfogfade.map

This is an intereting discussion. So, could one of the mods please move this to a separate thread as to not derail the beta testing thread. As a developer, you spend about 80% of your time just reading code. So, optimizing for readability is very important. The more information you can gather just by reading without cluttering up the code (by needless comments) the better. Hungarian notation helps immensely to quickly prase the displayed code in your brain. Yes, your IDE will show the desired information as well, but a mechanical interaction with the code is required to show it (mouse over or similar). Also, often you are tasked to do code review on webpages that don't offer these nice crossreferencing features of your IDE. Some things are objectively bad, 'though, so the respective rules preventing those things should universally be followed. For instance, much legacy code is nested extremely because at some point in time, it must have been a rule that you only have one return-point in your function (probably a c-residual). Such code is exhausting to read ("what was the else-if-condition some 1000 lines ago leading to this else-case again?") and very likely contains tons of code duplication. Today, we have the rule to only use little nesting and short if-else-clauses, to make the code easy to read and debug. If I come accross such a nested legacy function, I refactor the shit out of that function while trying to understand it, just so the next person after me doesn't have to deal with that horrible mess again.

I know this is a bit late for 2.12 Beta 3, was planning on asking earlier but other things kept me busy. Latest TDM version allows toggling not just crouching but also walking and sneaking, which is a great feature and I prefer it over having to keep the key pressed. There is however one problem I keep running into: There's no indication as to when crouching or walking is toggled, the same way there is a HUD element for crouching. This can be a problem when you're sneaking from a nearby AI or stuck in a tight space, as you need to test which modes are used by walking around. Think there would be a way to make the symbols on the sides of the lightgem also change shape based on those modes, or another good way of making them clear? Also noticed an additional problem: Sneak and run are mutually exclusive yet get enabled independently. I often find myself not knowing why I'm slow, noticing it's because creeping was on, but then I disable it to find myself running and making too much noise so I have to hit the run key as well but a guard may have already heard me... you basically need to tinker with two keys to switch between the 3 modes (creep, walk, run). When both creep and run are set to toggle, would it be better if pressing either key would also toggle the other mode? Yet another confusing though less problematic aspect is the toggles not persisting between saves: I have running turned on, do a save, run into trouble and reload, then I'm suddenly slow again. Since crouching is persistent in saves, can the toggles for creeping and running do the same?

Great take on it and solution from what I understand! Will the normal Beta 6 contain this patch? If so it's easier to wait till then, otherwise if it's important I can of course give the test build a try given it doesn't mess with my normal install.

Playing Tears of St. Lucia, I noticed really bad framestutter in the church. It seems to happen around the builder guards. The game starts to micro freeze at a short interval (every second roughly). I don't know if this a beta or a mission issue.

Hello everyone, Bikerdude's made significant updates to this mission and it's now fully playable in 2.08. Available in the in-game downloader or Download here! We'll update the OP to reflect this. Thanks! “I usually welcome the shadows, a place of refuge for a master thief like me. However, there are dark places that even I fear. That place being the plague ward at the edge of town. Rumour has it that it was cursed by a pagan witch and its inhabitants died from an incurable plague..." Build Time: Update Build Time: Original version - 3-4 weeks. Updated version - 2 days  Credits: Flanders - Prebuilt maps and textures Readables – SirTaffsalot. FeildMedic - ghost begger (which I fixed and updated). Springheel - jack-o-lantern (gotta have them)  Thanks:- Special thanks to my beta testers: Flanders, SirTaffsAlot, nbhormore, Pranqster, RPGista, Thor, Xarg, Glyph Seeker, Amadeus, Garret42 & Bluerat.

The Builder's Blocks The time has come for my unusual gameplay fm to be released! Important! Please read this before you play the map. You will be playing a mini-game in this map. This mini-game alters the mouse sensitivity setting when you start it, so be sure to click on the 'leave' button in-map before exiting the game. Failure to do so means that you must reset the mouse setting manually and then restart the map. Since this is a map for the unusual gameplay contest the gameplay is unusual (not surprisingly). Do not expect a normal Dark Mod mission. Link(s) (post mirrors, and I will add them here): https://www.dropbox....ders_blocks.pk4 Screenshot of someone playing with a prototype of the game: A big thanks to my beta testers (in alphabetical order): jaxa nborh1more Obsttorte PPoe without whom many features would never have seen the light of day.

New report from the 2.12 beta thread: Added to the wiki