Skip to content

Creating new guides for FGDs with specifics in regard to Strata#177

Open
OrsellGit wants to merge 7 commits intomainfrom
feat/fgd-docs
Open

Creating new guides for FGDs with specifics in regard to Strata#177
OrsellGit wants to merge 7 commits intomainfrom
feat/fgd-docs

Conversation

@OrsellGit
Copy link
Copy Markdown
Contributor

@OrsellGit OrsellGit commented Apr 8, 2026

There are some Strata Source-specific features with FGDs and how they work with Hammer. Here, I have created two new guides and documented some of the new Strata-specific features with FGDs. I am sure there is more to add but this is a good start to just document what is currently available and working, especially when it comes to custom AngelScript entities.

FGD Helpers documented:

  • - catapult
  • - direction
  • - orientedboundingbox(width, height, depth)
  • - orientedboundingboxhalf(width, height, depth)
  • - orientedwidthheight(width, height)
  • - worldtext

There is also light, but it currently has no purpose yet.

@OrsellGit OrsellGit added the documentation Improvements or additions to documentation label Apr 8, 2026
@TeamSpen210 TeamSpen210 self-assigned this Apr 8, 2026
@cloudflare-workers-and-pages
Copy link
Copy Markdown

cloudflare-workers-and-pages bot commented Apr 9, 2026

Deploying wiki with  Cloudflare Pages  Cloudflare Pages

Latest commit: 0ff4ec0
Status:🚫  Build failed.

View logs

@OrsellGit OrsellGit changed the title Creating a new guide for FGD helpers specifically created in Strata Creating new guides for FGDs with specifics in regard to Strata Apr 9, 2026
@OrsellGit OrsellGit marked this pull request as ready for review April 9, 2026 07:43
@OrsellGit OrsellGit marked this pull request as draft April 9, 2026 07:49
@OrsellGit OrsellGit marked this pull request as ready for review April 10, 2026 04:04

![Options Button](../../general_images/options_button.png)

From there, you can navigate using the side bar to `Game Configuration`. At the top is where used FGDs are listed under `Game data files`. To add an new FGD, simply click `Add...` on the right. To get to a existing FGD to edit, select an FGD in the list and click `Edit`. This will open the FGD file in your systems default text editor. To remove an FGD, select one in the list and click `Remove`, this will not remove the actual FGD file.
Copy link
Copy Markdown
Member

@iamsirenstorm iamsirenstorm Apr 12, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is up to you if you wanna change it, but as I recall, the standard for articles on the wiki is to keep language formal. So you should remove mentions of 'you' in your articles. This is obviously not really enforced, so that's why I say it's up to you. But I thought I should make a note anyway.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

oop, nice catch yes I will need to to fix this

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Consider adding a note for adding/changing FGDs in gameinfo.txt, because it can result in weird quirks/inconsistencies that someone may not immediately think about (I had this issue and was really confused at one point!)

If I recall correctly VBSP looks at this path and not the path in Hammer Game Configs, which can cause lots of issues like instances not having their rotation properly applied.

Image

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I do remember that the gameinfo FGD does have some weird involvements, I forgot this when implementing this guide, more focused on the idea of just custom FGDs for custom entities in mind rather than potentially needing to change the one in gameinfo with a different, I can mention it.


## catapult()

Typically used for `trigger_catapult`. Provides a preview of the launch arc of the launch by the trigger generated by other KVs. For the `catapult` FGD helper to properly render the launch preview, the KVs `playerspeed`, `physicsspeed`, `launchtarget`, `useExactVelocity`, and `exactvelocitychoicetype`, are needed whether that is from manually adding them to the entity class entree or inheriting the `trigger_catapult` class entree.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is "entree" intended? I'm not familiar with the term. Sounds like entrée, haha

Copy link
Copy Markdown
Member

@TeamSpen210 TeamSpen210 Apr 12, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Probably should be entry, or maybe definition?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lol sorry I meant entry, definition also I believe works but ill just correct to entry

@iamsirenstorm
Copy link
Copy Markdown
Member

Mostly nits. Ignore them if you wish.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants