[Dragokas]

Thanks!!!
That's nice you consolidated useful links and lot of own practice in one place.

Tools:
Dunno, should it be mentioned. Everybody have own tastes.
I'll just leave here own toolset I often use:
-------------------------------
VPK:
- GCFScape - extracting VPK
- vpk.exe (included in game) - packing to VPK, just drag & drop folder on it

Map decompilers:
- pakrat
- bspsrc

Skins:
- VTFEdit - inspecting vtf materials, converting, creating sprays...
- Crowbar - decompile / compile model, Model Viewer integration stuff
- [Batch] BZ2 compress/decompress/verify
- [Batch] Missing textures finder and model compressing
- WinHEX

Server:
- FTP Uploader
- Double click compiler (with N++/AkelPad/Sublime hotkeys support)
- HLSW - execute RCON commands
- Source Admin Tool (standalone), Game-Tracker (web-based) - monitoring

Source Code Helpers:
- Spider - web-based sp compiler with custom *.inc support
- WinMerge (freeware), Beyond Compare (trial) - compare differences between plugin versions
- Lysis - for decompilation - when e.g., you don't remember what plugin is installed on your server and can't find source or dunno what version is it.
- spcomp snapshots of other versions (1.11, 1.10, 1.9, 1.8, 1.7) - to compare 2 smx (last known source code and unknown smx), like such algorithm:

• use decompiler to see in header the version of compiler unknown smx was compile with
• use same compiler to create most similar smx from last known sp source code
• decompile your own smx compiled in previous step
• compare those pair in text mode

-------------------------------


// TODO for me.

Originally Posted by Silvers ConVars Anomaly Fixer

Perhaps need tutorial how effectively use it. Will do later.


Skip it. Already included in 1st post:

Spoiler

Originally Posted by Silvers Cvar Configs Updater - Good for updating convar configs when plugins update and add new convars

and to remove unused (to clean the server from garbage). And therefore decrease probability of cvar anomaly.

Common Scripting Mistakes:
You can append about opportunity to retrieve SteamId (GetClientAuthId, GetSteamAccountID) in case author wants to preserve user specific info in file/DB to survive the server restart.

Originally Posted by Silvers I'm unfamiliar with how to download Hammer for CS:GO etc and related tools (please let me know).

"bin" folder with hammer is only downloaded for users with Prime-status:

- By purchasing the Prime Status Upgrade from CS:GO's Steam Store page
- By reaching Profile Level 21 in CS:GO.

References:
https://developer.valvesoftware.com/...uthoring_Tools
https://support.steampowered.com/kb_...2235-QYCN-3295

Particles:
You can append that you can access Particle Editor through "L4D Authoring Tools" -> L4D (Tools Mode).
Also, [Batch] Particles Extractor & Tester plugin (if suitable)

AddFileToDownloadsTable:
Possibly, need a link to some good article about all stuff regarding setup content-server, packing bz2, black screen and so.
Look also: https://forums.alliedmods.net/showthread.php?t=224404
Maybe, add to article. Though, looks pretty overloaded.

SourceMod Coding:
For Russian speaking community:

Lessons by R1KO - very good for begginners and reminder for prof
Advanced tutorials by Kailo - inside smx, assembly, mem structure and so



Debugging:
I think, need to add some basic info on debugging, like:
- where crash dumps are stored
- using -debug switch to get more detailed description in crash logs.
- install Accelerator
- check addons/sourcemod/logs/error_<date>.log constantly; hightlight that most important parts are - error description (often omitted by users when they asking for help) and line number.
- memory leak and how to dump handles, also provide link to this good consolidator: https://hexer10.github.io/Sourcemod-HandleDumpParser/
and explain to pay attention on records with too may handles, like > 50 (excepting forwards),
instead of total memory they used like some people think, unless you are the author to be able make such conclusion).
In that case it's better compare memory by timeline to understand is it a leak:
little explanation - make dump #1, wait till map end, make dump #2, change map, make dump #3; restart server, make dump #4,
compare most suspicious values between dumps to see how memory/handle count increasing by time. In most cases, they should not, or should in a very limited range.
- explain the most direct and fast method of resolving plugin conflicts - halving, by removing half of plugins -> test -> repeat again.