Help:Automation

This is a draft help page. It is a work in progress open to editing by anyone.
Remember to check for any notes left by the tagger at this article's talk page.

This article or section should be converted to third person to conform to wiki standards.

Stub

This article or section is a stub. You can help by expanding it.

Todo: Rename and move to Automation on the VDC

This article or section needs to be cleaned up to conform to a higher standard of quality because:

Any ideas?

For help, see the VDC Editing Help and Wikipedia cleanup process. Also, remember to check for any notes left by the tagger at this article's talk page.

Scripts

Some tips on how to make your life easier when performing various tedious tasks. As you know, any simple tasks that do not contain something like "write a poem!" are subject to automation, although this is still possible today. But here I will show you some scripts that are useful... for creating something.

Tip:Almost any AI Bot makes mistakes during automation and requires appropriate prompts. Separately written scripts are still prefer for such tasks.

Entity Lists

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

For Source FGDs

Todo: Python impletation with GUI (PyQT6)

Bug:Sometimes the script adds entities to the wrong section (with a different prefix)  [todo tested in ?]

Bug:Sometimes unnecessary spaces may be created.  [todo tested in ?]

Warning:This script is useless if the FGD format is changed in the project (on the Source Engine). This script is works with the standard Valve format of FGD files for all vanilla Source branches.

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

Empty

This article or section is empty. You can help by adding it.

Bots

Empty

This article or section is empty. You can help by adding it.

References

1. "FGD to Entity List" for Source Engine (GitHub Gist)
2. "FGD to Entity List" for GoldSrc Engine (GitHub Gist)