<title>Wiki Page Requests</title> # This page is unlisted by choice This page is just about making bulleted lists of topics to actually write on and not really useful information on its own, I thought it would be better to keep it unlisted so that only the people really checking the wiki would find it. Anyone is welcome to add to list to help everyone else identified locations on the wiki they think should either be rewritten / updated / or just created in the first place. The only ask is that you only remove topics if they are seen as irrelevant to Garry's Mod (like something that is already better documented on the valve developer wiki) or if you finished doing that update yourself --- # Playing Pages This category contains guides aimed towards first-time or novice Garry's Mod players. The goal of these pages is to efficiently educate a new player in the basic concepts of Garry's Mod so they can get to the fun as quickly as possible! If you find a Playing page missing, using unexplained and confusing terminology, pages that are for developers, or pages that might confuse a new player rather than educate them, please **list them here with a brief explanation of the issue.** * Add Entries Below This # Developers Pages The pages in this category provide *crucial* documentation on the game's core concepts and processes. Many of Garry's Mod and the Source Engine's most-used features rely on hard-coded assumptions and requirements that are not easy or practical to self-discover. Because of this, it is very important that the Developers section contains guides that clearly outline both the basic "What" of a topic but also the "Why" of the topic. These pages should be written with the understanding that the reader may have zero prior experience with the Source Engine, game modding, programming, modeling, image editing, etc. Not all topics can be easily written with all audiences in mind; In these cases, pages should include links and references to resources that would help an interested reader in "coming up to speed" on the topic's prerequisites. If a page in the Developers category is missing, out of date, hard to read, poorly formatted, unfinished, needing an example, or any other issue that prevents it from being useful to readers, please **list it below and write a short explanation of what might be fixed.** ## Scripting, Programming, and Coding * Add Entries Below This * Creating Binary Modules (pretty sure most of the pages already are out of date) * Using Stencils - [Found this amazing resource but don't have the time to distill it into a wiki pages atm](https://github.com/Lexicality/stencil-tutorial) * Navmesh - generating, adjusting, fixing? ## Map Making and Level Design * Add Entries Below This ## Models, Textures, and Animation * Add Entries Below This * Playermodel Creation - Rigging, Weight Painting, how bones work on playermodels - a page already exists but more information would be helpful * Importing / Creating / Porting models - a nice guide taking you from obj (or similar) to valve dmx / smd would be super helpful ## Game Systems * Add Entries Below This # Developer Reference Pages These pages document the usage of specific <page text="Functions">function</page>, Enums (E.g. <page text="TEAM">Enums/TEAM</page> and <page text="RENDERGROUP">Enums/RENDERGROUP</page>), <page text="Hooks">Hook_Library_Usage</page>, Structs (E.g. <page text="ENT">structures/ENT</page> and <page text="GM">structures/GM</page>), and Libraries (E.g. <page text="surface">surface</page> and <page text="net">net</page>) Developer Reference pages have multiple goals depending on the reader: * **Novice readers** should be able to quickly understand what the page's subject is tangibly used for so they can easily determine if it is applicable to their use case and worth investing further time to better understand it. * **Advanced and expert readers** should be able to either quickly refresh their memory, or rapidly come to understand the subject's available options, caveats, bugs, and known pitfalls. If you see a Developer Reference page that is missing, poorly worded, confusing, lacking a clear example, or is otherwise in need of an update, please **list it here and briefly explain the problem.** ## Globals * Add Entries Below This ## Classes * Add Entries Below This ## Libraries ### Render * Add Entries Below This * <page>render.PushFilterMin</page> * Needs an explanation of what its purpose is * Example should be stand-alone with a screenshot * <page>render.PopFilterMin</page> * Needs an explanation of what its purpose is * Example should be stand-alone with a screenshot * <page>render.PushFilterMag</page> * Needs an explanation of what its purpose is * Example should be stand-alone with a screenshot * <page>render.PopFilterMag</page> * Needs an explanation of what its purpose is * Example should be stand-alone with a screenshot ## Hooks * Add Entries Below This ## Game Events * Add Entries Below This ## Panels * Add Entries Below This ## Enums * Add Entries Below This * <page>Enums/SND</page> is missing descriptions for 2 enums. Some clarification on what these enums do would help aid novice and expert developers alike.⤶ * Ditto for <page>Enums/SIGNONSTATE</page>, <page>Enums/CONTENTS</page>, <page>Enums/COLLISION_GROUP</page>, <page>Enums/EFL</page>, <page>Enums/OBS_MODE</page>, <page>Enums/PLAYERANIMEVENT</page>, <page>Enums/RENDERMODE</page>, <page>Enums/RT_SIZE</page>.⤶ * There may be more enum pages like these that require additional descriptions--I just marked down the ones I felt were either very close to having all descriptions in place, or were more important for developers to know about compared to more niche/unique use-case enums.⤶ * Feel free to expand this list.⤶ * Some pages (like <page>Enums/SNDLVL</page>) may be self-explanatory. Other pages (like <page>Enums/ACT</page>) may be too large to bother adding descriptions for every enum available. ⤶ ## Structs * Add Entries Below This ## Shaders * Add Entries Below This