summaryrefslogtreecommitdiffstats
path: root/EssentialsGroupManager/build.xml
diff options
context:
space:
mode:
authorElgarL <ElgarL@palmergames.com>2011-11-02 22:33:29 +0000
committerElgarL <ElgarL@palmergames.com>2011-11-02 22:33:29 +0000
commitceba3e08993f29598a99196773f4699d753cfde2 (patch)
tree4d7c6210f967c4a8ad7234bd245670cf908907b3 /EssentialsGroupManager/build.xml
parent4ee2f557a85d45770a712f891f653ba9f2db1955 (diff)
downloadEssentials-ceba3e08993f29598a99196773f4699d753cfde2.tar
Essentials-ceba3e08993f29598a99196773f4699d753cfde2.tar.gz
Essentials-ceba3e08993f29598a99196773f4699d753cfde2.tar.lz
Essentials-ceba3e08993f29598a99196773f4699d753cfde2.tar.xz
Essentials-ceba3e08993f29598a99196773f4699d753cfde2.zip
GM will now check to see if it's data files have been changed at each
scheduled save. If the files have been altered (on disc) it will reload, so long as the in-memory data hasn't changed. If the files on Disc have changed AND there have been changes to it's in-memory data it will show a warning. You then MUST issue a '/mansave force' to overwrite the disc files, or a '/manload' to overwrite the memory data.
Diffstat (limited to 'EssentialsGroupManager/build.xml')
0 files changed, 0 insertions, 0 deletions