Creating new guides for FGDs with specifics in regard to Strata#177
Creating new guides for FGDs with specifics in regard to Strata#177
Conversation
…Markdown extensions on the article links
|
|
||
|  | ||
|
|
||
| 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. |
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
oop, nice catch yes I will need to to fix this
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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. |
There was a problem hiding this comment.
Is "entree" intended? I'm not familiar with the term. Sounds like entrée, haha
There was a problem hiding this comment.
Probably should be entry, or maybe definition?
There was a problem hiding this comment.
lol sorry I meant entry, definition also I believe works but ill just correct to entry
|
Mostly nits. Ignore them if you wish. |
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:
catapultdirectionorientedboundingbox(width, height, depth)orientedboundingboxhalf(width, height, depth)orientedwidthheight(width, height)worldtextThere is also
light, but it currently has no purpose yet.