snatcher

Yeah, we agree. I am not criticizing that alert X is Y points. Y must be something and it is what it is. Getting "seen" could perfectly have a bigger impact, to encourage players not to be seen - in example - and drastically decrease the score, but this is a different topic altogether. What matters is that the Stealth score remains consistent across missions and among all difficulty levels, which is the case. A different story though is whether the difficulty settings (AI Vision, AI hearing) should play any role or not. I think it all comes down to how the first page is presented, which feels kind of unfocused and therefore dull, and the second page doesn't improve things much. By having the "Mission Score" I propose players will normally always get a positive outcome based on facts. The outcome. The Stealth Score implementation and perception is arbitrary and subjective and perhaps it doesn't deserve much focus not to confuse players. I haven't thought about the Stealth Score and all the variables much and I don't have any suggestion other than a negative "Ghosting Score".

Yes, a manual edit with bogus data. This is what's left for a second page (plus anything else you can think of if technically possible): Times saved: 25, Times loaded: 12 Pockets picked: 3 out of 5 Time seen by AI: 0m 2s AI KOed: 3, AI Killed: 0, Bodies found: 1 Damage dealt: 0, Damage received: 203, Health restored: 187 A third page could include the current "Stealth score details" as is today but I don't personally find any value in explaining arbitrary decisions (an alert 4 is 3 points because of reasons).

What do you people think of this "focused" mode? (all other stats will of course be found in the next page, but I didn't create any mock up for it)

Thanks, Dragofer. Implementing such UI facelift is fairly easy to do with zero risk of breaking anything. Target files: game/Objectives/MissionData.cpp (source) guis/mainmenu_success.gui (pk4) strings/*.lang (pk4) - Optional? Unfortunately there is little I can do on my own (mod) since this part of the source code is structured in an awkwardly linear, uncontrolled and strict way. If there ever is an initiative to seriously discuss improvements and come up with suggestions and mock ups, count me in. Let's just make sure someone is available and willing to commit changes of MissionData.cpp. Cheers!

In the next page we can include all stats for nerds we want. We don't need long sentences or multi-line static paragraphs explaining nothing. If players want to know what something is about they go online and check and/or ask. There's plenty of room here for everything. Bottom line: the main stats page must include the relevant information casual players expect to find. Nothing else and nothing more. Excuse the triple post.

When I say the statistics are a mess I actually mean the main screen is unspired, or at least, that's what I feel when I look at it: a bunch of words and numbers thrown at the screen. Casual player: I just completed a long and cool mission! Let's see how I did! Difficulty level and Time: Cool, thanks! Times saved and loaded: Do I need to know this? why are you hurting my feelings? I didn't ask for it > Stats for Nerds Why the very first thing I get is the damage? What the? > Stats for Nerds The health restored must be reaaaally important. C'mon. > Stats for Nerds Pockets picked is apparently more important than the Loot, correct? Finally! The Loot! How about an easy to grasp percentage? Killed, KOed and Bodies: Ok. Time seen > Stats for Nerds Oh, and I would appreciate if I get the damn name of the mission at the very top. You know? For my records, social sharing and the like? EDIT - In the above screenshot secrets are missing. Not sure if secrets get displayed in the next screen or since there weren't secrets in this mission secrets just don't show up.

Precisely. The Mission Statistics screens are a complete mess (imho) but on the subject let's simply call it "Ghosting Score". GHOST KEEP TRYING On the next page you can have all "stats for nerds" you like.

Thanks, @Goldwell! The animations are so fast that your sounds are way too long but your samples are so rich that I found a nice texture that I think gives the lamp some personality. Hope you like the result. v0.4 at the bottom. Console command to spawn the lantern: spawn mod:weapon_playerlamp z_handheld_lamp_v0.4.pk4

Something similar happened to me with arrows, not sure in which version but I would say 2.10. At some point arrows would, for some reason, go through bodies and I had to aim for the head, which was the only body part arrows would collide with. I don't normally go on killing sprees and it only happened two or three times that I recall.

I took your version of the model @HMart and managed to export it from DarkRadiant in ASE format and I changed the texture. I don't know about collisions or anything about models and I hardly know what I am doing but it looks a little better now, imho. v0.3 at the bottom. Console command to spawn the lantern: spawn mod:weapon_playerlamp z_handheld_lamp_v0.3.pk4

Perhaps we just have to replace this material with something less fancy. textures/darkmod/glass/dirty_yellow_warp // milky yellow transparent glass { // Written by Tels, mainly based on // http://www.iddevnet.com/doom3/materials.php noSelfShadow noshadows twoSided translucent forceoverlays sort decal glass qer_editorimage textures/darkmod/glass/dirty_yellow_warp_ed description "A dirty, yellow, reflecting, translucent material suited for glass panes" // this block makes the glass distort what you see through it // one unwanted side-effect is that this effect does not stack // and distorbs objects in front of the glass, too { vertexProgram heatHazeWithDepth.vfp vertexParm 0 0 , 0 // texture scrolling vertexParm 1 .8 // magnitude of the distortion fragmentProgram heatHazeWithDepth.vfp fragmentMap 0 _currentRender fragmentMap 1 textures/sfx/vp1 // the normal map for distortion fragmentMap 2 _currentDepth } // this stage sets up the alpha mask (it doesnt render anything) { maskcolor map makealpha(textures/glass/glass1) } // now use the alpha mask to add some fake reflections { blend gl_dst_alpha, gl_one maskalpha cubeMap env/gen2 // tone down the reflection a bit and make it yellow red Parm0 * 0.2 green Parm1 * 0.2 blue Parm2 * 0.05 texgen reflect } // add our texture on top { blend gl_dst_alpha, gl_one map textures/darkmod/glass/crystal_milky red Parm0 * 0.5 green Parm1 * 0.5 blue Parm2 * 0.2 } // This is the code required for frob highlighting this texture frobstage_texture textures/darkmod/glass/crystal_milky 0.15 0.40 } I could try with different materials myself if the model was in ASE (or any other open) format.

No idea. No joy

You maintain it for FMs and I offer it for general use. The more people toying with the lamp the more feedback / support we may get. I noticed the lens part of the model is transparent. We need a modeler.

It seems we killed two birds with one stone (double model / lights on) by moving the attachment from the entity to the animation: anim idle models/md5/weapons/mod_playerlamp/idle.md5anim { frame 1 attach mod:attachment_playerlamp hand_r frame 1 sound_weapon blackjack_sheath frame 12 melee_hold } The lamp no longer auto-spawns but script/tdm_user_addons.script is still required to load script/mod_weapon_playerlamp.script. Console command to spawn the lantern: spawn mod:weapon_playerlamp In v0.2 I also updated def/tdm_player_thief.def to version 2.11 (thanks to @Dragofer). z_handheld_lamp_v0.2.pk4

My proposal is to build a layer on top of the "broadhead" arrow key that allows players to cycle through all available arrows, that way we free 7 slots in one go. Players can have up to 8 arrow types but we hardly ever end up with all arrow types. Let's stick to an average of 5 arrow types (broadhead, water, rope, noise and gas or fire). Pressing 5 times a key to cycle through all available arrows isn't too much asking, imho.