7 Commits

Author SHA1 Message Date
cora
c9b11b7c73 add ws cheats to cheat.lua ... why, fleck, why ? :D 2021-08-28 23:01:49 -05:00
cron
2aefaaee92 tchat: prevent /commands from being sent unintentionally 2021-08-28 22:48:09 -05:00
cron
6697a9e235 tchat: add team clear and chat clear 2021-08-28 22:32:39 -05:00
cron
4a12c4b818 tchat: fix duplicate player online bug 2021-08-28 22:32:39 -05:00
cron
519575a9b3 tchat: make message prefixes consistent 2021-08-28 22:12:31 -05:00
flyc0r
51408076dc updated wisp and tchat 2021-08-28 22:12:31 -05:00
flyc0r
2551ddbf1d Add changes from waspsaliva initial commit
This commit contains changes best credited to flyc0r
<flyc0r@localhost.localdomain>, although the changes were separated
out from waspsaliva's original initial commit rev. 0e9e1f352, which
added the files from DFC work tree, and squashed in numerous additions
by flyc0r and collaborators.  That commit log:

    commit 0e9e1f3528c3d2fa1f1e9a79d4a00576be8552f5
    Author: flyc0r <flyc0r@localhost.localdomain>
    Date:   Sun Oct 4 03:37:08 2020 +0200

        init

This rebase had the effect of griefing the git history xD, so
for example `git blame` of DFC and even upstream Minetest sources
appear to be originally authored by `flyc0r` in that commit.

To fix this, I will recommit only the changes onto the appropriate
commit in DFC, and recreate the following git history (incl. merges).
After this, the git history will be at least visually the same as the
original Waspsaliva, even if commit sha1sums have changed.

AFAICT, the closest commit from DFC was af085acbd.  That commit was
found simply by running `git diff wsc-master <some_DFC_rev>`, and
locating the commit with the smallest number of differences.

This commit was then created as follows:

    # Check out the DFC base commit
    git checkout af085acbd
    # Check out the *files* from WSC's initial commit
    git checkout 0e9e1f352 -- .
    # Make sure everything is added and commit the changes
    git add -A
    git commit
2021-08-28 21:58:59 -05:00