7 Commits

Author SHA1 Message Date
cora
46c9b4b5b6 nlist: makin it all smoother 2021-08-28 23:13:45 -05:00
cora
435d82cc57 esp: add nodelist 2021-08-28 23:13:45 -05:00
cora
01aeffa8a7 esp: improved autostop 2021-08-28 23:12:30 -05:00
cron
5c52f0b6ba esp: fix cheat registration
We should merge dragonfire sometime :]
2021-08-28 23:12:30 -05:00
cora
c9b11b7c73 add ws cheats to cheat.lua ... why, fleck, why ? :D 2021-08-28 23:01:49 -05:00
cora
860f40dbd0 esp: quick optimisation 2021-08-28 23:01:34 -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