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
An idea came up to implement more default ids into pgm, the same way never or everywhere are default ids for <never/> and <everywhere/>. This can't be done without potentially breaking old maps that could be using whatever we decide on id names, as an already existing filter id for something else. That's when the idea to make a proto 1.5 came.
With a new proto, maps on older (1.4.2 and below) protos simply wouldn't get those defaults registered, and would continue to operate just fine. New maps or maps that get migrated to 1.5 will start getting these new default ids.
Here's a list of proposals/potential candiates:
observing & participating filters
alive & dead filters
match-idle, match-starting, match-running, match-finished & match-started match phase filters
kill generic <match-phase> filter
add specific idle & starting filters (atm you're forced to use <match-phase>idle</match-phase> etc)
crouching, walking, sprinting, flying and grounded player pose filters
An idea came up to implement more default ids into pgm, the same way
never
oreverywhere
are default ids for<never/>
and<everywhere/>
. This can't be done without potentially breaking old maps that could be using whatever we decide on id names, as an already existing filter id for something else. That's when the idea to make a proto 1.5 came.With a new proto, maps on older (1.4.2 and below) protos simply wouldn't get those defaults registered, and would continue to operate just fine. New maps or maps that get migrated to 1.5 will start getting these new default ids.
Here's a list of proposals/potential candiates:
observing
&participating
filtersalive
&dead
filtersmatch-idle
,match-starting
,match-running
,match-finished
&match-started
match phase filters<match-phase>
filter<match-phase>idle</match-phase>
etc)crouching
,walking
,sprinting
,flying
andgrounded
player pose filtersvoid
filtermaxbuildheight
variabletimelimit.duration
variabletimelimit.overtime
if we want that to be variable-modifiable?.
for hierarchy-like keys, but we can't use-
in variables so...<walking/>
filter to<standing/>
to better reflect what it means?The text was updated successfully, but these errors were encountered: