Functionally, this is a non-change.
This just conforms a few odd cases to be the same as the rest.
`git show -w` shows nothing (this is a whitespace-only change).
Since circle/tba is not case-sensitive, this should be a non-change.
I confirmed this by verifying that `diff -i` shows zero changes.
So, to tba, this is just a cosmetic cleanup.
However, to others that use this data, the case might be important.
...this includes my own separate MUD codebase. :)
This just converts the few DOS text files still in here to standard text files (line-endings),
removes all the trailing spaces on lines, removes all the trailing blank lines, and replaces
all the tabs (except in .zon files, where they seem to be common) with expanded spaces.
It's easy to confirm this is actually a non-change, except for whitespace:
* `git show -w` shows this commit as only removing 8 trailing blank lines.
This should make no difference to tbaMUD itself, but it will make working on these files,
especially with scripts and automated tools, much easier.
This is the base change for a set of other changes I will put up once/if this merges,
without this, the others are just too complicated to wrangle.
These are mostly cases of confusion between the "on the body"
and "about the body" slots (5 and 12).
But, there are also some that seem to just be misconfigured,
like non-weapons being wielded, worn items being unwearable,
weapons being worn instead of wielded, and items being worn
instead of held.
I have an independent MUD codebase that reads these files, and
so this gives me an ability to somewhat orthogonally test these,
and easily find this sort of issue.
I did avoid all the cases where it was clear this was done
intentionally, like all the cases where the second neck was
used for the missing face slot (masks, etc).
The ones fixed here all seem to really be (minor) bugs.
I don't know dg_script well at all, so I could be mistaken.
But, I think these are just minor errors in this script.
I have a separately-implemented mud codebase that interprets the
worlds from tbamud, and it flags these as errors, and some other
issues I might chose to fix later, depending on how this PR goes. :)
Of course, it's possible this is really a bug in my own codebase, and
not in these scripts... but I don't think so - and the documentation
I've managed to find seems to confirm my suspicion.
I am guessing some script or tool used upstream is doing an unsafe
search-and-replace for '@' with TAB, and accidentally changing these.
They seem to have been creeping into the repo for years.
I produced this fix commit automatically with:
sed -i 's|\t\([bcdgmnoruwyBCDGMRWY]\)|@\1|g' tba/*/*.*
...and then a few files' changes had to be undone.
I looked through all of the rest, and they look like correct fixes.
I also ran all the other letters, and they only make incorrect "fixes".
* new unfollow command available for all players
* new unfollow command available for all players (fix redundant check)
* new unfollow command available for all players (fix redundant check)
Added year to several datestamps. Unbounded dates are locale-specific.
- Minor re-formatting was needed for STAT PLAYER and SHOW PLAYER.
The 'slay' feature of do_kill now requires a GRGOD or higher.
'last *' and 'last all' are now synonyms.
