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
Also some net messages are exploitable, especially since it sends the weapon entity over instead of just checking if the sending player's weapon is a multi physgun.
Have fun causing chaos on servers that end up using this until its fixed
You're trusting the client on what entity gets sent, plus its a waste of bytes anyways when you can easily just check the sending player's active weapon, see if its class is multi_physgun and then do what you need to do.
If a client sends an entity that isnt multi_physgun, it'll error in some cases. If the entity does send a multi_physgun entity, they can control what it does no matter who owns it
shouldn't be to long now unless something goes horribly wrong lol