Jump to content
The Dark Mod Forums

Aosys

Member
  • Posts

    277
  • Joined

  • Days Won

    8

Posts posted by Aosys

  1. So I've been on-off working on various missions of some description or another, and during the course of doing this I've been thinking about the process of bringing an FM together from start to finish. That is, maybe less the technical side and more: how does one go from an idea, to a fleshed-out concept, to a final product? There is some good stuff on the "Mission Design Tips" wiki page (http://wiki.thedarkmod.com/index.php?title=Mission_Design_Tips), but I feel there's more to the mapping process that can be explored and expanded upon. So I was wondering, how does everyone here do it? Is there a particular mapping method(s) that works for you / that you'd recommend?

    Some things that might be nice to learn more about, just to start the ball rolling (provided this thread isn't redundant):

    1. Where do you draw your inspiration from? How do you tend to come up with a mission idea?

    2. What building techniques do you utilize? Free building? Planning everything on paper first? Bare-bones architecture first? Modular? Creating major areas, then linking them all up later? Something else?

    3. What do you do to keep morale up / keep progress going, particularly when you've been working on the same mission for a long time?

    4. What are some of the most important things to keep in mind when creating a mission?

    5. Are there any particular mapping practices you'd argue for/against?

    6. What are some of the most common issues you run into when creating a mission, and what are some ways you can overcome these issues?

    7. Would something like a GDD for missions be useful? What about something like a cognitive model of TDM players?

    • Like 1
  2. Goldwell's is a skull; Aosys wanted to adapt it for something like a Weeping Angel.

     

    @Aosys Try replacing abs(angle_x); with 0;

     

    Worked like a charm, thanks!

     

    Also, you don't want to put the while() loop inside the main() routine, in case you want the main() routine to execute code after the while() loop.

     

    Yeah, I figured as much. For now, I'm just doing it for testing purposes. In my actual WIP I'll be sure to create a separate method, and hopefully be able to call it after a specific event.

    • Like 1
  3. Aosys, by "fully ghost" you mean without tools? One water arrow each is enough, of course.

     

    I'm probably not following the full rules of ghost (it's not a style I usually play in), but I did try for no-tools, no-alert run, since this FM seems pretty well set up for it. I ended up having to blackjack the two aforementioned characters, since they were in the way of loot/objectives. In hindsight, I probably could have used water arrows or something, but eh, I'll take what I got and roll with it.

     

    [Edit] Actually, I just remembered, I had to blackjack a third guy too.

     

     

    One of the sleepers had a purse, and the only way for me to get at it was to knock him out. So there's that...

     

     

  4. Thanks for the mission, and gratz on the release! I played through it last night, and was able to almost fully ghost it, with the exceptions of

     

    the innkeeper and the thief.

     

     

    Very nice little mission, especially for only two weeks - modular building seems like a powerful technique indeed. In terms of issues, I only found three pretty minor ones:

     

     

    1. The haunted candlestick was already mentioned, so nothing new there I guess.

     

    2. The material for the portrait on the northeast desk, in the room behind the counter, seems to be missing?

     

    3. Had some minor issues frobbing the one piece of loot in the Builder's room chest. Ended up having to pull noclip shenanigans to get at it. Anyone else run into this?

     

     

     

    Anyway, thanks again, and nice work!

  5. Hi all, was just recently poking around my AppData folder and managed to find my Darkradiant crashdumps, which reminded me that I should probably report what happened. To date, I've had three crashes from 2.0.3, all of which occurred when I was manipulating patch vertices, if I remember correctly. Has anyone else encountered this? Is it even worth reporting at this point?

  6. Evenin' folks, having a bit of an issue with the "door_128x64x2_withhandles_oak.pfb". It works fine as a door, but I visportal and it a) doesn't register as a double door and B) doesn't close the visportal when the doors are closed. Looking at all the entity properties, I see nothing wrong, and I know the visportal is set up correctly. Anyone know what might be causing this?

     

    NXOtCHK.jpg

  7. It looks like you may have enough beta testers atm, but if you're looking for someone with a pretty powerful computer, you could maybe put me down as well? Maybe as a backup? I'm completely new to beta testing, but would be happy to give what feedback I can. I could also try testing on my old computer, if you want someone on a really terrible machine...

  8. If I may say so, "boom shroom" is a fantastic asset name! :D

     

    [Edit] Well, a bit of poking around revealed that the static boom shroom models seem to work just fine (though the flinder's collision material appears to be missing). I'm guessing this was never fully implemented?

     

    7jlXjeV.jpg

     

    qiEaCIr.jpg

    • Like 1
×
×
  • Create New...