Share Config/Console Code Stuff Thread

[Costigan_Q2]

//disable hear-view chat bind
alias chatoff "cf1; cf2"
alias cf1 "bind BUTTON chaton; set cl_chat_sound 0; set con_notifytime 0"
alias cf2 "echo chat off"
alias chaton "cn1; cn2"
alias cn1 "bind BUTTON chatoff; set cl_chat_sound 1; set con_notifytime 3"
alias cn2 "echo chat on"
bind BUTTON "chatoff"

Alternate 'alias cf2' line:
alias cf2 "clear;echo chat off"
The 'clear' command clears the console of messages.

Or do it this way:
set cl_chat_sound "0"
set con_notifytime "0"


cl_chat_sound - This is a Q2PRO command, i don't know what else it works with.
Specifies sound effect to play each time chat message is received. Default value is 1.
0 — don’t play chat sound
1 — play normal sound (‘misc/talk.wav’)
2 — play alternative sound (‘misc/talk1.wav’)

con_notifytime - This is a regular Q2 command.
The delay before console messages disappear from the screen. Default value is 3.
0 — don't show console messages

For the 'cl_chat_sound' command the talk1.wav file is located just below the talk.wav file in the standard Quake 2 pak0.pak in \sound\misc.

For the 'con_notifytime' command if you set 'con_notifytime' to '0' you can still view the console messages by just opening up the console.

[Costigan_Q2]

//set msg bind
alias msg0 "bind BUTTON msg1; set msg 0; echo All messages"
alias msg1 "bind BUTTON msg2; set msg 1; echo Most messages"
alias msg2 "bind BUTTON msg3; set msg 2; echo Limited messages"
alias msg3 "bind BUTTON msg4; set msg 3; echo Minimal messages"
alias msg4 "bind BUTTON msg0; set msg 4; echo No messages"
bind BUTTON "msg0"

Alternate 'alias msg4' line:
alias msg4 "bind BUTTON msg0; set msg 4; clear; echo No messages"
The 'clear' command clears the console of messages.

Or do it this way:
set msg "0"
set msg "1"
set msg "2"
set msg "3"
set msg "4"


msg
Type: Toggle
Default: 1

Description: Toggle the display of messages.

Values:
0 - All messages.
1 - Most messages.
2 - Limited messages.
3 - Minimal messages.
4 - No messages.

[Costigan_Q2]

This post was inspired by the 'ignore nick commands' thread: http://forum.tastyspleen.net/quake/index.php?topic=23172.0


Q2PRO client manual ignore commands: https://github.com/skullernet/q2pro/blob/master/doc/client.asciidoc#chat-filters

Chat Filters

Chat filters allow messages from annoying players to be ignored. Each chat filter is composed from a match string. When a chat message is received from server, a list of chat filters is examined. For each filter, match is wildcard compared with the message, ignoring any unprintable characters. If the message matches, it is silently dropped.

There is also simpler form of chat filters: nickname filters that ignore chat strings from specific nickname. They can be replicated with generic filters and are supported for convenience. Unlike generic chat filters that support wildcards, nicknames are matched as plain strings, ignoring any unprintable characters.

ignoretext [match …]
Adds new generic chat filter. When called without arguments, prints a list of registered generic filters.

unignoretext [all] | [match …]
Removes the specified generic chat filter. Specify all to remove all filters. When called without arguments, prints a list of registered generic filters.

ignorenick [nickname]
Adds new filter to ignore specific nickname. This command supports nickname completion. When called without arguments, prints a list of registered nickname filters.

unignorenick [all] | [nickname]
Removes filter to ignore specific nickname. This command supports nickname completion. Specify all to remove all filters. To remove literal nickname ‘all’, pass a second argument (can be any string). When called without arguments, prints a list of registered nickname filters.


Q2RTX client manual ignore commands: https://github.com/NVIDIA/Q2RTX/blob/master/doc/client.md#chat-filters

Chat Filters

Chat filters allow messages from annoying players to be ignored. Each chat filter is composed from a match string. When a chat message is received from server, a list of chat filters is examined. For each filter, match is wildcard compared with the message, ignoring any unprintable characters. If the message matches, it is silently dropped.

ignoretext [match ...]
Adds new chat filter. When called without arguments, prints a list of registered filters.

unignoretext [all] | [match ...]
Removes the specified chat filter. Specify all to remove all filters. When called without arguments, prints a list of registered filters.

ignorenick [nickname]
Automatically composes and adds two chat filters: _nickname_: * and (_nickname_): *. This command supports nickname completion. When called without arguments, prints a list of registered filters.

unignorenick [nickname]
Automatically composes and removes two chat filters: _nickname_: * and (_nickname_): *. This command supports nickname completion. When called without arguments, prints a list of registered filters.


R1Q2 client manual ignore commands: http://panjoo.tastyspleen.net/R1Q2%20Client%20README.htm

Client commands:

ignore text
Ignore any chat messages containing text.

unignore text
Allow previously ignored messages containing text.

[Costigan_Q2]

This post is for uncertain/unknown chat code stuff, i will add more stuff to this post as i find it:


set scr_chathud_ignore_duplicates "1"


//ACME CTF 'Last Resort' Server ignore/unignore bind
alias players1 "ignore;bind BUTTON players2"
alias players2 "unignore;bind BUTTON players1"
bind BUTTON "players1"


//ACME CTF 'Last Resort' Server ignore nickname bind
bind BUTTON "ignore thisnick;ignore thatnick"

[Costigan_Q2]

This post was inspired by the 'Help-Error help' thread: http://forum.tastyspleen.net/quake/index.php?topic=23497.0


//set cl_noskins bind
alias noskins0 "bind BUTTON noskins1;set cl_noskins 0;echo YES skins next map"
alias noskins1 "bind BUTTON noskins2;set cl_noskins 1;echo NO skins next map"
alias noskins2 "bind BUTTON noskins0;set cl_noskins 2;echo NO NEW skins next map"
bind BUTTON "noskins0"

Or do it this way:
set cl_noskins "0"
set cl_noskins "1"
set cl_noskins "2"


cl_noskins
Type: Toggle
Default: 0

Description: Toggle the display of custom skins on other players.

Values:
0 - Enable the use of skins.
1 - Disable the use of skins.
2 - Enable the use of skins but do not download new skins from the server.

cl_noskins 0 = You can see any skins you have AND new skins will be downloaded.
cl_noskins 1 = You can see just male grunts.
cl_noskins 2 = You can see any skins you have BUT no new skins will be downloaded.

[Costigan_Q2]

This post was inspired by the 'Help-Error help' thread: http://forum.tastyspleen.net/quake/index.php?topic=23497.0


//allow_download_players bind
alias adp0 "bind BUTTON adp1;set allow_download_players 0;echo Disable downloading players"
alias adp1 "bind BUTTON adp0;set allow_download_players 1;echo Enable downloading players"
bind BUTTON "adp0"

Or do it this way:
set allow_download_players "0"
set allow_download_players "1"


allow_download_players
Type: Toggle
Default: 1

Description: Toggle the automatic downloading of players files.

Note: This command can be used by both the client and the server individually to prevent the automatic downloading of game files.

Values:
0 - Disable downloading of players files.
1 - Enable downloading of players files.

[Costigan_Q2]

This post was quoted from Replacing the rocket/grenade splash damage animation/graphic

In the 'Effects' section of the Q2PRO Client Manual there are several relevant console commands.


cl_disable_particles
Disables rendering of particles for the following effects. This variable is a bitmask. Default value is 0.

1 — grenade explosions
2 — grenade trails
4 — rocket explosions
8 — rocket trails


cl_disable_explosions
Disables rendering of animated models for the following effects. This variable is a bitmask. Default value is 0.

1 — grenade explosions
2 — rocket explosions


Tip: Bitmasks
Bitmask cvars allow multiple features to be enabled. To enable the needed set of features, their values need to be summed.


I dunno what else is in there but Q2PRO clearly has it covered from the console command angle.

[Costigan_Q2]

A post by Clippy recovered from deletion.

http://forum.tastyspleen.net/quake/index.php?topic=23156.msg235001#msg235001

Re: Share autoexec.cfg Code Thread
« Reply #7 on: 08-08-2021 03:41:14 »

press and hold the key down (N) to see packetloss , eg red lines

//Netgraph
alias +netgraph "netgraph 1"
alias -netgraph "netgraph 0"
bind n "+netgraph"

this while simple saves a load of typing

bind o spectator 1
bind p spectator 0

« Last Edit: 19-08-2021 23:08:11 by Clippy »

[Costigan_Q2]

A post by QwazyWabbit recovered from deletion.

http://forum.tastyspleen.net/quake/index.php?topic=23156.msg235020#msg235020

Re: Share autoexec.cfg Code Thread
« Reply #8 on: 12-08-2021 16:25:35 »

Your default cfg file in the baseq2 folder is autoexec.cfg, if autoexec.cfg is too big then it may fail to load when you connect to a server, if you have this problem then you can create an extra cfg file (pick your own name for said extra cfg file) and then take cfg code from autoexec.cfg and put it into said extra cfg file so that you can keep autoexec.cfg from being too big.

1. Create the insertnamehere.cfg file and put it into the baseq2 folder
2. Take cfg code from your autoexec.cfg file and put it into the insertnamehere.cfg file
3. Put this line of cfg code into your autoexec.cfg file: exec insertnamehere.cfg

You can create more than one extra cfg file by following the same 3-step process.

This is a good procedure that everyone would be well-advised to follow. The command buffer size in modern clients is 64k bytes but was originally only 8k in the idSoftware code. The game swallows the entire contents of the config files into the command buffer before it tries to parse the commands so spaces and comments are all put into the command buffer before parsing. Breaking your configs into multiple files exec'd from within the autoexec.cfg is definitely a good way to keep them organized. Executing them as modules from within autoexec.cfg allows greater control of the client startup without a lot of duplication of text.

Writing files like grapple.cfg, hook.cfg, zoom.cfg, msgmodes.cfg, etc. allows you to keep all files in your configurations nicely cataloged into single-page, easy to edit modules. Different autoexec's per mod can be customized to call the needed component configs so you don't have to be scrolling through a long file looking for a particular command or bind.

« Last Edit: 27-08-2021 16:53:16 by QwazyWabbit »

[Costigan_Q2]

//set crosshair bind
alias ch0 "bind BUTTON ch1;set crosshair 0;echo ch0"
alias ch1 "bind BUTTON ch2;set crosshair 1;echo ch1"
alias ch2 "bind BUTTON ch3;set crosshair 2;echo ch2"
alias ch3 "bind BUTTON ch0;set crosshair 3;echo ch3"
bind BUTTON "ch0"

Or do it this way:
set crosshair "0"
set crosshair "1"
set crosshair "2"
set crosshair "3"

...

//sky binds
bind BUTTON "sky black"
bind BUTTON "sky 1"

Or type into console:
sky black
sky 1

[Costigan_Q2]

This FANTASTIC bind, that I composed, covers the grapple hook code for a whole bunch of (Original) Quake 2 mods.

Chaos, L-Fire CTF, WOD, LMCTF, Lithium, Railwarz, Etc.

//many grapple hooks bind
alias gh1 "bind BUTTON1 gh2;bind BUTTON2 +grapple;echo chaos grapple"
alias +grapple "grapple;wait;grapple shrink"
alias -grapple "grapple grow"
alias gh2 "bind BUTTON1 gh3;bind BUTTON2 +ctfgh;echo ctf grapple"
alias +ctfgh "use Grapple;+attack"
alias -ctfgh "-attack;weaplast"
alias gh3 "bind BUTTON1 gh4;bind BUTTON2 +hookwod;echo wod grapple"
alias +hookwod "hook action;wait;hook shrink"
alias -hookwod "hook stop"
alias gh4 "bind BUTTON1 gh5;bind BUTTON2 +hook;echo misc q2 mods gh"
alias gh5 "bind BUTTON1 gh6;bind BUTTON2 +hook2;echo laser hook old"
alias gh6 "bind BUTTON1 gh7;bind BUTTON2 +hook3;echo alt ctf grapple"
alias gh7 "bind BUTTON1 gh8;bind BUTTON2 +hook4;echo alt wod grapple"
alias gh8 "bind BUTTON1 gh9;bind BUTTON2 +hook5;echo laser hook new"
alias gh9 "bind BUTTON1 gh1;bind BUTTON2 ngh;echo no grapple hook"
alias ngh ""
bind BUTTON1 "gh1"
bind BUTTON2 "ngh"
bind BUTTON3 "hook action;hook action"
bind BUTTON4 "hook4 action;hook4 action"

BUTTON1 = change grapple hook using
BUTTON2 = use equipped grapple hook
BUTTON3 = wod grapple - shoot multiple grapple hooks (NOT NEEDED)
BUTTON4 = alt wod grapple - shoot multiple grapple hooks (NOT NEEDED)

Do not alter the 'alias ngh' line, it is correct, there is nothing wrong with it.

[Costigan_Q2]

This post is for other config/console code stuff threads on this forum, i will add more stuff to this post as i find it:

Binds/Aliases
http://forum.tastyspleen.net/quake/index.php?topic=7.0

Q2 binds
http://forum.tastyspleen.net/quake/index.php?topic=2385.0

Re: Share autoexec.cfg code Thread (Deleted Posts)
http://forum.tastyspleen.net/quake/index.php?topic=23156.0

[Costigan_Q2]

https://skuller.net/q2pro/ is gone, find Q2PRO on github instead:

https://github.com/skullernet/q2pro
https://github.com/skullernet/q2pro/blob/master/doc/server.asciidoc
https://github.com/skullernet/q2pro/blob/master/doc/client.asciidoc

[Costigan_Q2]

Here is how you use config/console code to defunctionalise a button:

//defunctionalise a button bind
alias ALIAS ""
bind BUTTON "ALIAS"

Or do it this way:
bind BUTTON ""

By placing nothing between quotation marks in code you defunctionalise a button.

[QwazyWabbit]

There is also the

unbind

command.
unbind <key>