Jump to content
The Dark Mod Forums

snowy

Member
  • Content Count

    31
  • Joined

  • Last visited

Community Reputation

6 Neutral

About snowy

  • Rank
    Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. As a newbie I'm still working out a best strategy for creating a mission. I took a lot of notes on the TDM / TTLG / Quake fan missions, either because they have an interesting unique event, setting, low poly architecture or models I can study and reproduce in DR with brushes. I completed the Springheel and Sotha tutorials. Then I immediately tried to make my mission, spending 12 hours on it before losing interest on this map idea. That didn't work out well. Now I've switched strategy, doing TDM speedmaps inspired by the Quake speedmapping community. Trying to create a really short 2-minute finished TDM mission within 100 minutes (excluding planning time) and doing something original and new every time. Builder church, rooftop parkour, city section etc. They're toy missions, but so far this is the most fun way for me to get better at DR and keeping at it.
  2. I can spend at least a few hours a week helping out with coding. Writing code is both my hobby and profession. I have a background in AI and 11 years of professional coding experience (mainly Java, PHP and some C). These last 6 years I've also worked on interactive, responsive and animated web GUIs in JavaScript, HTML and CSS and single-page web apps. I've worked on GUIs both without and with styling systems such grid systems and re-usable styling building blocks that boost productivity. C++ and ID Tech GUI scripting doesn't look too far off from what I'm used to. Maybe the GUI script can borrow ideas from CSS systems to make design changes easier. This doesn't have to be a one-man job. Is the web part also under version control? If not, Greebo or taaaki might want to do this task themselves. I'm also okay with doing the data entry work to add new information to the 100 existing missions to help improve the TDM GUI. If it's mostly wiki data being added, this isn't that much work.
  3. Then I think SeriousToni's mock-up is spot-on. Having a "selected for download" check, mission title, author, series, mission type and release date in the "Downloadable Missions" list. The fields about EFX and Monsters can be added to the "Read more..." section because of space, spoilers and not being primary information for selecting a mission. I'd still separate "Story" and "Mission Notes" fields, which are now one field in TDM. Renaming "Mission details" at the bottom of the mock-up to "Story" which is primary information and a good teaser, and placing "Mission Notes" in the "Read more..." section which could contain useful information for the player and be more spoiler-ish. I'd also like to see a tiny square screenshot either left or right of the bottom "Story" field to aid the story teaser when browsing for missions. A screenshot like an image thumbnail could be very effective for mission authors to get players to download their mission. Here's a case for separating "Story" and "Mission Notes": VanishedOne made a mission called "In the Black". In the spoiler-ish "Read more..." section it would show that this mission features monsters: undead. The mission notes then mention that the undead can be completely avoided. Thanks to this note, I did play, enjoy and finish this mission that I otherwise would've avoided.
  4. Springheel said we should first have a consensus on what information to include. So first we need to know what information there could possibly be. The best source for that is the oldest source, from the TTLG mission authors. This is the information they include. We can exclude all of that, if none of the TDM mission authors want any of those fields. But then at least we can say we've excluded all those fields intentionally, not because we didn't know about them. I think separating story and mission notes could be useful if there's anything the player should know about the mission not story related. Maybe TTLG has this many fields and potential filters, simply because they have an insane amount of missions from authors since 1998 and it's really easy to get overwhelmed when browsing through them especially for newcomers. Also notice what's missing: there's no field for a mission rating. That's been brought up a few times here. I guess they don't need that, so we don't need one either.
  5. The wiki mission table has the most interesting information, I think. Title, author, release date, size, EFX support, series, mission type and monster info. Beyond that, there would be the extra info usually included in TG / T2 FM missions which might not be relevant for TDM missions, such as: difficulty settings (yes / no), if yes, difficulty level names and any extra information about the difficulty levels equipment store (yes / no) map (yes / no) auto map (yes / no) custom assets (yes / no) multi-language support (yes / no), if yes, which languages? briefing (yes / no) build time story mission notes known bugs (if they aren't fixed) Which information do we want to include in TDM? Which of those information fields would be considered spoilers and should be moved to the "more details" section?
  6. Great! I couldn't see your mock-ups anymore, but I did see a mock-up from Springheel that looks similar and I'm a fan of this presentation. Consensus on a design is probably the most tricky part, unless you already have that covered. I can probably help you with the code.
  7. I like the ideas of allowing multiple play styles through a mission, similar to Hitman and Deus Ex. Ghosting, blackjacking and combat are standard. Key hunts, lock picking, underwater parkour and rooftop parkour are less standard. How would "unfortunate accidents" play out in a TDM mission? Would a "whoops, dropped a heavy box onto a guards head" count as such an (unscripted) unfortunate accident?
  8. Let's try that. I did switch buttons "Set Finished" and "Main Menu" around, because I think a back-button should always be on the bottom row. Also I think it would be best to keep button names as brief as possible, so I kept "Refresh List" the same name. See files in attachment and a screenshot: mainmenu_newgame.gui mainmenu_defs.gui
  9. Sure, I can help with that. I'd add a new GUI "markMissionCompleted" command to darkmod_src 2.07 game/ModMenu.cpp:134 like this: (I should probably refactor this into its own re-usable function shared by SysCmds.cpp:157) Then copy the "Refresh list" button from the tdm_gui01.pk4 guis/mainmenu_newgame.gui:151 and add the "completed" command before the "refresh" command. I added the files mainmenu_newgame.gui, mainmenu_defs.gui and ModMenu.cpp as attachment. It's a draft, of course. Feedback for better wording and button arrangement is welcome. Here's a screenshot with the new button marked with red to get this ball rolling: Yes, and if the type has multiple descriptors, we can truncate it down to a single line with the triple dots "...". I think mission size is important for people with a slower internet connection, but it shouldn't be a primary factor in choosing a mission. So I'd be fine with replacing size on the download page with multiple type descriptors. Mission size wouldn't be gone, it would still be visible for secondary evaluation on the "More..." page. When I think about it, the way I really use the "spiders and undead" column on the wiki is two-fold: To evaluate if there will be combat and un-blackjackable enemies in the mission. I really dislike combat and love to blackjack everything. To avoid missions with possible scare jumps or overly graphic scenery. I am one of the "faint of heart", I try walk the very fine line between good amount of suspense and too scary. I would like to be able to see if a mission features any monsters. It'd be fine if that were visible on the "More..." page along with all the other mission details. mainmenu_newgame.gui mainmenu_defs.gui ModMenu.cpp
  10. From a design perspective, the mission types are a mixed bag consisting of locations (mansion, city), genres (horror) and game play types (platforming). Ideally we'd want to split these 3 groups and allow multiple tags in each group. This would cover both single missions and campaigns. It could possibly facilitate an advanced tag-based search if we'd ever want one. And maybe even something fancy, such as a mission recommendation system based on, for example, highest percentage overlap of type tags from already finished or downloaded missions. I wouldn't do those features in C++. Python has easier access to data science tools to do such things. To keep it simple, I'd say the wiki mission type list has a high overlap with the TTLG mission type list that has been in use since 2006. So after 13 years of use, maybe it's just a good list. Mission authors can choose a single mission type that most represents their mission. It can be an artistic decision. A campaign simply remains a "campaign" and missions without a type remain a "single mission". I added a screenshot of the mission download menu with mission type included in the existing layout, marked with red. Because the release date value is fixed in width, there's room for a type value next to it. Since type names are not finalized yet, we can make each type name fit in that type value space. This would always be a single value. I don't know how missions are uploaded. If it's a form, the mission author can select a mission type from a drop-down list. If it's a PM, maybe the mission author can simply mention the mission type in the PM. Because it's a fixed type list, I think we should exclude type from darkmod.txt. Otherwise we'd either have to allow a free type text that could deviate from the online types in the mission manager, or guarantee fixed types in the mission manager by matching the type text with the fixed type name list using something like Levenshtein distance. I'd say the mission type is always read from the online mission mirrors. I think the idea is to help players to more easily select missions to download. Once a mission is downloaded, we can assume players have already made their preferred selection, so mission types in the offline mission manager are less important and more a nice-to-have. I don't know how missions are updated, can I assume they are updated the same way they are uploaded?
  11. Then I misunderstood. Thanks! But maybe if the final result is good enough, it'll get picked up. My goal is simple: the ability to see the specific mission type when selecting missions to download in TDM without changing the current layout. I see showing specific mission types in TDM is no problem. I propose a fixed set of mission type keywords based on the wiki mission page, which I assume is already agreed upon by the TDM community: single, multi, bank, castle, city, church, experimental, tavern, prison, lostciv, horror, mansion, museum, caves, daylight, pagan, pirate, platforming, sewers, ship, rooftop, tomb, training and warehouse. TDM can automatically translate these keywords into the correct language in readable form by mapping, such as "bank" translating to "Bank Jobs" in TDM. Many translations are already available in the lang files, missing translations can be added. I can handle the coding, scripting and translations unless someone else prefers to do that. Once that's done, these mission type keywords need to be added as attributes or field values to the missionlist.xml, which I assume is downloaded from the mission mirrors. I don't know if the XML is manually edited or generated from the darkmod.txt in the missions. For backward compatibility with older TDM versions, these mission types will need to be a new attribute or field in the XML. That's as far as I got. Any feedback to approve, disapprove or improve the plan is welcome. What do you think about this plan?
  12. I wish the rope arrows were retrievable when they are misfired, similar to vine arrows. Any time I use a rope arrow, I quick save just in case I break one.
  13. I like that verticality! Maybe add a mini-tutorial with a note on rope arrows and what to look for though, because when I started looking into FM missions recommended for their verticality, I was totally clueless what to look for to use rope arrows on. It took a while for me to "get it", but when I finally got it, it was amazing.
  14. I'm not aiming for a complete redesign, instead I'm aiming for a smallest significant improvement if there is one. If I just add these lines to mainmenu_download.gui:516 in tdm_gui01.pk4/guis to show "mission type" in the mission details alongside release date (which has a fairly constant string width), right half of the type value aligned with the "More..." text: windowDef SAMDPropertiesType { rect 125,30,80,16 text "#str_04354" // Type: AVAILABLE_MISSION_DETAIL_TITLE } windowDef SAMDPropertiesTypeValue { rect 152,30,190,16 text "gui::av_mission_type" AVAILABLE_MISSION_DETAIL_TEXT } That's a subtle change to conveniently show the mission type in TDM without a complete redesign, right? I bet most won't even notice it unless they actively look for it. I know it's not useful yet, since it only shows Single or Multi, but we can probably expand that enum Type in Mission in darkmod_src 2.07 game/Missions/MissionManager.h:82 since only Multi is checked in two other files, unless this also requires changes in the DR repository. I'm a total TDM and DR architecture newbie, so it's all probably way more complicated than it seems. You're the experienced dev. If you want to shoot this idea down again because you still think it's too complicated or a waste of time, I won't spend any more time trying. All good mainmenu_download.gui
  15. If that means the mission list has been improved enough and everybody agrees, then I'll stop bringing it up. I do like the improved mission list mock-up you made, though. It's similar to the insightful mission wiki page, except all that information shown conveniently in TDM itself.
×
×
  • Create New...