clientside sv_cheats commands and immune to triggers

[satoon101]

As far as the build process goes, it has to build for each engine we support on the master branch on both Linux and Windows. If any of those fails to build, the entire build fails. Currently, that is 7 engines (bms, csgo, css, dods, hl2dm, l4d2, and tf2) times 2 operating systems.

[decompile]

So can we just use the 2 versions for CS:S http://forums.sourcepython.com/showthread.php?1066-clientside-sv_cheats-commands-and-immune-to-triggers&p=6882&viewfull=1#post6882 and CS:GO http://forums.sourcepython.com/showthread.php?1066-clientside-sv_cheats-commands-and-immune-to-triggers&p=7112&viewfull=1#post7112?

[Ayuto]

Yes, but the CS:S version needs to be updated due to the getter/setter update a few weeks ago.

[Ayuto]

Added send_convar_value() to the Player class!
https://github.com/Source-Python-Dev-Team/Source.Python/commit/a0513d0a26c0ed439a57ab18811f21e39786712f

[decompile]

Hey Guys,

sorry for bumping older threads but I may found something for the triggers immune thing.

After searching a source engine game's sourcecode, I noticed that they are setting a flag, which prevents the players from NOT touching triggers.

https://github.com/momentum-mod/game/bl ... r.cpp#L177

Right after I googled and found pretty much this:

https://developer.valvesoftware.com/wiki/SetSolidFlags()

Is there a way to use this for SP? I noticed recently, that I got exactly this problem when going into spec and back.

[L'In20Cible]

Syntax: Select all

from entities.constants import SolidFlags

# Not solid...
entity.solid_flags |= SolidFlags.NOT_SOLID

# Solid again...
entity.solid_flags &= ~SolidFlags.NOT_SOLID

Requires lastest commit: 4cadca4