nbohr1more

The objective is to get mappers to use newer features. The Asset bonus is capped to 2 perfect votes averaged into the visual score. I was considering only awarding bonus points for code features ( game-play, visuals ) but the Asset bonus allows mappers to decide (risk) only to use one code feature or none at all and still have a little buffer against others who use them. Hopefully the vote participation will be high so that the bonus bias won't be too exaggerated anyway. ( I may need to add a scaling factor if 18 additional votes is half or more of the overall vote participation. ) I ask you to consider joining the fray as you always add stellar submissions to contests! Otherwise, please consider joining "in spirit" and adding story connections and 2.07+ features to your WIP and targeting the 2.10 release window. There is no obligation to declare your participation before submitting your entry. Yes, for 2.10 features players will need to install a 2.10 Dev Build or Beta version: https://forums.thedarkmod.com/index.php?/topic/20824-public-access-to-development-versions/ they can either use this as the primary TDM install or install it separately. As for 2.09 "features"? You're right, I guess I should say "feature" as the only player exposed feature is the new physics based particle setup: https://wiki.thedarkmod.com/index.php?title=Particle_collisions_and_cutoff

The bonus cap will be: Two feature awards ( based on the highest two TDM versions used ) ( added to either game-play or visuals ) One asset award ( based on the highest used TDM version ) ( added to visuals ) One "Connection" award ( based on voting for how connected the mission is to other missions 1 - 5 ) ( added to story ) So 6+5+2+5 = 18 perfect votes biasing the average. Side note: One easy thing to add to get a feature score is to add an EFX 2.0 reverb definition as that was added in 2.07

I think this is a @taaaki comment since I used the native poll creation feature. That said, it would probably look better to write out One Star, Two Starts etc given the current design.

Hello all! It has been too long since a contest has been organized so this is an overdue proclamation. Part 1: The theme of this contest is "connections". This means that the mission must in someway relate to the story or characters of another existing TDM mission. For example, you could create a mission that creates a side story that connects a Thomas Porter series mission to a mission in the Penny Dreadful series. You could also create a mission that tells the story of what happened to a side character in a Thomas Porter mission before the events of a subsequent Thomas Porter mission. If you are the author of a mission series, you are free to create another entry in your existing series but are encouraged to somehow connect that new mission to a different author's series. If you are not the author of the series, it will be up to you to decide how strongly you describe or imply that your mission is connected to the series. Feel free to make branch stories of the main TDM campaign missions or be more adventurous and branch out from a unique gem like Blackgrove Manor. If you do intend to strongly associate your connected mission to a mission not created by the TDM team or Crucible Team, it may be best to reach out to the original author of the mission for approval or guidance. You are only free to create "official sequel" missions for a series if you either created that series or have approval from it's author. For example, should you decide to create a new Chronicles of Skullduggery mission and call it "COS 4: Sneaky Snacks" chances are that Bienie would not approve of this unofficial sequel and we could not host it or allow it to compete. It is safer if instead you create a mission that tells your own story but incorporates location names, characters, and story elements from an existing mission. Further, when incorporating these elements they should remain largely untouched. You can have your character discuss where Thomas Porter was going (etc) but you should not change Mr Porter's sexual orientation or conjure some story about his desire to quit his adventures to become a hot-air balloon operator. ( Unless the author Sotha approves of your fanciful divergent version of Mr Porter ) More "safe" ways to "connect" your mission to an existing mission: A story book (readable) that tells a fable version of what happened in a different mission. A character who hates the protagonist of a different mission for some reason. A character who has visited a town from another mission. The "connection" attribute will add to the "story score" and will be voted on. ( Ranging from 1 added perfect vote to 5 added perfect votes biasing the average. ) Part 2: 2.10 OPTIONAL Dev Build Bonuses To help promote the 2.10 beta process and encourage more testing, additional points will be added for using features from the latest TDM versions. This will be a risk \ reward scenario since cutting edge features may need to be changed or even removed by the final 2.10 release. We will work hard to ensure that features that are critical to the design of these missions are maintained and improved but we may not be able to guarantee 2.10 beta features will be considered stable for production. Mission authors are free to release a two versions of their mission ( 2.10 and 2.09, or 2.10 and 2.07 etc ) if they want to allow players who don't want to use TDM 2.10 beta ( Dev builds ) to play their mission. This isn't just a 2.10 initiative, you can see below that we are also awarding authors who use features from 2.07 to 2.09 as well. The newer the feature, the greater the reward. The reward for using a new 2.10 graphic or game-play feature will be 6 perfect votes added to your voting average. The reward for using a new 2.10 asset ( texture, model, sound, etc) will be 2 perfect votes added to your voting average. The reward for using a new 2.09 feature will be 5 perfect votes added to your voting average The reward for using a new 2.09 asset will be 2 perfect vote added to your voting average The reward for using a new 2.08 feature will be 4 perfect votes added to your voting average The reward for using a new 2.08 asset will be 2 perfect vote added to your voting average The reward for using a new 2.07 feature or asset will be 2 perfect votes added to your voting average These points will be averaged into either the graphics or game-play section of voting depending on what you add. I will attempt to identify what features are being used but will kindly ask that authors declare which features are being used in their submission thread. Standard Contest Scoring: Total Points = (gameplay * 3) + (Appearance * 2) + (Story \ Theme * 1) Max Possible = Total Votes * 5 (Outstanding) Category Score (%) = Category Points /Max Possible * 100 Total Score (%) = Total Points /Total Max Possible * 100 The vote count was equal in all categories for everyone so: TotalMaxPointsPoss (TMP) = AllCategoryVotecount(ACV) * 30 Full Weighted Score (FWS) = (Gamescore*3 + Visualscore*2 + Storyscore) / TMP Pre-existing maps: The contest will be for newly created missions. Authors can use modular assets and prefabs and limited pre-made map sections. If you wish to use an existing WIP mission, you will need to declare this in your release thread and other participants will need to agree that your mission should be allowed to compete. Otherwise, if multiple authors with WIP missions decide to join we can create a separate scoring for those missions. The submission deadline will be Christmas Day ( but we can extend the deadline if all participants agree to the request. )

Here is a revised EFX reverb file:kiss.efx Since Baal already expressed that he wasn't happy with the current setup, this may be added as a replacement depending on feedback. Just add it to /darkmod/fms/talbot/efxs/ ( you'll need to create the efxs folder )

Hmm, did you have any missions installed? It may be that the mission you are trying to launch is not 2.09 compliant. Try moving all fms from your darkmod/fms directory then running the tdm_installer again so that it puts the default missions back. After this, try launching TDM.

A small fix for particle fog rendering near water: tdm_ghouse_sfx.mtr Needs to be added to a materials sub-folder in the darkmod/fms/northdale1 folder tdm_sfx.mtr

I think this is the right place. The other discussions should probably be moved here.

Fixed in rev 16360 The strange particle sprite used in the training mission collides with the flame material. Fortunately the material used here is not used in other scenarios that are fixed by sort last. That said, someday we need to make the heat haze in torch flames work better with water or glass materials ( known limitation ).

Hard to fix this one. If you universally highlight all alpha, it causes artifacts on door hinges or other transparent decal areas. Maybe a new material flag "frobAlpha" ?

I'll take a look. It could be that some of the particles in that torch are not set to sort last and other are.

Here are my latest settings: r_frobHighlightColorAddB = "0.00001" r_frobHighlightColorAddG = "0.00001" r_frobHighlightColorAddR = "0.00001" r_frobHighlightColorMulB = "0.3" r_frobHighlightColorMulG = "0.3" r_frobHighlightColorMulR = "0.3" r_frobOutlineColorA = "0.4" r_frobOutlineColorB = "0.4" r_frobOutlineColorG = "0.4" r_frobOutlineColorR = "0.4" r_frobOutline = "1" r_frobDepthOffset = "0.004" r_frobIgnoreDepth = "0" This produces a more subtle frob that more closely resembles the original version but has a slight glow due to the frob outline.

I have been bothered by the overly clear water effect in many TDM missions including this one. I have attached two modified material files: tdm_water.mtr tdm_sfx.mtr A water with a blend filter stage and the particle vfx material set to "sort last" so that lamp glares will render over the top of it. Add these to a materials sub-folder in your volta fm folder to try them out.

2.10 compliant version added to the original post