Category Archives: CSGO

This Catagory is for the blog posts regarding the CSGO evaluator

Best new mute config for CSGO

Ive always been frustrated with the options available to mute other players in CounterStrike: Global Offensive,

Whether you’re getting yelled at in a clutch round or just joined a noisy server where people are spamming their music, you cant be expected to mute and un-mute individual players in dire situations. I found that some of the existing mute functions online are not easy to use, require too many keys, or can be accidentally kept on – leaving you clueless when your team mates are actually communicate to you in future rounds – My bind aims to solve these issues.

Before I show you the bind, lets first look at the current alternatives available for muting all players in CSGO:

The existing solutions
Below are the common techniques of muting players in CSGO:

Block individual players via the UI
Blocking players individually requires you to open up the main menu during a firefight and be vulnerable for at least 2 seconds while you go through and manually mute each noisy teammate.
Set up a voice toggle key using: bind BindToggle “[KEY]” “voice_enable”
This works well, but there is no indication if your toggle bind is on or off, as enabling mute hides the visual popup of a player talking in the server, ive left on for hours using this setting without knowing it, and missed some vital callouts.
configure 2 separate mute / un-mute keys using: voice_scale 0 / voice_scale 1
Including your voice chat button, this solution requires 3 keys, while its one of the better solutions, I would prefer one single mute key, as I always forget which key is mute, and which is unmute.
Autoexec mute scripts
there are many one page scripts you can find online,
but as a developer I want to understand all of the code inside them, especially when I have issues trying to get them to work or modifying them.
I also dont want to have to find all my autoexec code to deploy on any new PC’s I play on
(Tip: with the solution im about to show you, you can just google “best mute config” and this blog post comes up)

The actual code
Today I will be documenting my new mute function I wrote for myself:

bind "KP_UPARROW" "voice_scale 0;";
bind "v" "+voicerecord; voice_scale 1;"

Note: Only copy code from my post seen in the code boxes (like above)
there are issues copying the double quotes into CSGO from anywhere else in this article.

How to enter this mute key bind
You can enter the mute bind seen above by:

– Enabling the developer console (Options > Game Settings > Enable Developer Console – 5th from the top)
– Then Opening the developer console (default “~” key)
– Then Pasting the commands into the console (together, or each line individually) and press Enter.

How to mute people
The above bind sets your mute key to NUMPAD 8 on the right number pad.
it mutes everyone by setting their voice transmit volume to zero,
This means you still get to see when people are talking (eg Fig1)
but you wont’t hear them until you start talking yourself (by pressing the voice key).

Muted preview

Fig.1 – Muted preview

How to unmute people
Once you are ready to hear people again, you just go ahead and press the “push to talk key” which is now set to “V”
The beauty / simplicity of this bind is that using voice chat is also the un-mute key!!

Explanation and Customization
I will go on further to explain how you might want to customize the commands for yourself.
(Eg. if you dont want “V” as your push to talk key)

The first line

bind "KP_UPARROW" "voice_scale 0;"

The first line is a single command, we are binding voice_scale to zero (silencing players) to the NUMPAD 8 key
You can swap “KP_UPARROW” out with any other key such as “K” (especially if your keyboard dosnt have a full numpad)

The second line

bind "v" "+voicerecord; voice_scale 1;"

This is actually 2 commands – which both happen at the same time – when pressing “V”,
– the +voicerecord action (the action of using voice chat)
– then sets everyone’s voice scale (you loudness you hear people at) back to full volume

How to customize
So lets say you want to change your mute key to “M”,
your voice chat key to “K”,
and for some reason you want other peoples voice volume audible to you at 75%
You would customize the binds to read as per below:

bind "M" "voice_scale 0;"
bind "K" "+voicerecord; voice_scale 0.75;"

Upsides to our new solution
– “voice_scale 0” (
which we are using) is a more elegant alternative to “voice_enable 0” because when using “voice_enable 0” you never actually know when people are muted, you dont get the visual reminder on screen (seen above in Fig.1) when a muted person is trying to talk to you.
– No autoexec requirement
– No Aliases (Aliases are stored binds that are removed when you close CSGO)
– Doesn’t require you to remember 3 dedicated keys for “mute”, “unmute” and “voice chat”
– you’ll never have the frustration of playing half a comp game and realizing you haven’t heard your teammates all game because you accidentally had “voice_enable 0″ ages before the  current game even started.

Downsides to this solution
You have to hardcode your “voice_scale” setting(volume at which people speak to you)
If you go into the menu and change this value with the slider, every time you use the voice chat key, it will override that value to 100% voice receive volume.
(not a big deal for me, I always use 100%)
You have to use the push to talk button to un-mute people (small drawback for simplicity)
you may occasional have to quickly tap voice-chat to hear people again during games, which is visible to everyone.
Needs to be configured once on every computer (most mute configs require this anyway)
But you can easily find this bind again by typing into google “Best mute config” and using this post!

Conclusion
This mute option isn’t going to be for everyone,
this is simply the closest I could get a mute config that worked the way I wanted it
a mute config that actually informed you when you had people muted. not requiring 3 pages of auto exec to apply, or multiple keys to manage it.
I hope some others can also get some use out of my new mute binds!

 

CSGO Operation Release Order

operation_bravo_coin

Operation Shattered Web was the last operation.

When I first made this blog post in 2016 it was the longest break between operations after Bloodhound ended. so I decided to made this post to detailing all release information about the previous operations.

Some of the initial data was sourced from the csgo wiki

The Table below shows info on: Release days of the week (PDT), Release Time (PDT) and duration of all of the previous operations

Order Operation Release Date Day Time Duration Extended Gap
1 Payback 25-Apr-13 Thu 4AM 128 Yes
2 Bravo 19-Sep-13 Thu 5PM 139 Yes 19
3 Phoenix 20-Feb-14 Thu 9PM 111 Yes 15
4 Breakout 1-Jul-14 Tue 4PM 93 No 20
5 Vanguard 11-Nov-14 Tue 10PM 140 Yes 40
6 Bloodhound 26-May-15 Tue 4PM 128 No 56
7 Wildfire 17-Feb-16 Wed 7PM 149 No 139
8 Hydra 23-May-17 Tue 3PM 174 No 313
9 Shattered Web 18-Nov-19 Mon 6PM 174 No 735

I will be updating these details over time as new operations are released.

Notes:

  • The “Gap” column indicates the time where no operation was active, or the time that operation started after the prior operation ending.
    (Eg. By commencing, Operation Bloodhound ended a 56 day gap in which no operation was active.)
  • The heading “Release Time” is the rough time measured in Pacific Daylight Time (PDT) the update was released, rounded to the nearest half hour
  • Please contact me if there are any errors or outdated data!
  • This page was last updated on 7-Sep-2020

This post was created off the back of an existing page that proved quite popular with people: CSGO Case Release Order – check it out if thats something that interests you!

CSGO Case release dates

https://i.imgur.com/MhRUoCj.png

when working on my CSGO Skin evaluation site
I noticed there wasn’t a place where I could easily look up the release dates, and order of CSGO cases. Which prompted me to make this blog post

The most recently released case is the
Fracture Case

The table below orders all the CSGO cases by release date, and shows how many days it took for valve to release each case.
It also shows the day of the week, and date (in american timezone) that the case was added to the game.

Order Case Release Date Release Day Comments Wait Time
1 CS:GO Weapons Case 14-Aug-13 Wednesday Arms Deal Update
1 ESports 2013 Case 14-Aug-13 Wednesday Arms Deal Update
3 Operation Bravo Case 19-Sep-13 Thursday Operation Bravo 36
4 CS:GO Weapon Case 2 6-Nov-13 Wednesday Arms Deal Collection 2 48
5 eSports 2013 Winter Case 18-Dec-13 Wednesday Winter Offensive Update 42
5 Winter Offensive Weapon Case 18-Dec-13 Wednesday Winter Offensive Update 0
7 CS:GO Weapon Case 3 12-Feb-14 Wednesday Arms Deal Collection 3 56
8 Operation Phoenix Weapon Case 20-Feb-14 Thursday Operation Phoenix 8
9 Huntsman Weapon Case 1-May-14 Thursday   70
10 Operation Breakout Weapon Case 1-Jul-14 Tuesday Operation Breakout 61
11 ESports 2014 Summer Case 10-Jul-14 Thursday   9
12 Operation Vanguard Weapon Case 11-Nov-14 Tuesday Operation Vanguard 124
13 Chroma Case 8-Jan-15 Thursday   58
14 Chroma 2 Case 15-Apr-15 Wednesday   97
15 Falcion Case 26-May-15 Tuesday Operation Bloodhound 41
16 Shadow Case 17-Sep-15 Thursday   114
17 Revolver Case 8-Dec-15 Tuesday R8 Revolver Release 82
18 Operation Wildfire Case 17-Feb-16 Wednesday Operation Wildfire 71
19 Chroma 3 27-Apr-16 Wednesday   70
20 Gamma Case 06/15/16 Wednesday   49
21 Gamma 2 Case 18-Aug-16 Thursday   64
22 Glove Case 28-Nov-16 Monday   102
23 Spectrum Case 15-Mar-17 Wednesday   107
24 Hydra Case 23-May-17 Tuesday Operation Hydra 69
25 Spectrum 2 Case 15-Sep-17 Friday   115
26 Clutch Case 15-Feb-18 Thursday   153
27 Horizon Case 3-Aug-18 Friday Panorama Update 169
28 Danger Zone Case 6-Dec-18 Thursday Danger Zone Update 125
29 Prisima Case 13-Mar-19 Wednesday   97
30 CS20 Case 18-Oct-19 Friday   219
31 Shattered Web Case 18-Nov-19 Monday   31
32 Prisma 2 Case 1-Apr-20 Wednesday Shattered Web End 135
33 Fracture Case 7-Aug-20 Friday   128

Notes

– On 2 occasions there were 2 cases released simultaneously, which is reflected in the column named “Order”

– The heading “Wait Time” is the time it took for Valve to release the case, prior to the release date of the previously newest case.
(The community waited 114 days for the release of the Shadow Case, meaning for 114 days the Falchion Case was the newest case in CSGO.)

– The day counter at the start of this blogpost (in bold) is updated each day automatically.

– Please contact me if this page is out of date!

– This page was last updated on

People seem to really like this blog post, so I have made a similar blog post about the
CSGO Operation Release Order which outlines similar things like duration and downtime between operations.

CSGO Case FAQ

When are new cases released in CSGO?
The average wait time between case releases is currently 78 days
Valve regularly shifts priorities within the company so its not possible to know the exact date when new case will come out – this can be seen from the CS20 Case that took 219 days to release in 2018, which is a much longer wait time than the average

Are cases available in every country?
Cases can be considered lootboxes or a form of gambling depending on your countries laws and online regulations. so far there are are some restrictions in European countries.
– Opening cases is not possible in Netherlands and Belgium
– Opening cases in France requires a P250 Xray to first view a cases contents, then purchased
– Also in France, Cases cannot be purchased from the Steam Community Market.

My Current Progress with the CSGO API

Its been a week or so since I launched the CSGO Evaluator site I made, and its died.
Didnt really expect much out of my free hosting, but its something im working on.
I want to grow my web skills and figure whats causing this one myself.

Essentially the error ive been getting is in relation to the PHP function that actually gets the data from the steam API, not reciving any data at all. Hence my site cant talk to steam at all.

I have done some troubleshooting, and there is something wrong with my host.
I still have functional get_file_contents() requests going on with other pages I have made. its just my webhost has decided that steam API requests should be blocked.

I am currently awaiting a response from my web hosting support ticket.

I have attempted to join another free hosting site, to see if I have the same problem on their site with similar code, but I cant get dotabuff get_file_contents calls to work either.  This isnt conclusive however, because I didnt rule out the possibility that they block ALL file_get_contents() requests.

Anyway, thats the updated situation with my downtime at the moment.