Convar tweaks - dvdvideo1234/TrackAssemblyTool GitHub Wiki

Does this thing have any wire extensions and how can I control when my clients are abusing them?

Yes, it does. You can enable/disable the wire extension using the convar trackassembly_enwiremod and set it to 0 to disable the wire extension and 1 to enable it.

I want to use custom tweaks for my server. Could you recommend appropriate convars?

Here is the list of the maximum value tweaks and settings to control the script:

  trackassembly_logsmax   - Controls the maximum logging lines being written
  trackassembly_logfile   - File logging output flag control
  trackassembly_modedb    - Database operating mode ( "LUA" or "SQL" )
  trackassembly_devmode   - Toggles developer mode on/off server-side
  trackassembly_maxtrmarg - Controls the maximum time needed to perform a new player-cached trace
  trackassembly_maxmenupr - Controls the maximum decimal places utilized in the control panel
  trackassembly_timermode - Controls the memory management setting when DB mode is SQL
  trackassembly_maxmass   - Controls the mass upper limit of the piece spawned ( the lower bound is "1" )
  trackassembly_maxlinear - Controls the maximum offset that can be applied by next x,y,z linear offsets
  trackassembly_maxforce  - Controls the force limit upper border on the welds made between pieces
  trackassembly_maxactrad - Controls the vastness of the active point search area
  trackassembly_maxstcnt  - Controls the maximum pieces that can be spawned in stacking mode
  trackassembly_enwiremod - Toggle the wire extension on/off server-side
  trackassembly_enctxmenu - Toggle the context menu on/off in general
  trackassembly_enctxmall - Toggle the context menu on/off for all props
  trackassembly_endsvlock - Toggle the DSV external database file update on/off
  trackassembly_curvefact - Parametric constant track curving factor
  trackassembly_curvsmple - Amount of samples between two curve nodes
  trackassembly_spawnrate - Maximum pieces spawned in every think tick
  trackassembly_bnderrmod - Unreasonable position error handling mode
  trackassembly_maxfruse  - Controls the maximum frequent pieces to be listed
  trackassembly_dtmessage - Controls the time interval for server addressed messages
  trackassembly_incsnpang - Controls the button-sliders angular amount adjustment
  trackassembly_incsnplin - Controls the button-sliders linear amount adjustment
  trackassembly_crvturnlm - Controls the track segment turning limit when curving
  trackassembly_crvleanlm - Controls the track segment leaning limit when curving
  sbox_maxprops           - The maximum props on the server ( Gmod default control )
  sbox_maxasmtracks       - A variable for the maximum things spawned via TA

You can trigger these limits independently from one another. For example:

  • Value maxprops is 50 and maxasmtracks is 30 will trigger maxasmtracks
  • Value maxprops is 30 and maxasmtracks is 50 will trigger maxprops
  • Value maxprops is 50 and maxasmtracks is 50 will trigger maxasmtracks

Note: If you want a server with many props and fewer tracks, then lower down the value of maxasmtracks. The default value is 1500 for maxasmtracks to rely on the props limit. Some tracks when spawned will trigger creation for additional props like the Shinji's for example.

How can I control errors when the clients are flooding my server with rails, and stacking/spawning outside of the map bounds?

Easy. Just set trackassembly_bnderrmod to one of the following values

OFF     -> Clients are allowed to stack/spawn out of the map bounds without restriction
LOG     -> Clients are not allowed to stack/spawn out of the map bounds. The error is logged.
HINT    -> Clients are not allowed to stack/spawn out of the map bounds. Hunt message is displayed.
GENERIC -> Clients are not allowed to stack/spawn out of the map bounds. A generic message is displayed.
ERROR   -> Clients are not allowed to stack/spawn out of the map bounds. An error message is displayed.

Other values will be treated as LOG. But remember young samurai, this variable is only server-side, and because of that you can only access it via the single-player or set it in the server.vdf gmod start-up file. May the force be with you and your server ! Note: The error is logged if the logs are enabled !