v1.5.1

Full Changelog: v1.5.0...v1.5.1

Features

Warning

We recommend not using "require" GMCL on single-player, as the pause mechanics break the watchdog.
We are working on fixing this by detecting for single-player pause mechanics.
Please see #10 for further tracking of this problem.

Client Isolation

Because some servers do not like client-state being tampered with, or the server's own trust towards users aren't maintained, this solves that issue by blocking the client-state from having the API & Pulse from existing.

Console Commands

We now have console commands under the cc_* prefix, this allows you to have control without the need for lua execution.

New Patch

gm.phys.mindist_event_illegal - patches the assert and fixes the teardown from mindist's illegal event.

Installation

This is a list of possible routes for you to install the binary into the game engine.
I highly recommend carefully reading which ones you would like to chose.

Windows

• Rename the CL/SV binary into version.dll and place it near the executable of garry's mod
• Rename the CL/SV binary as gm(cl/sv)_crashcapture_win(32/64).dll and place it in the lua/bin folder for require
• Place the SV binary as a plugin in lua/bin folder and create a .vdf in the addon's folder to load it
• Inject the CL/SV binary into the garry's mod process

Note

Some garry's mod branches contain different locations for where gmod.exe real executable may be.
For no.1, we recommend that you do not place crash capture next to the gmod.exe launcher

Linux

• Rename the CL/SV binary as gm(cl/sv)_crashcapture_linux(null/64).dll and place it in the lua/bin folder for require
• Place the SV binary as a plugin in lua/bin folder and create a .vdf in the addon's folder to load it
• Inject the CL/SV binary into the garry's mod process

Note

Client native linux builds are experimental due to a lack of testing infrastructure.