You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
some progress with the UI. While it is far from done, my general idea is already there:
A text box on top that explains some things that can be ignored once you know how it works
The time slider is replaced by a preset of 5(?) predefined times. Makes it easier to select and define differences
the area below will show the effects of the selected time on the explosion in a visible pleasing manner; right now my idea was to have the following effects:
volume of C4 beeper
amount of wires that lead to instant explosion on defusal attempt
amount of fire spawned around C4
C4 killradius
These values should be balanced in such a way that no C4 is inherintly better than the other, only situational differences
While i like removing the clonky slider, it did allow you to set the timer close to important round progress points like roundtime and overtime end. And depending on your server config there can be huge differences in max/min time available.
Would it maybe make sense to instead have a Time with a -30s and +30s button next to it? This is a granular enough increment i think and you can still clearly show the effects from the increase 🤔
Great Idea! Its probably a huge pain to do, but it would be amazing if the kill radius would be shown visually, like this:
So showing a person as a size reference, and the a half circle for the radius? (bigger radius = smaller reference person)
What exactly do you mean here? I assume something like more time -> range++, defuse difficulty++, offset by beep volume++ and the increased time to find it? or did you have a more complex interaction in mind?
While we can make the times dynamic, your +/- 30s remove the possibility to define a handful scenarios. Allowing for dynamic time changes defeats this purpose
I honestly wanted to make this waaay simpler. Something like "Radius: 20m" in a neatly rendered way
yeah, something along those lines, I have not yet figured this out
Hmm, personally, I am not sure about the complete removal of the slider as an option. I see where you're coming from but personally greatly appreciate the exact control over the timer.
I like it just being displayed as a readable distance in irl units. Is an F1 menu toggle to switch between meters and feet needed :D?
A longer C4 should be quieter, but should it maybe scale higher? I can see arguements for basically all implementations of volume scaling/levels i can think of.
I think personally I would make it so there are only two or three discrete levels. the normal beeps, which are only audible within the same room. Then the beeps withing the last minute or so, where they should be audible in a few rooms over. and finally the the last 30 seconds or so, where it gets as loud as it gets currently. I think putting it in discrete stages like this makes it easier for (trained) innocents to understand where they are at, and how to react, while it should at the same time make it a bit more tense when players immediatly notice "oh we are already in the endgame"
I am not sure how to scale this to the fuse time though. if this should all be based on percents of the chosen of time, or if shorter bombs should immediatly start in the later levels or what
I personally hated the slider because nobody really bothers to set an exact time anyway (I watched quite a few videos and everybody just either leaves it at 0:45 or removes it to a random position without any second thoughts; therefore I want a quick to use UI). And probably nobody noticed the correlation between the defuse wires and the time. Having a fixed amount of presets makes that clear. Also I don't get why you have to set it to 2:06 instead of 2 minutes - is there really a difference? Because I'm always trying to achieve to things: simplify the options and explain more.
Currently we only support metric, and I'm not really interested in supporting anything else
I personally hated the slider because nobody really bothers to set an exact time anyway
awww, i definitly do that haha. but i get what you mean. I've got to say, I did not entirely get the problem with having discrete 30 second or so steps to choose from. It feels like a great compromise to me. these can still be discretely defined, it would be more a matter of displaying them so that there arent like 10 different options to choose from but you instead cycle through them by pressing the "time up" or "time down" buttons
There is no real problem, maybe your solution is even the best. My point was: Nobody wants to fine tune their C4, nobody has the time. I want to provide 3 to 5 discrete time stamps that have their own strategic benefits. When having a +-30s button, you have a slider, but worse :D It is even slower than a slider, while providing less granularity
After discussions that we had in different PRs I decided to change gears on that. First of, I will finish #1752 first. After that, I will go forward with my initial idea, however same as with armor I will add a "classic mode" that is exactly as it is now (with a nicer UI though)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
type/enhancementEnhancement or simple change to existing functionality
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Currently done:
fixes #1096