GUARD event spec incomplete (#7619) · Issues · Legacy / Trac

GUARD event spec incomplete

The spec for the GUARD event type has a few issues...

I'm not really sure what to expect for the 'Name' attribute. The spec says...

Name = The (possibly verbose) nickname of the guard affected.

I've listened for some and it seems to be a fingerprint...

650 GUARD ENTRY $5D0034A368E0ABAF663D21847E1C9B6CFA09752A BAD
650 GUARD ENTRY $071C2D9D0E03D75FF30DCCA850BB29CA4A4BB383 BAD
650 GUARD ENTRY $36B5DBA788246E8369DBAF58577C6BC044A9A374 NEW
650 GUARD ENTRY $071C2D9D0E03D75FF30DCCA850BB29CA4A4BB383 GOOD
650 GUARD ENTRY $5D0034A368E0ABAF663D21847E1C9B6CFA09752A GOOD

Is this either a "$[fingerprint]" or nickname? Something else?

There's a TODO comment to explain the states.
The 'Type' is simply described as...

Type = "ENTRY"

I'm guessing that this attribute is to allow guards to be used for other things in the future. If so then the spec should say so.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information