Tutoriale

amxxpc turns Pawn source into the .amxx bytecode the server loads. How to compile locally on Linux and Windows, read the errors, target the right AMXX version, and install the result.

Why hlcsg cannot find a WAD referenced by the map, and how to correct the wad key paths, use relative paths, or copy WADs locally so the compile completes.

What the ZHLT/VHLT warning means, why vertex-manipulated faces produce it, and how to re-align the texture in Hammer so the compile is clean.

What each of the four GoldSrc compile stages does and the real flags that matter — a fast draft pass for iteration and a full-quality pass for release, with no invented switches.

Why a map shows black, purple-checkered, or missing textures in game, and how WAD embedding, client-side WADs, and correct texture names put them back.

How hlcsg handles textures, what -wadinclude actually bakes into the BSP, and the modern rule: embed your custom WADs, keep the standard cs WADs external.

What clipnodes are, why complex brushwork blows past the GoldSrc limit, and how func_detail, CLIP/NULL texturing, and simpler geometry bring the count back down.

What a leak actually is, why hlbsp aborts VIS, and how to load the generated .pts/.lin pointfile in your editor and in-game to walk straight to the hole.

Why amxxpc throws error 017 when compiling an AMX Mod X plugin, and the five things that actually cause it: missing includes, wrong-version natives, typos, and scope mistakes.