Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Every weapon has a detailed inspection page with stats and descriptions of its properties. You may also find a very short breakdown in the "purpose and instructions" bubble that pops up when selection the weapon using mouse wheel or number keys.
The inspection mode is not mapped to a key by default, you can set it in the options in the spawn menu's utilities tab (as seen the very first screenshot in the showcase above).
Do note, inspecting obviously only shows details about the weapon you're currently holding.
There is no breakdown of every weapon in a list-form or something similar at the time of writing.
I meant prior to spawning the gun. Everything here looks like an addon conflict.
To confirm, try and temporarily disable other addons in the gmod main menu, before loading a game and then verify if my weapons are still broken.
Bad SetLocalOrigin(-1279.986328,16520.039062,10078.145508) on gmod_hands
Error creating 'sting_pfire' (Make sure the file is AddCSLuaFile'd and there aren't any errors!)
Error creating 'sting_sfire' (Make sure the file is AddCSLuaFile'd and there aren't any errors!) (x3)
When first loading onto a map, do you get any console warnings or errors related to my addon?
That sounds like an addon conflict, caused by another addon overwriting my content.