These are quite useful on fields (ent.origin_x, for instance), but if inside of a struct, there's no _x/_y/_z generated for them (ent.s.origin_x generates an error)
Apparently this is by design, as it uses up extra fields.
The only compromise I could think of is adding a (expensive) flag that will always allocate those extra fields, but as Spike said people should rather just use .x/.y/.z or [n].
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yes, this indeed still seems to be a problem.
Apparently this is by design, as it uses up extra fields.
The only compromise I could think of is adding a (expensive) flag that will always allocate those extra fields, but as Spike said people should rather just use .x/.y/.z or [n].
Moved to https://github.com/fte-team/fteqw/issues/71