Jump to content
The Dark Mod Forums

Search the Community

Showing results for '/tags/forums/work thread/'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • General Discussion
    • News & Announcements
    • The Dark Mod
    • Fan Missions
    • Off-Topic
  • Feedback and Support
    • TDM Tech Support
    • DarkRadiant Feedback and Development
    • I want to Help
  • Editing and Design
    • TDM Editors Guild
    • Art Assets
    • Music & SFX

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

  1. I just recently became aware of this feature: https://wiki.thedarkmod.com/index.php?title=Particle_collisions_and_cutoff Unfortunately I completely missed it, as when I went to create weather effects in my FMs I just followed this (which doesn't mention it): https://wiki.thedarkmod.com/index.php?title=A_-_Z_Beginner_Full_Guide_Page_3#Rain_and_Snow The point of this thread is to a) make people aware of it and b) gather feedback from any mappers that have used it so we can get some mapper-focused documentation in the Wiki. The page above is great for background information about how it works, but as a mapper I really just want to know: What are the limitations of this (i.e. when should it be used and when shouldn't it be used)? Why isn't it the default behaviour? Why all this work to get it into the map? What built-in support for it exists (particle definitions, materials, etc). Do I need to create all this stuff myself? Texture layout vs. Linear layout: what's the difference in the end, pros/cons, why would I use one over the other... Why does it need a separate command (runParticle)? Can this just not be bundled in with dmap? A clear, step-by-step instruction on how to implement it in a map from beginning to end using a simple use case. Tagging some users who have relevant experience with this: @stgatilov @Goldwell @Amadeus
  2. Builder Compound Pack will help you create better environments for your Builder-themed map sections! The aim of this experimental package is to provide high-quality models, materials, and other assets that don't put a big strain on the idtech4 engine. This early version is slightly more bare-bones than I wished for, as some modular sets (e.g. the roof) proved to be too complex and unfit for general use. Don't worry though, the set will be updated and expanded in future releases. Tweaks – Arch door and arch with hinges models have been removed. They were just static models, not actual door entities, and they weren't super useful, e.g. hey couldn't act as visportal closing entity due to gaps and transparent parts. – Detail texture stage added to selected materials (mostly those you can get very close to). As you approach a surface, you should see a slightly grainy layer that enhances the details. New content – Door01 and door01_frame have been added to both models and entities. This is a basic door for this corridor section. By default, it's locked (with easy lock) and AI will notice if it's left ajar. You may want to disable the latter (set ShouldBeClosed to 0) if you have a section with many AIs and doors, as it will probably disrupt AI patrolling too much. The frame will work with walls that are 16 units thick. Both door and the frame will work with grid of 8 and smaller. You can use the grid of 4 to change the door position within the frame. Look for grooves in the frame model. First of all, launch the map to see a simple section that was made with these assets. Use the menu or type map bc in the console to start the map. Noclip though the north wall, if you want to get to the staging area and see all pieces used to make this section. General info and tips: Make sure you have Rotate func_* entities around origin (Ctrl+R) enabled (Dark Radiant top icons) to use models efficiently. All models have custom pivot / origin point placement to make them snap to grid and geometry really fast. If you have keyboard shortcuts configured for RotateSelectionX/Y/Z and FloorSelection, placing these models around the map will be a breeze. I also recommend having shortcuts for SelectNudgeUp/Down/Left/Right, so you can move models in ortho views without using a mouse. DR detects models in a weird way, e.g. if your model is one-sided, or has some faces turned back to the camera in ortho view, selecting and moving it around will be difficult. Using keyboard is often more seamless and precise. You can select a model in perspective view, and then move it around in X/Y/Z plane using keyboard. Optimal scale for tileable materials is 0.125. This provides good pixel density vs repetition. Materials are optimized to be used both with and without post-processing, and the default gamma of 1.2. In some cases, specular hotspot might look slightly overblown with post-processing enabled. Correct look without post-processing was the first priority. Same principles apply to using lamp. The main idea behind this set is that you can use simple brushes for walls and floors, and wall panels have proper offset, so you don't need to use special surrounding BSP behind them. You can place panels right where your walls are, and there will be no z-fighting or clipping. Assumed basic measure for a corridor is 192 x 192 (length / width), but you can go lower if you don't plan to use arches and metal doors. The smallest wall panel piece is 24 units long. Use brushes to create basic space, then adjust it to what you can make with wall panels (combinations of 24, 48, 96, 192 etc.). DR's measurement tool is your friend. Default grid for placing most pieces is 8, but it goes down with smaller / more complex models and setups. One special case is matching metal doors to arch with hinges, this needs grid of 2. That's a mistake on my part. I didn't think of better pivot placement until it was too late. The example map contains a "staging area" where you'll find grouped arch, hinges, and doors, so you can use that as a template. As per The Dark Mod license, you may modify this pack's contents, although I'd advise against it. Most textures are compressed in lossy DDS format and compressing them again will result in loss of image quality. If you want to make changes, need alternative versions of a model or material contact me first. I'll see what I can do. Last but not least, I hope you'll find this pack useful and fun to work with, as I had plenty of fun while making it I already have a long list of models and features to include in subsequent releases, but I'm always open to feedback and suggestions. Thanks! Credits: Springheel, Obsttorte, Spooks, nbohr1more, STiFU, Destined and other TDM Forum members: guidance, encouragement, and fruitful discussions Epifire: asset feedback and critique The Black Arrow: inscription texts Plans for upcoming releases: Corridor: - Fixing the wall panel collision model, so strafing along it isn't wobbly Done. - Roof modular set Done. - Making metal door an entity with proper sounds and open/close times. Done, made proper door instead. - Floor switch model/entity for metal doors - Window set Done. Roadmap: All work is on hold for now. I'm working on a small FM that will use some of these assets plus many more. Some of existing assets will get reworked too. All links are taken down, and I have no release date yet, sorry.
  3. I created the page: https://wiki.thedarkmod.com/index.php?title=Lightgem In the source I placed the following text: <!-- Page text made by forum user Fiver: https://forums.thedarkmod.com/index.php?/topic/22327-how-can-i-create-an-account-on-the-tdm-wiki/&do=findComment&comment=491145 --> Personally I think the page isn't really necessary because the info is already present under HUD.
  4. This is actually a rather old request that we encountered often shortly after going standalone in 2013. Hardcore GNU\Linux folks, especially those who use Debian, think that all open projects should use GPL v3 licenses with full "Libre" licensed content ( Creative Commons ). The goal is that open projects should be a shared resource that no single person or group regulates and can be used for ANY purpose without fear of prosecution or litigation. The primary motivation is "extreme paranoia". Any license restriction is seen as a potential trap that could unintentionally jeopardize contributors or users. For example: Imagine that I create a blog where I review darkmod missions and earn advertising revenue by visits. Through a very convoluted legal premise, the owner of non-free assets used in TDM could claim I owe them revenue since their license doesn't allow "any" commercial exploit of their work. Likewise, the owner of an internet cafe where the game is played might owe the asset owner their revenue. The ISP that made the asset available to it's subscribers might owe them too. The overarching theme is that copyright scope is not clearly defined and can be perverted to sabotage open projects. A fully Libre compliant project is immune to these risks. People who want their favorite projects to be easily available in GNU\Debian evangelize this type of license change. The problem is that most TDM contributors would strongly object to allowing their work to be used by 3rd party commercial projects, especially if those 3rd parties simply rebranded darkmod and sold it as a game in an app store. Even if that were a palatable eventuality, it would also make Embracer Group ( current owners of Thief IP ) more inclined to attempt a legal take-down of our project. A Libre version would need to be a fork that is maintained outside our community so that we can still clearly state that we prohibit all commercial usage. Debian and other similar distros need an easy way to allow users to install projects that are strictly non-commercial rather than forcing all open projects to permit 3rd parties to resell their work.
  5. It took awhile to get used to the size of this mission. The long loading times didn't help, but after passing a certain point, I get it now. However, I will say this - the AI is crazy on this map. I started, right? And the first thing I see - all guards going ape because some thug cut loose. I sat in the dark corner, for like ten minutes, waiting for them to calm down, because I figured I should look around for loot (I only found some of it much later when I was returning here after finishing the mission) The same thing happened later, when I needed to pass an abandoned mansion. I waited for the epic battle, instead it was a massacre, but like an idiot I saved AFTER I left the tunnel, not before. So I couldn't reload and see if next time the battle will go differently. (Am I crazy or do leather thugs spawn after a moment?) I had to use up all gas arrows to pass that part because they kept trimming the bushes. The evidence part got me confused because I dropped a piece of evidence, but it didn't count, so I dropped everything that said evidence. Only then it counted, but later, as I was still hunting for loot, I finally remembered that I had a vent key and came looking and found yet another piece of evidence?! Finding Smythe was funny, because he kept saying "Show yourself" and the moment I did... I gathered skulls before I was prompted to, but Edgar... I don't get it. edit: Those glasses, tho. Holy crap, I did not expect to see "actual glass" in this game. The hidden room took me ages to find, despite TWO blatant hints. But I was sleep-deprived at the time. There was one snag, and one confusion that I had. The snag was that, when I finally reached the alchemist, the note told me to use the vent, right? But... I couldn't open the second vent in his lab. I don't know which key I was missing for that. So I figured - I could just go back the same way... and game CTD. I walked there again - CTD. I noclipped through that locked vent, killed the spiders, and tried to open the doors to my left (got spooked by friendly guards) - CTD. Only when I walked right and up the stairs did I finally progressed. Not sure what that was about. The confusion, however, came from Builders. I knocked out most of them in the Builder's outpost, but when I dealt with the Mr. Nom-nom-zom, they vanished. I guess they needed that many people to dig him out of the spider outhouse? (Never found the second news flash either) I still somehow missed 3.5k, and noticed that lights kept poking through walls (there is a piece of light pointed at doors leading into the inner garden of Builder's outpost that nearly got me killed a few times) Overall, however, this was an impressive piece of work.
  6. I liked the atmosphere, build up of tension, without actual scares. Although, when I started, and got into Captain's quarters... I read the readable and thought.... Okay, so there are 11 sailor thugs, only to find a lot more in the house, and wonder what the heck. Maybe I didn't scroll it? I liked the dialogue too, but I was a little disappointed that the interior didn't match the description, it wasn't until I returned for the first time did it change to match. And I expected some sort of ghost or ghoul to pop up. Then the transition, and when I went looking for the spot, I noticed the way it was highlighted. =D That was pretty funny TBH. Then - Two missions in one was a bigger surprise than I expected. How does it even work? The only thing I don't get is the finale, but I suppose that's the point.
  7. As soon as I started, I was hooked. Intro, our thief's reactions (can never have enough of those), cutscenes (YES!), dialogue with NPC's... It was great. And the further I went, the more it opened up. Overhearing conversations, a freaking tape recorder?! I found a very sus table in the pantry, and thought that maybe I need to light the candle, which did nothing. But you gotta admit, that looked like a puzzle of sorts. Turns out I was overthinking it... I too completely missed the hidden "chest" with the second book, only after coming here did I went back and found it. , but it's sad that Mage's readable turned out to be only partially true. =D Thank you for your work and release!
  8. @MirceaKitsune - have you raised a bug report for this particular problem (searching in the wrong place if shot by an arrow)? I think I have found the cause of it and can write it up in the bug tracker. In short, I believe the intended behaviour is that the victim is supposed to search halfway between him and the shooter (presumably chosen because he shouldn't really know where the shooter really is) but the code that sets this point gets overridden shortly afterwards by code that sets the search point to his current location. It's quite instructive (if you like that sort of thing) to read up the various bugs reports on AI behaviour that have been raised down the years. In particular, bug 3331 contains a number of fixes to problems similar to those reported in this thread.
  9. Okay: I replayed a few missions with difficulty set to Hardcore which is the maximum setting. Nothing obvious changes: All of the same issues persist, including the ability to beat up a guard with no reaction by climbing on a table in total darkness. All that changes is guards running to your location a bit more accurately when seeing you from a distance, attacks however don't count as sight. I decided to record a video for this thread to show my point, Crucible of Omens: Behind Closed Doors. What's happening here: While standing on a ledge that should be reachable by a stair, I shoot the guard in the back as he's walking away. His first reaction is to run down the stairs in the completely opposite direction. A few seconds later he comes running back up, only to go in a crevice at the other opposite end of where I was located. By sheer chance he heads somewhat toward my initial position, after which he runs down the stairs again. He finishes his alert state far away, looking for me far at the bottom of the stairs where I clearly wouldn't have been located. How this could have been better: The guard was shot in the back, it doesn't take a genius to tell that's where the arrow came from. He should have picked random positions in a cone originating from his view and facing toward me at the moment of the shot: He shouldn't come running to my exact location which would be both difficult and unrealistic, but should have searched in my general direction such as the wooden door to my right.
  10. In case anyone decides to pursue this further, here are a couple more references: https://discourse.gnome.org/t/pointer-warping-on-wayland/9197 https://gitlab.freedesktop.org/wayland/wayland-protocols/-/issues/158 Seems like this feature is also common in PCB design software. The "correct" solution would be to use Wayland's pointer locking interface and relative mouse events, which is essentially what the FreezePointer class accomplishes by continuously warping the pointer back to its original location. The complication is that the way it works now all goes through wxwidgets which then goes through gtk3 on Linux. To fully implement this, I think someone would have to: Create a platform-specific alternative to the cross-platform FreezePointer that we have now Make sure it's only called on Wayland, and only if the pointer locking API is available Work your way through the wxwidgets / gtk3 layers to get hold of the native wayland surface and pointer handles Reconcile the Wayland mouse events with the mouse events received by wxwidgets If someone was motivated enough to pick this up, it might make sense to try to build this in at the wxwidgets level and try to get it accepted there. It would help keep platform-specific code in the right place and also make a couple other projects happy.
  11. I use hotkeys for filters, yes. If I had to access the menus every time I wanted to hide/unhide things I'd go insane. I wouldn't toggle them on/off nearly as much as I do, and my workflow would be slower and more limited. As an example, I very often toggle visportals on/off for adjustments, or func_statics for inspecting world geometry. And sometimes I have to turn off all filters so that I'm 100% sure I'm copying or moving geometry properly, without leaving behind hidden clips, triggers, visportals, nodraws, etc. And then I have to re-hide all the things I like to keep hidden. I don't know about your workflow, but 99% of the time, I keep collisions, shadows, sky, visportals, triggers, nodraws, and also caulks, all hidden and out of my way. With hotkeys I just press alt and a bunch of keys in succession, and it takes me seconds. With menus it would take a while. There's no way I could ever not use hotkeys. I'd go completely nuts. No, I'm saying they require more work than just simply creating a layer and putting stuff in it. And if you don't put a hotkey on it, it's also more work to use. I'm not saying you can't use them for that. I'm saying they're not the right tool for it. EDIT: Keep in mind that the example above is just one example. There's all sorts of things you might want to use that functionality I suggested for. And again, layers are map-specific. If you setup filters for layers (is that even really possible?), then your filters menu will grow, and become polluted with junk that only works on certain maps. And the more you do it, the worse it gets. Back when I could used that in Hammer, I always had quite a few layers per map that controlled visibility of specific groups of objects. When you can just go wild with it, you go wild with it.
  12. Surrounded by greedy noblemen and treacherous siblings, Lady Kamila Leicester gets more than she bargains for after acquiring an ancient tome and performing the dark rituals within. Bikerdude, Wellingtoncrab, Dragofer, and I proudly present Grayman’s FM “Seeking Lady Leicester.” Notes - TDM 2.11 or later is REQUIRED to play this mission. You can get the latest TDM version via the installer or here. - Seeking Lady Leicester was originally a work-in-progress given to the Dark Mod community per Grayman’s wishes after his passing and was initially adopted by Bikerdude before Dragofer, Amadeus, and Wellingtoncrab joined to complete the FM. -This FM does NOT support any unofficial gameplay patch or mod. The use of such a patch and/or mod could break things in this FM. You've been warned. - "Story" subtitles are available for this FM. Simply go to Settings --> Audio and select "Story" or "On" for the subtitles setting. - This FM may be more hardware intensive than normal. LOD settings can be set below "Normal" to improve performance on low-end machines by disabling certain features. - This FM implements the func_peek mechanic, allowing players to peek through any door that has a keyhole on it by leaning forward. PLEASE NOTE: This function has been known to cause crashes for a small number of players in the past, likely due to using the 32-bit version of TDM. At no point in this mission is it required to use the func_peek mechanic; it is purely optional, so feel free not to use it. Download Version 1.1 This FM is available for download via the in-game mission downloader, or here via Google Drive. Promotional Screenshots ThiefGuild Thread Credits A big thanks goes out to Noelker and Goldchocobo for their wonderful voice work with the briefing and conversations, JackFarmer and itsPapiD for their fantastic briefing video, and nbohr1more for his story contributions and writing one particular gameplay feature that I won’t spoil here but you can read about in the readme.txt. An even bigger thank you goes out to our beta testers: nbhor1more, Daft Mugi, Silverwolf, Havoc, Datiswous, Cambridge Spy, Aluminumhaste, Thebigh, Ate0ate, Acolyte6, Kalavi, JoeBarnin. Thank you all very much for your fantastic feedback and tireless efforts as this FM evolved throughout the course of development! Asset Credits - Arx EOS’s Fish - Epifire’s models - Kingsal's Assets and Textures - WellingtonCrab’s assets and textures - Obsttorte's frob loot script - ZergRush's custom Grayman painting ===================Rest In Peace Grayman. You are missed=======================
  13. It's arguably quite a bit more work than just creating a layer and adding stuff to it. And then you'd have to also add it to a hotkey, to make it practical. Filters are good for things you want to keep as groups forever, not really for temporary or map-specific groups. One other problem with filters is that you can only have so many hotkeys. Any filters that aren't attached to hotkeys aren't practical to turn on/off, because you need to access the menu. (Ideally, filters and layers would be unified under the same system, because they are actually the very same thing. I went into this in more detail here. I'm not expecting that to be done in DR, though. It might be a lot of work. But I could be wrong.)
  14. New report from the 2.12 beta thread: Added to the wiki
  15. Oh well, I guess that rules out any kind of mouse grabbing behaviour that will work on Wayland desktops. I'm not sure what the alternative is. Some kind of on-screen widget that you can click and drag to rotate the camera, like a sort of circular scroll-bar?
  16. Yeah, I guess I didn't consider making a new entity for future mappers to implement in their future maps when I responded to you (sorry!), but that is not a bad idea. The changes should be done in a way where it wouldn't affect older FMs, and it would be a fair chunk of work. I actually have a few breakable lights in my WIP, although they are kinda glitchy and far from perfect.
  17. There might be another way, or at least it's what I thought of as a non-developer: Use a different way to transform mouse movement into camera rotation or viewport offset. Is there no alternative to calculating the distance from the pointer to the window center before resetting the pointer to the middle? There must be other mouse look implementations that could work. Most obvious alternative: We can detect how much the pointer moved on the screen compared not to the center, but to its previous position wherever that may be. While of course still trying to lock it in the middle, but if that fails at least it doesn't cause the view to go crazy: The only issue then will be the cursor reaching the screen edge and having to be re-engaged so you can keep scrolling in that direction, which is also a big annoyance but comparatively less bad and not as noticeable unless you do long-range movements in one go. Any reason why we couldn't give this option a try?
  18. In the first post of the other topic Geep proposed: Then Stgatilov's answer: But I think applying subtitles in different languages shouldn't be too hard I would think, but I don't know how the current translation system works. The engine should apply the correct subtitles based on the applied language setting, this doesn't need a whole new language system I think. Not sure who's going to write those subtitles though. I can only do Dutch and English and nobody needs Dutch I think. I suggest further discussion of this to take place in topic https://forums.thedarkmod.com/index.php?/topic/21741-subtitles-possibilities-beyond-211/
  19. Oh my, I completely forgot about this. @OrbWeaver I actually got DR to work fine with png images and obj models. Seems like it supports them fine, as long as the mtr files are correct. Greebo helped me out on discord. Also got it to be compatible with Godot's importer plugins by exporting as Quake 3 format (as long as there's no complex geometry, like patches, etc, it seems to work). The only reason I didn't keep using DR, is because DR doesn't seem to store the game's path properly. When you switch game setup, the path remains the same, so you have to manually set the path every time you switch project. I tried having separate portable DR installations for each project, but it seems DR isn't properly portable either, as the game setups are also stored globally. So that didn't work either.
  20. Some folks have been asking about the new tdm_show_viewpos cvar and screenshot_viewpos command, so I thought I'd make an thread about it as a reference. The purpose of the cvar is to show the viewpos on the player HUD, and the purpose of the command is to add the viewpos to screenshots in order to help with troubleshooting and beta testing. Bug tracker: https://bugs.thedarkmod.com/view.php?id=6331 tdm_show_viewpos tdm_show_viewpos is a cvar to show/hide the viewpos on the player HUD, which can be set to the following: 0 --- hide 1 --- gray font color 2 --- cyan font color screenshot_viewpos screenshot_viewpos is a command that takes a screenshot with the viewpos added to it. screenshot_viewpos screenshot_viewpos <gamma> screenshot_viewpos can be typed at the console or bound to a key. The "gamma" is an optional argument, which as of 2.12 Beta is the r_ambientGamma value. Some mission authors prefer to have screenshots (from players) that are brighter, so they can see what is in the screenshot more easily. Setting the "gamma" argument is a convenient way to temporarily adjust the gamma just for the duration of the screenshot. For example, I have the following bound: bind "F12" "screenshot" bind "F11" "screenshot_viewpos" bind "F10" "screenshot_viewpos 1.3"
  21. Hello everybody. The Beta Testing subforum said to recruit testers before making a thread there, so I'd like to recruit first and then make a thread there if anybody's willing and interested. I've just finished work on my first Fan Mission, "The Threepenny Revue" and I'd like to get outside opinions on it. I have a zip file with the directory and files that can be dumped into the /fms/ directory and it should play, but it hasn't otherwise been packed up properly yet. The files will be available on my own site, and I'll post a link to it in the Beta Testing thread if there any takers here. I'm still finding my legs with the process of sharing FM files, so I might mess things up but hopefully it works. Thanks in advance.
  22. I wouldn't normally do it, but I put a member on my ignore list because the posts were upsetting. Very upsetting. I enjoy TDM and DR and enjoy the forum, except for the one person. Usually I check the forum out as 'guest' but will auto sign-in so there's no trace of the ignored person's post, mentions, and all of it. But it doesn't work. And I'm outa here if I have to suffer any more of that.
  23. It doesn't work at all, v2.09a and the latest dev build. If I input eg. "r_showShadows 2" nothing happens, then when I input "r_showShadows" it gives the info that the value is currently set at "2", that default is "0", along with info on how it should work.
  24. Congratulations on your mission, hard to believe its your first, well done. Thanks for all your hard work, I hope to see more missions from you.
  25. Hidden Hands: The Lost Citadel ============================================================== Title: Hidden Hands: The Lost Citadel Filename : hhtlc.pk4 Authors: Jack Farmer with Amadeus & Joebarnin Date of release: 18.09.2020 Latest version: 5 (released June 2021) EFX: Yes ============================================================== Hidden Hands series: I - Initiation II - Vitalic Fever III - The Lost Citadel ============================================================== Available via the Dark Mod Mission Downloader (Version 4) ============================================================== Jack Farmer: Mapping & drafts Amadeus: Editing and revising of all texts for readables, narration and dialogues, testing of gameplay and gameplay mechanics, all alpha testing & performance optimization joebarnin: Beta testing lead, debugging and debugging reports Beta testers: Krilmar Joebarnin Cambridge Spy manzanita-crow Shadow Voice actors: New Horizon: The educated Builder & Brother Gilbert (Briefing video) Goldchocobo: The naive Builder, guard (A union of its own) Jedi_Wannabe: Two guards (Of monsters and master guards) AndrosTheOxen: Jonus, guard (A union of its own) Boy Lag: Guard (Evolution of the peasants) Malasdair: Narrator (Briefing video & in game comments) Special thanks to: - Springheel, Sotha, and Fidcal for the tutorials - VanishedOne, HMart, Destined, Grayman, Joebarnin, Dragofer, demagogue, AluminumHaste, STRUNK, Geep and ERH+ for patiently answering my questions and solving in-game issues - All voice actors & beta testers for their great support - All others not mentioned here who answered my questions in the Newbie thread or via PM Pilfered items: - Setup for the main menu animation originally developed by Goldwell for "Snowed Inn" - Portal sky with trees originally developed and arranged by Dragofer for "Down By The Riverside" - Selected cliff sections originally developed and arranged by Dragofer for "A Perilous Refuge" - The scary, red-eyed Builder ghosts that have been originally developed by Bienie for "Longhorn Lodge" - Floating boat set-up originally developed by Bikerdude for one of his missions Contributors from the Inventor's Guild: - STRUNK created a prefab (S.T.A.R.S) used for various puzzles and mechanical items, he also helped with models - Dragofer supplied the experimental func_mover entity (modified by STRUNK to fit the mission purposes) - Joebarnin provided the script alteration for the mechanical locks - Grayman adjusted the switch/door mechanics for all sliding doors and fixed several AI problems Additional ambient sounds by gigagooga All other new ambient tracks and sound effects produced and mixed by Jack Farmer Explosion sound taken from freesound.org produced by tommccann Drowning man sound taken from freesound.org produced by muses202 Engine room machine sound taken from freesound.org produced by Astounded Electric zap taken from freesound.org produced by Joel_Audio Briefing video by SirSmokeALot "Walk On Roses" (title screen reprise) RC Deickler - Drums & loops R. Recum - Keyboards gigagooga - Additional ambient outtakes This mission is dedicated to all past & present Dark Mod and Dark Radiant contributors - thank you for all of your hard work over the years. ============================================================= Listen to another crazy inventor and learn more about his sick brain! Marvel at the latest inventions from the Inventors Guild! Sneak through long forgotten ruins and face (yes. I know, once again) the unspeakable evil! Show the undead that the living are not to be trifled with! Solve puzzles the complexity of which would even melt the brains of Nobel Prize winners!
×
×
  • Create New...