Help:Automation: Difference between revisions
mNo edit summary |
mNo edit summary |
||
Line 1: | Line 1: | ||
{{draft}} | |||
{{stub}} | |||
This article delves into the realm of automation, exploring the scripts and bots in streamlining processes and enhancing efficiency across VDC. | This article delves into the realm of automation, exploring the scripts and bots in streamlining processes and enhancing efficiency across VDC. | ||
Revision as of 03:47, 5 April 2024

Remember to check for any notes left by the tagger at this article's talk page.
This article delves into the realm of automation, exploring the scripts and bots in streamlining processes and enhancing efficiency across VDC.
Scripts
Scripts are fundamental to automation, enabling the automation of repetitive tasks and the execution of complex operations. This section will detail the types of scripts used in automation, their applications, and the programming languages most commonly employed for scripting.


Entity Lists
Creating lists of entities is not something supernatural; in fact, it is a simple task. While reaching the .fgd file format, I outlined some points for myself that can be used to my advantage. Well, look!




Known issues


For
Source FGDs
The Script[1]
- Uses grep -i '^\(@solidclass\|@pointclass\|@NPCClass\)' "$1" to filter lines from the input file that start with @solidclass, @pointclass, or @NPCClass.
- Creates sections based on the prefixes extracted from the processed lines. It uses an associative array declare -A seen to keep track of prefixes that have already been processed. This ensures that each prefix corresponds to a single section.
- Uses *{{ent|$result}} to format the processed lines as wiki entries.
- The section headers are formatted as ===%s_*=== where %s is replaced with the prefix. For example, if the prefix is example, the section header will be ===example_*===. Each processed line is then added under the appropriate section.
- Handles unincluded lines by appending them to a separate "Unincluded" section at the end of the output file. This ensures that all lines are accounted for, even if they don't fit the criteria for the other sections.
Usage
Source-FGD-Ent-List-VDC-2.sh <input> <output>
Examples
- List of Fistful of Frags entities
- List of Heart of Evil: Source entities
- List of Grey entities
- List of Wilson Chronicles entities
For
GoldSrc FGDs
The Script[2]
- The logic is same to
Source script
- Uses grep -i '^\(@solidclass\|@pointclass\)' "$1" to filter lines from the input file that start with @solidclass, @pointclass, or @NPCClass.
- Uses *{{ent|$result_(GoldSrc)|alt=$result}} to format the processed lines as wiki entries.
Usage
GoldSrc-FGD-Ent-List-VDC-2.sh <input> <output>
Examples
- List of Counter-Strike: Condition Zero Deleted Scenes entities
- List of James Bond 007: Nightfire entities
- List of Paranoia entities
- List of Cry of Fear entities
Table Generator for Console Variables
Bots
Bots are automated software agents designed to perform specific tasks, often in response to certain triggers or conditions.
WisdomBot
This marks the inaugural creation of an automated bot within the VDC, created by Wisdurm. Despite the existence of PIPEbot prior to this, there is no evidence to suggest that it operated autonomously or performed any specific functions[3].
This bot has significantly replaced the outdated {{entity}} and its derivatives with {{this is a}} on the pages.[4]