You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There currently seems to be some support for HammerAddons tags, but it's very limited. Single tags on keyvalues and I/O will be highlighted blue, but using multiple tags or inverted tags will cause the surrounding coloring to break.
For spawnflags and choices type keyvalues it's worse, adding the FGD tags at the end of the line will break coloring for the entire rest of the file past where the tag is located.
For reference, the full list of supported features can be found here
The text was updated successfully, but these errors were encountered:
I've been wanting to rewrite the FGD syntax highlighting for a while since it was way too rigid and was easily broken. Just pushed an update that should fix the issues you mentioned. (0.10.3)
Let me know if there are any more problems. If there aren't, feel free to close!
Seems to all be working as expected now! One more thing is you might want to change the parameters of the appliesto() helper to be colored dark blue since those are also FGD tags, but not doing that doesn't break anything.
There currently seems to be some support for HammerAddons tags, but it's very limited. Single tags on keyvalues and I/O will be highlighted blue, but using multiple tags or inverted tags will cause the surrounding coloring to break.
For
spawnflags
andchoices
type keyvalues it's worse, adding the FGD tags at the end of the line will break coloring for the entire rest of the file past where the tag is located.For reference, the full list of supported features can be found here
The text was updated successfully, but these errors were encountered: