Allow "." in command names

[recatek]

So far as I can tell in local testing, this doesn't seem to break anything. This is useful for automatically generating commands for setting nested fields (e.g. thing1.inner.value 3).

Any reason why this shouldn't be allowed?

[andersmmg]

It may be better (at least for now) to use a command like set instead of creating lots of commands for each field. Then it would be called like set thing1.inner.value 3 instead

[recatek]

What wouldn't give you autocomplete out of the box though, would it? You'd need to provide it yourself. It looks like allowing . works fine for command names if you change the criteria to use a regex instead of checking for a valid identifier. I'm happy to PR it.

[andersmmg]

It wouldn't, but it seems like as much work to implement basic autocomplete as it is registering commands for every settable field isn't it? Limbo console makes it super easy to add autocomplete to commands, that's what I'd do, but you could still do a PR if you want