FGD Features

[Mikk155]

BSPGuy crash upong using the @include method

[Mikk155]

@wootguy i didn't want to open a new issue for this but instead add suggestion label or so.

Would be cool as addition as well to show a BOX traced on these limits from within the 0,0,0 to the limits this variable is defined to. i'd recommend it to be a simple box drawn by lines on all the corners, Not covering the whole faces of it, and if posible, warn the user if part of the map is outside this zone

[Mikk155]

i may also add this for linking entities

Also the recently new addition of J.A.C.K that is target_generic that works the same as target_destination but is used in JACK so it doesn't list "errors" as missing entities.

[Mikk155]

BSPGuy does show repeated BaseClasses when they're defined on only one Class type.

For example a entity that is both Point and Solid class will share their values and BaseClass. it will show both Solid and Point entity with the info of the last entity readed on the FGD

Example:

@BaseClass = Cfunc_friction : "Surface with a change in friction" : ""
[
	modifier(integer) : "Percentage of standard (0 - 100)" : "15" : ""
]

@SolidClass base( Mandatory, Cfunc_friction, RenderFields, ZHLT, Appearflags )  = func_friction : "Surface with a change in friction" : "" []

@PointClass base( Mandatory, Cfunc_friction, hullsizes, RenderFields, ZHLT, Appearflags )  = func_friction : "Surface with a change in friction" : "" []

In this case both point and solid entity will have the keyvalues from the class hullsizes wich only exist in the PointClass. in J.A.C.K they're defined separately