Search the Community

https://store.epicgames.com/en-US/free-games Epic is giving away "good" games, probably a summer event, each one is a mystery before reveal. Starting with Dragon Age: Inquisition - Game of the Year Edition. Steam has this until May 27: https://slickdeals.net/f/17490963-machinika-museum-pc-digital-download-free https://store.steampowered.com/app/1507190/Machinika_Museum/

It seems like I missed this mission somehow. I'm down in the crypt with the slow match, but I can't get the torches on each side of the gold statue to light. How do I remove the gold statue?

I hope that is not the new TDM version. https://forums.thedarkmod.com/index.php?/topic/20784-render-bug-large-black-box-occluding-screen/

As far as I know Blow only works on small flames that mostly can be extinguished by Frob in my patch anyway. Actually the fact that the core developers wouldn't include pinching out oil lamps compared to candles, which is rather illogical to me but was always excused by not breaking existing missions, was the main reason I made the patch in the first place!

I think wiki pages for these files would be useful: mainmenu_custom_defs.gui mainmenu_briefing.gui mainmenu_background_custom.gui I think those are the only files with official support for editting.

The topic says it all, the error goes away when Bloom is disabled, otherwise it looks like this in the training mission for basically all items you can take:

I have numbered your suggestions because I find it hard to multiquote here. As for calling blow and whistle tools and not skills, this was just done to not confuse the player with another inventory class. Also what would the Numbers scroll be? 1) Is there an advantage of your method vs mine? If the result is the same, nothing needs to be changed. 2) I don't know what you mean with blinking being out of sync. Should all loot blink in the same rhythm? 3) It removes the need for slow matches and flints which mission authors might provide for their stories. 4) This is what it looked when I copied it from you, but I had to rename it to avoid duplicate definitions!

Regarding the Blow I would argue that if you need a backup plan perhaps the main plan isn't that good after all. Maybe the main plan simply needs a little more work and maintenance. Besides, players using the Unofficial Patch can extinguish almost everything with their hands except that element there, for which they need a tool? Odd.

The question is, what do you want the Unofficial Patch to be? Then do just that. Players shall judge. I am fairly sure, yes. What's wrong with some free virtual relighting ? Since you are interested in some skills what we can do to avoid duplicates is to adopt the same basic entities with the same basic properties. That way players using only the Patch will get your version but players using both the Patch and the Modpack will get a single instance (whichever mod that wins). Here is an example for the Whistle. tdm_playertools.def Go from: // Whistling sound to distract enemies, added by wesp from snatcher entityDef atdm:playertools_whistle { "inherit" "atdm:playertool" "editor_usage" "Don't use, gets automatically spawned at the start of the map" "scriptobject" "playertools_whistle" // changed by wesp "inv_category" "#str_02394" // Tools "inv_name" "Whistle" "inv_icon" "guis\assets\hud\inventory_icons\whistle_icon.dds" // changed by wesp "inv_map_start" "1" } To: // Whistling sound to distract enemies, added by wesp from snatcher entityDef mod:playerskills_distraction { "inherit" "atdm:playertool" "editor_usage" "Don't use, gets automatically spawned at the start of the map" "scriptobject" "playertools_whistle" // changed by wesp "inv_category" "Skills" "inv_name" "Whistle" "inv_icon" "guis\assets\hud\inventory_icons\whistle_icon.dds" // changed by wesp "inv_map_start" "1" } tdm_user_addons_wesp.script Go from: void user_addon_init_wesp() //If any of your addon scripts need to be initialised at map start, add their init function here. See the line that has been commented out with // for an example. { entity blow = sys.spawn("atdm:playertools_blow"); // added by wesp entity whistle = sys.spawn("atdm:playertools_whistle"); // added by wesp statistic_message_init(); // added by wesp thread frob_details(); // added by wesp tdm_frob_lock_init(); // added by wesp tdm_chest_sounds(); // added by wesp tdm_unlit_lamps(); // added by wesp sys.waitFrame(); // contingency in case no addons are specified } To: void user_addon_init_wesp() //If any of your addon scripts need to be initialised at map start, add their init function here. See the line that has been commented out with // for an example. { entity blow = sys.spawn("atdm:playertools_blow"); // added by wesp entity whistle = sys.spawn("mod:playerskills_distraction"); // added by wesp statistic_message_init(); // added by wesp thread frob_details(); // added by wesp tdm_frob_lock_init(); // added by wesp tdm_chest_sounds(); // added by wesp tdm_unlit_lamps(); // added by wesp sys.waitFrame(); // contingency in case no addons are specified } See if that does the trick, and if you like it.

WOW, what a pleasant surprise! I expected this day would come but not this soon. There they are :) Here is an initial, quick assessment. Currently the Modpack loads last, therefore it takes preference. We can test the other way around at a later stage. tdm_frobactions.script No conflict detected. The Modpack's version takes preference and it apparently works as intended. The Patch changes some chest sounds in a separate script at mission start but then the Modpack overrides these sounds on the fly. Blinking items Threads from both the Modpack and the Patch run in parallel throughout the mission. I don't notice anything unusual except that sometimes the blink is out of sync. The reason is that something fishy is going on between milliseconds 16 and 17 in Uncapped FPS mode. In v4 of the Modpack I set the wait time to 15 milliseconds to avoid the issue and you should do the same in the Patch: tdm_froblock_frobability.script > mod_frob_highlight_blinking() > sys.wait(0.015) Containers Threads from both the Modpack and the Patch run in parallel at mission start. I honestly don't know what the game is doing in this case but the outcome apparently is not negative. No issues detected. Body names Threads from both the Modpack and the Patch run in parallel throughout the mission. I don't notice anything unusual but most probably names are being displayed twice. Shock / Electric mine No conflicts that I can detect at a glance. Whistle No conflicts that I can detect. Players however end up with two different versions of the same feature in different categories. Blow No apparent conflicts. Players however end up with two different versions of a same feature in different categories. This one is interesting because the Patch introduces "extinguish on frob" on small candle sources and players are spoiled by options now.

The project to round up viable orphaned translations is mostly complete now. https://bugs.thedarkmod.com/view.php?id=4726 Since Darkfate has their own translations it took awhile to merge the older translations with the darkfate formatting since they generated new string numbers from scratch. A few missions are so radically changed that the old translations are practically worthless now ( and some Darkfate translations are also incompatible with the latest mission versions ) but most of the work was salvageable. I added a "Translation Pack" column to the Missions wiki: https://wiki.thedarkmod.com/index.php?title=Fan_Missions_for_The_Dark_Mod all entries marked with "Yes" are working translations that use Darkfate's translation design ( includes xdata, GUI and Map files if the author didn't perform localization changes in their own mission pack ). Sadly, these changes do not show in the mission downloader list. You will need to delete mission_l10n.pk4 files from the darkmod/fms/mission_name folders to acquire the new translation packs that "actually work". Not all mission packs contain all languages. Mostly you can count on Russian being in there, but a good percentage have German and Italian strings too. French, Polish, and a few other languages are represented but not very broadly. Hopefully now that the packs work other contributors will add more language strings. Mission administration details: Going forward, it would be courteous if the mission admins ( like myself ) would diff the map files when new mission updates are supplied and replace all the objectives, inv_name, pop-up messages, and shouldered names in a copy of the new map file with the previous string codes then copy that file to the map folder in the translation pack folder. Ideally, authors will be encouraged to run their missions through the converter so only new strings need be added to the packs but not everyone likes that workflow and how cumbersome it makes future edits to the mission.

Do you really want to try? I'd suggest looking at idSoundWorldLocal::MixLoopInternal. That seems to be the only place where effect is found by area index, then by area name, then default. If you manage to add a member like idSoundWorldLocal::listenerEfxPreset and ensure it is set properly, then you most likely can pass the preset name here (perhaps via something like idEFXFile::FindPreset). In my opinion, the location spawnarg should get top priority. If missing or empty, then the ordinary approach with .efx file works.

I wasn't aware that you changed the whistle so I am probably using an old version which I like pretty much. I just renamed the internals in the vain hope that our mods can be mixed that way, but there are too many other overlapping definitions. P.S.: I looked closer into it and it seems there was only one other overlap which I fixed by renaming, so now the patch and your modpack can be merged with each other ! As you use x_ as prefix your features will override mine though ...

I have never been truly satisfied with the Whistle: it was either too much or too little. The latest version (v4) is so far the best (imho) although I still disagree with some things. Are you up to date or are you keeping a previous version for some reason?

I just noticed that the sounds of hitting something with the blackjack or the sword seem not to be audible to NPCs. On the other hand hitting something with an arrow does, as fas as I know. Is this intended to avoid punishing the player for e. g. a missed hit during knock out or is this an oversight that should be fixed?

Maybe it's possible to make a script that extracts all the info_locations from the map file and creates an efx file from that in the correct format (run again to update). Then you can simply fill it in. Possibly you could also edit in DR the efx-data as a fake spawnarg for that info_location entity and make the script write that to the efx file. This might also be possible via a script/plugin inside DR.

I made a small update including the fixed fonts by Geep and also brought Snatcher's Whistle back, because a) I noticed that hitting something with blackjack or sword has not the same effect and b) the name now doesn't look bad anymore because of the font fix .

@stgatilov @nbohr1more I'm wondering if it would be possible to get this implemented for 2.13? I'm really not loving the EFX files - it's way too easy to miss/forget locations and just a general PITA. I am even considering offering to help implement - any reluctance on my part is purely down to lack of confidence. But with some hand-holding I could possibly accomplish something that isn't a total disaster. Maybe an alternative is to have a feature that allows DR to manage the EFX preset in the EFX file? Basically what I'd like is to be able to manage everything related to a location entity in the one place, preferably in DR. Not sure if that's ever been considered? @greebo?

Thanks for the replies, particularly the reference to the embarrassingly-obvious "Music & SFX" subforum just below this one. I just like the music: I don't have any illusions about creating a fan mission. I messed with Dromed way back in the day, and I remember what a black hole of time and sanity it was.

So path_follow_actor actually DOES work if you want it to follow the player. You just need to target the player entity dynamically in game. It doesn't work if you target the player_start entity. I can't remember if that's what people were doing (or even if that's what I was doing), but that won't work because the player_start entity and the player entity aren't the same thing. You can use a atdm:target_changetarget entity to do this, or a script: $path_follow_actor_1.addTarget($player1); Both can just be triggered by another path node, a atdm:target_callscriptfunction, whatever. Also you need to add the player target to the path_follow_actor node BEFORE the AI gets to it. If the target gets added after the AI reaches that node, it won't work. Video where the AI hits a node that triggers a atdm:target_changetarget entity: https://drive.proton.me/urls/A3DJW5EYFM#0WgYnCVOU6nv test map attached as well. EDIT: I have no idea why just manually setting 'target' 'player1' on the path_follow_actor node in DR doesn't work. I'll try to look into this. UPDATE: It appears the the player1 entity simply isn't there during initialization when the path_follow_actor's targets are evaluated. As a result, the 'actor' is null and the node does nothing. I didn't mention it before, but when I used the script method I just stuck in the map script's main function like so, and this works too: void main() { sys.waitFrame(); $path_follow_actor_1.addTarget($player1); } UPDATE 2: Wiki updated: https://wiki.thedarkmod.com/index.php?title=Path_Nodes#path_follow_actor path.map

Stone 24pt Font Upgrade, May 9 2024 Interim Release This first release just clears away some of the low-hanging fruit, while buffing the new datBounds program. In summary - stray mark next to W removed poor spacing of J and AE improved 6 characters got accents added. The download is made up of: .dat and 2 .dds files, for distribution/game inclusion .ref [with changes annotated] and .xcf [master source GIMP project, including datBounds layers] 2024 May 9 Stone 24 Interim font update.zip The changes were also doubled-checked using the testSubtitlesANSI FM. As this work continues, with an interim release approximately monthly, characters to be fixed will be chosen seemingly "at random", but actually due to layout considerations... you don't want to know. They'll all be done eventually. Details of Improvements:

For free ambience tracks it's as Freky said: you look around on the internet for tracks with the appropriate license to be included in your FM. Fortunately, you likely don't even need to bother doing this as a beginner as there's an entire "Music & SFX" section of the forums full of good ambient tracks for you to use if the stock tracks do not meet your fancy. You might also be interested in Orbweaver's "Dark Ambients", which come with a sndshd file already written for you.

I like this very much. It goes in line with the idea that players become more creative when they can alter the world around them temporally instead of permanently. Each time is a different challenge. It will never happen globally, though. Good news is that we have Shadow Arrows.

Thank you for the kind words. I don't know who made the track. It comes with the core assets of the mod. So it should be possible to find the composer.

IP over Avian Carriers with Quality of Service https://www.rfc-editor.org/rfc/rfc2549 Mini ponds are 'tiny universes' of biodiversity for gardens and windowsills : https://www.bbc.com/future/article/20240423-how-to-make-a-mini-wildlife-pond