snatcher

The Frob Helper doesn't work in this mission. I suggest an update of tdm_player_thief.def to the latest version.

I have never been truly satisfied with the Whistle: it was either too much or too little. The latest version (v4) is so far the best (imho) although I still disagree with some things. Are you up to date or are you keeping a previous version for some reason?

I would say sound propagation was built mainly thinking of player footsteps and while it works very well for this purpose it is unsuitable for one-off special events.

I need A New Job

Walking in the footsteps of previous explorers... So far, so close!

Yes, it's time to do something about this. For all missions.

I like this very much. It goes in line with the idea that players become more creative when they can alter the world around them temporally instead of permanently. Each time is a different challenge. It will never happen globally, though. Good news is that we have Shadow Arrows.

This topic is going in different directions and it is difficult to tell if we all are in the same page. Facts: Stgatilov wants to change (improve, I guess) something and while implementing the change he realizes he will break some mission in the process. Mappers have been including (now obsolete) core files in their missions and the developer wants to know why these files were included in the first place, as in: the purpose. Changes in two mission are unavoidable, unless the authors go back and revisit the entire logic of their missions. Changes in eight missions are avoidable, in the sense that missions remain essentially the same with or without these changes. Regardless, if the improvements are to be implemented ten missions need to be reviewed and updated. Now my opinion: Considering how the topic is going the next time Stgatilov wants to improve something similar he might think it twice (we all lose because of ten missions). If these same improvements were to be implemented in the future chances are not ten but fifteen missions would have to be reviewed and updated which begs the question, does the inclusion of core files in missions put the present and future development of some areas at risk? No, as long as things remain under control: preserve what must be preserved, encourage and support innovations, identify and address trends. This requires an effort by all parties involved.

Ok but, at what point do we consider *it* relevant, if ever?

Plan B in case Joebarnin cannot get it right with immobilizations. By Any Other Name: attached to this post are the Bow/Arrow, Blackjack and Shortsword scripts updated to 2.12. I didn't take any liberties. Blame snatcher if something isn't right. @joebarnin, @stgatilov z_byanyothername_212_scripts.pk4

Many thanks for bringing this to TDM: it looks great!

A House Of Locked Secrets: attached to this post are the Bow/Arrow, Blackjack and Shortsword scripts updated to 2.12. I didn't take any liberties. Blame snatcher if something isn't right. @Moonbo, @stgatilov z_ahouseoflockedsecrets_212_scripts.pk4

Do you disagree with the core defaults in general or is this a character-specific setup for your mission? Or is it a test or...? ---------------------------------------------- Sometimes we must take things to the extreme to see the whole picture. Let's pretend all these years mappers have been tweaking the player slightly and depending on the mission: You walk faster or slower. You jump very high or you barely get off the ground. You jump long or fall short. You can mantle high or low. You make more noise or less. The lightgem is more sensitive or less. You inflict or take more damage or less. ... Any thoughts from anyone about this scenario? I wonder how the playerbase would feel. My opinion is that the above tweaks are justified when a different universe is competently established. Or when a new, fully realized character is introduced. Otherwise we are tweaking simply because we can, nothing to do with the story.

Are we switching 10 scripts for 10 defs? What if the core def changes sometime in the future and we then have not 10 but 15 or 20 missions from different authors with this def? What if, in the end, nobody is willing to change/enhance/improve the bow because of the trouble? This is the day people might look back to in the future, which reminds me:

You sure know but "missionspecific" can be anything: "byanyothername", "puzzle_solving_time"... Choose something that is unique to your mission not to conflict with any immobilizations in core.

Yeah, we could change ARROW_ZOOMDELAY from 6 down to 3 in core, after a good debate. Or have an optional mod that applies to all missions.

Complicated, heavily linked to the mission: ahouseoflockedsecrets byanyothername ARROW_ZOOMDELAY (from 6 down to 3): cauldron_v2_2 good hazard moongate northdale1 northdale2 prize seeking snowed_inn written

I you cannot change course, nobody can.

There is a problem. You may or may not see it but the problem is there. We can do something about it or we can look the other way. It's in your hands, guys. By looking the other way you can say goodbye to future core improvements on certain features / mechanics.

I will have a look. No promises eh.

Innovation is good: someone has a new idea (or need) and executes it to the best of his/her knowledge and ability. When we start borrowing and adopting other people's innovations we are no longer innovating but creating a trend, for better or worse. Stgatilov is touching the tip of this, still small, but growing by the mission iceberg.

Venturing beyond the base game... A candle set consists of a candle holder and a candle attached to it. Core candle holders, candles and candle sets are properly named in v1.0 but mappers sometimes create their own candle sets and because of how these object are handled by the engine we end up with a "Candle holder" on screen. We can approach this puzzle in different ways but for the sake of simplicity in v1.1 everything is a "Candle", including single candle holders. Find v1.1 attached to this post. Remember you need the Core Essentials for the mod to work. EDIT - The latest version can be found in the opening post.

It is not included in the Modpack. It is a little side project, that's all I know today. You know the drill: do what you please with the stuff I release. And if you can make it better or different: do it!

I agree with your observations. That's the main point: to allow mappers to easily enrich a scene and/or tell little stories through useless objects. Players may or may not pick up an object though, therefore players must be trained (core objects must have default names).

There is the "acquired" slot and then there is the "shouldering" slot. Both look identical but are different entities. I am using the latter (shouldering) at this moment.