[QOL Feature/Bug-ish] Fix name and argument inconsistencies in locs
xvq387
<user deleted>
{200403.1422}
EZ_21's argument is `Nez_21` in locs, while DATA_CHECK's argument cannot be lowercase.
This causes confusion for new players.
My suggestion would be to let EZ_xx also be accessible via the `NEZ_xx` parameter, and replace the references to the lowercase parameter in the vlan to the uppercase parameters. Removing the lowercase parameter would not be ideal because everyone's crackers would break.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
kaitlyn
{200404.0508}
`NEZ_xx` *does* work. `NeZ_xx` or `NEz_xx`, however, do not. I think every lock name should either be strictly case sensitive or strictly case-insensitive.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ast
{200404.0512}
making all locks case-insensitive would be moderately painful on the code side (or at least I assume it would be - the simplest code I can come up with is still a wee bit complicated). perhaps instead `Ndata_check` (and `Ndata_check` alone) should also be treated as a valid key?
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
<user deleted>
{200404.0811}
if it does work, that is the argument that should be included in the vlan to avoid confusion.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
dtr
{200406.2306}
IMHO one of the following 3 should be done:
1) the case displayed is the only case that works. EZ_21 but never ez_21
2) for all locks, all upper or all lower works. i.e. data_check, con_spec, L0CKET, ACCT_NT, SN_W_GLOCK
3) for all locks, any casing works. I.e. AcCt_Nt, coN_A5V4h.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -