Changes

modified ant build to not do unit tests -- not necessary right now. also
closes #66 -- all LWC dependencies are now located in the lib/ folder
(commit: 2e58458)

emptied out README.md and for now put basic build instructions (much
easier now! clone & ant)
(commit: 015d008)

Oops, <code> is a lie
(commit: 33b9b14)

All admin commands have thus far been converted to use the new events
(commit: a1c34c2)

All use of deprecated events on LWC's end should now be fixed !!
(commit: a8fc599)

/lwc admin version will now use VERSION (BUILD), in preperation for #65
(commit: a59ce44)

Reformat build.xml (mainly replacement of tabs with spaces.)
(commit: 348facd)

fixes #54 - do not allow access to chests when LWC has database issues
(or other problems.)
(commit: 9e2e83a)

and print out problem stacks when bad errors occur :-)
(commit: dcac5d3)

closes #51 -- pistons can no longer destroy protected objects (doors,
signs, etc.)
(commit: 2396f94)

Change default table prefix to 'lwc_'
(commit: 0f00482)

some minor formatting fixes in core.yml
(commit: 09e6625)

fixes #68 -- core LWC modules must take precedence over modules from
other plugins.
(commit: b45632c)

Fixes issue where one would always receive "limit reached"
(commit: 4d605db)

Fixes #75 -- obtain a player's groups the correct way via
PermissionsBukkit.
(commit: 0500f16)

Fixes #70 -- also, when clicking on say, a block under a Sign, it will
now say that it's a Sign, not the block you clicked (e.g Stone). Done
for consistency and also so it's easier to know that's the block that's
not actually protected (just indirectly !!)
(commit: c79712f)

It would be preferable to take your eyes away from this commit. On a
nicer note, detecting wall signs was fixed. It detected too many blocks
before.
(commit: 2d7d046)

Closes #61 -- Kainzo: This one is long overdue !! Protection discounts
now give the exact amount for the discount price. e.g, if you set a
discount to charge 0 money, and set amount to 5, players can obtain 5 of
these before never being able to get 5 discounted protections for 0
coins again (unless you make it higher than 5 or change the surcharge.)
(commit: bebee65)

Updated changelog.md -- should have done that already !! Also made
purchased protection refunds use the player that setup the transaction,
not the current protections. Why: Before: Hidendra /cprivate's chest.
/cadmin forceowner Notch is done to the chest and it is removed. Notch
then gets the refund, not Hidendra. After: The same, except Hidendra
gets the refund, instead of Notch.
(commit: 6138726)

forgot linebreak between header and lists
(commit: cb3182a)

Native SQLite binaries were not being downloaded.. >.>
(commit: b6bdf12)

Just kidding, this one's the real RC ....
(commit: 123eba5)

Fixes issue with interfering with PermissionsBukkit somehow... and made
LWC-Economy load after the world is loaded
(commit: 3e2343d)

Fix LWC-Economy -- LWC now loads at STARTUP. Also changed wording in the
default iconomy.yml
(commit: de6223e)

Convert history when converting from SQLite -> MySQL. History was not
being correctly modified when a protection was registered by placing it
down (resulted in not being able to get a refund for it.) Next commit
will be 3.40.
(commit: fe75db7)

Push version to 3.40
(commit: 5ba4358)

Fix PermissionsBukkit (again), /permissions did not work, LWC was using
softdepend and it made PermBukkit break, I guess.
(commit: 2eb90fc)

Init ModuleLoader early
(commit: 37a76fe)

Fix a stackoverflow error
(commit: bf3dcf8)

Push version to 3.41
(commit: 4ae0f03)

Fix LWC-Economy bootstrapping
(commit: a2b89db)

Push LWC-Economy to version 1.21. LWC is unchanged.
(commit: f36b399)

Fix a freezing issue some servers may experience on startup.
(commit: 27b92f2)

Disabled modes were not being properly disabled, despite the user being
told the mode was disabled when they tried it.
(commit: 6bcc2f6)

Protections + history will now not be immediately flushed to the
database as quickly as before -- at the moment, mostly just History
(even when it is created.) The update thread is in a seperate thread. In
the future, this will play a much larger role.
(commit: c6961fa)

That is prepareStatement, not prepareCall, mr. database
(commit: 8a171ea)

MonsterTKE: fixes #73: add EXEMPTION flag which exempts protections from
being expired by ADMIN PURGE, and ADMIN EXPIRE. This flag can only be
set by LWC ADMINS: /cexempt on OR /lwc flag exempt on
(commit: c142dfe)

Allow history logging to be disabled in core.yml (core.disableHistory)
(commit: a3870b1)

Comment up core.yml
(commit: 2c9cb5b)

small sanity check
(commit: 5e1c843)

pre-3.42. Fix a consistency error for history cache <-> database. And
for Jenkins-built builds, /lwc admin version will use (bBUILD) instead
of (BUILD). Manual builds will still show up as (MANUAL)
(commit: 72c48ba)

untrack changelog.md. Mainly just testing fingerprints.
(commit: a78cf09)

Update Package.json, let's try uploading it again
(commit: 9c2ec81)

formatting errors ...
(commit: 8e1c10a)

wrong checksum, I've been had...
(commit: 8781475)

sqlite.jar in lib/ folder is not required for anything in particular.
(commit: b7fdaf0)

Move WorldGuard and Lists modules to core/ (afterall, they ARE bundled
with LWC by default ...)
(commit: 2d8cedf)

3.42
(commit: 550565f)

SQLite did not recognize streaming made (Integer.MIN_VALUE)
(commit: b835189)

Add discount type to LWC-Economy, to support how discounts worked
before. The default (current) way is discount.type: EXACT, while the old
behaviour which would give the discount while the player was UNDER the
discount.amount is now discount.type: TOTAL
(commit: 50c1d94)

Update iconomy.yml to not include outdated info
(commit: 76b06a8)

Native PermissionsEx support
(commit: aac4689)

Update build.xml with PermissionsEx.jar
(commit: bad75e3)

Go around a Bukkit bug for pistons which would cause a casting exception
when a block would be moved on top of a chest
(commit: c3394ad)

Put the version back to 3.42 (whoops (?))
(commit: 4dd0845)

Allow refunds to be disabled in LWC-Economy
(commit: 21688e4)

Allow /lwc admin purgebanned to take the -remove argument, which removes
every block + contents as well (e.g chests + contents, etc.)
(commit: 9edccba)

Updated Polish locale, courtesy of Geoning!
(commit: ab437c0)

Closes #83 -- add Essentials Econ support.
(commit: 1bbc5c3)

Closes #85 -- fixes /permissions not working on PermissionsBukkit 1.2
(but 1.1 was fine.) Technical: LWC was enabling a plugin when it
resolved it as a Permissions API, which must have made PermissionsBukkit
not a happy camper :-). LWC no longer enables the plugin, which is not
necessary, anyway.
(commit: 73bc131)

New versions: LWC: 3.43  LWC-Economy: 1.30
(commit: 3710449)

Test promoting via changelog tag #promote
(commit: 6e1ab01)

Test auto-promote tag one last time #promote
(commit: cafa249)

Forgot to turn on the notifier.... #promote
(commit: e64343d)

Does all of #88 - not fully tested yet, so it will not be auto closed
just yet. By default, permission groups (via SuperPerms) uses
lwc.group.X, and can be overridden in core.yml with groupPrefix:
'your.prefix.'  Also, ensure you don't have a supported Permissions
plugin installed so that this will activate correctly (it will not
override others, so as to not break the ones that don't support
SuperPerms by themselves.)
(commit: 48da505)

Fixes #89
(commit: 856afe6)

Initial work on #87 - fully untested !! Adds central bank functionality,
enforcing money to not come from thin air. When a protection is
purchased, the money goes into the configured bank account, and when a
protection is removed, the money will be withdrawn from said bank
account (and denied removal if they don't have enough.) Supports
BOSEconomy, iConomy [?]
(commit: 290bae3)

Add a bit more to central banking so protections could not be removed if
the server bank cannot afford it. Also, /cremove wasn't broading
LWCProtectionDestroyEvent! (#87)
(commit: f61e1eb)

mostly final changes for #87. Central banking now works as expected,
have only tested on iConomy 5.01 for now (should also work as expected
on BOSEconomy.) [cc: imaxorz]
(commit: 1b70331)

closes #87 - central banking for LWC-Economy is looking excellent to me
(commit: 9bba55d)

Reconnect to the MySQL database if connection is lost from a timeout
(commit: d12c4a0)

Make double wooden doors also automatically open on both sides much like
double iron doors, assuming both are protected [cc: Tyrope]
(commit: 438d0ea)

Using /cinfo (or most other LWC commands) on a double wooden door would
open or close the one beside it (while the door hit was reverted) and
mis-match the doors. Doing the same thing again would fix it, though.
(commit: d1c9850)

Give a default value of TRUE to lwc.protect perm node
(commit: e5e36f1)

Support multiple groups on Perms 3+, with fallback support to 2.1.x
(commit: b570751)

database.adapter had to be all lowercase (MySQL would not work, had to
be mysql) - now adapter: MySQL will work.
(commit: 29324ac)

nospam mode now also hides notes. SEND_LOCALE event was also not being
sent through the new events.
(commit: d5ea9fa)

in regards to #88 - removes reliance on Permission plugin-specific
methods to check for permissions and instead defaults to Superperms.
Legacy Permissions 2/3 support is for the most part dropped in this
build and can be supported with SuperpermsBridge.
(commit: 36971bb)

Prepare protections table for #87 - the build associated with this
commit should be considered broken and not working.
(commit: 2564bfb)

Protection rights are now stored via JSON in the protections table.
Automatic conversion of the old rights table will  be a build or two
ahead, not this one (#81). ChestProtect/ChastityChest plugin conversions
are now also fully removed.
(commit: 30e1c1b)

Old rights -> new rights conversion. Does not drop the rights table just
yet. Will be tested more performance-wise once word is received from
Kainzo.
(commit: c8ba2d7)

Use streaming query for old rights -> new rights if it's available (not
on SQLite, only MySQL.) (#81)
(commit: e09b85e)

That's right, streaming results won't work in this case!
(commit: 7747557)

Display 4.0.0-alpha2 in the version
(commit: e8b394a)

sp
(commit: 75c7cab)

Reconnect to the MySQL database if connection is lost from a timeout
(commit: 48f841a)

Push version to 3.44  #promote
(commit: a0f3194)

(forgot VERSION file)
(commit: 8b582e5)

Initial implementation for being able to schedule jobs or commands - for
example, being able to automatically run cleanup every week (or
something.) It's also extensible by other plugins. LWC had something
extremely similar to this a long time ago, when a web UI was in the
works - it was able to remotely delete chests, open/close doors,
dispense dispensers, and so on (it would insert jobs into the database,
and LWC would notice that, and then execute them.) It may not seem so
useful at first glance, but if combined with outside tasks, it can
potentially do a lot.
(commit: b9cf3bc)

Allow resource bundles to add keys that are not defined in the default
locale
(commit: 575a9f6)

Allow resource bundles to add keys that are not defined in the default
locale
(commit: 6d55a77)

nospam mode now also hides notes. SEND_LOCALE event was also not being
sent through the new events.
(commit: e697108)

Make double wooden doors also automatically open on both sides much like
double iron doors, assuming both are protected [cc: Tyrope]
(commit: 6a81875)

Using /cinfo (or most other LWC commands) on a double wooden door would
open or close the one beside it (while the door hit was reverted) and
mis-match the doors. Doing the same thing again would fix it, though.
(commit: 3d10e29)

3.45, cherry picked commits from devel branch.  #promote
(commit: eab08ff)

Spout support via 100% standalone LWC-Spout.jar. At the moment, it just
allows you to unlock passworded chests via a GUI, but was just made.
It'll be expanded upon, of course!
(commit: 4cfe20a)

Open the chest after entering the correct password.
(commit: 1fae71d)

I disregarded the fact that you can protect blocks other than chests :D
(commit: 73d35b5)

Non-Custom spout windows can't be drawn on, so we'll make our own. /lwc
spout opens a blank window at the moment ... Version info is also in the
bottom left of any LWC Spout windows for the time being.
(commit: 602055e)

remove test junk
(commit: 6987b63)

pushing small changes before sleeping. Just a header on /lwc spout
(commit: ec8db04)

Redstone flag was not being propogated via new events
(commit: 9f7265a)

Redstone flag was not being propogated via new events
(commit: e323f07)

3.46  #promote
(commit: 214f53d)

Add iConomy6 support
(commit: 8f3f6b0)

Add iConomy6 support
(commit: 6c9660d)

3.47 #promote
(commit: c93a904)

Fix merge conflict #promote
(commit: 40bb348)

Redid how /lwc admin report looks. Much prettier and easier to read.
/lwc admin debug has also been removed, since the new /cadmin report
does what it did as well.
(commit: 0f0336f)

Change cache hit/read counter to use long. spunkiie's server would
probably max out the integer cap :) (2.147 billion)
(commit: 5dace84)

Add changelog.md again so I'm not keeping track of changes in my head
all of the time.
(commit: 740487c)

Basic job scheduling commands. e.g: /lwc schedule create test2 cleanup,
/lwc schedule run test2. Next commit should allow something like: /lwc
schedule create weekly cleanup, /lwc schedule autoRun weekly 1 week.
Something like that, anyway!
(commit: 9d62fb1)

4.0.0-alpha3. Scheduler is complete and needs some minor changes and
localized into the localization files. A bunch of new commands attached
to it - changelog.md has the current commands ..
(commit: 16466b8)

Added the expiration job handler. To add arguments: /lwc schedule create
remove expire | /lwc schedule arguments remove -remove 2 weeks | /lwc
schedule autorun remove 1 week  - it removes protection + blocks of
protections that haven't been accessed in at least 2 weeks, every week.
[cc: MonsterTKE]
(commit: 348c3e5)

Update changelog
(commit: 1928f48)

- fixing umlauts
(commit: 40bd1be)

FULL removal of Memory Database. Every single usage of it has been
removed - gone. Still may be UNSTABLE and volatile; it has not be tested
extensively just yet !! [#53] The current implementation will be
smoothed out later on.
(commit: c1af71d)

Update changelog.
(commit: baa9804)

Fix a possible dupe exploit that when magnet was used alongside the
Showcase plugin would duplicate items.
(commit: c1b65d1)

misc changes
(commit: 8434a53)

Fix merge conflict (accidentally committed.) Double console output also
fixed on the latest CraftBukkit
(commit: 6b1ac9d)

Closes #98 - out of sync double doors can be fixed with /lwc fix or /lwc
fixdoor.
(commit: dd5361b)

The openAndClose feature of double doors has been given new life and
works fully as expected now. Double wooden doors now function more
gracefully, as well. #98
(commit: 17696f2)

Version comparator for semver compliancy. Parses versions as small as
3.47, but can also fully parse 4.0.0-alpha3 (b220). For example,
4.0.0-alpha3 (b221) would be greater than 4.0.0-alpha3 (b220), if
compared via this class. As would betas of the same version be greater
than alphas.
(commit: 82ff2b4)

Don't continue to look for release levels if one is already found
(commit: f5fb196)

Define possible update schemes and provide convenience methods for
versions.
(commit: a3d4571)

Change LWCInfo.FULL_VERSION to instead use the Version class.
(commit: 3a3e396)

3.48. You can now interchange 3.48 and 4.0.0-alphaX without NOT being
able to easily revert back. lwc.protect perm node now also default to
true #promote
(commit: 8cf1510)

Old, deprecated LWC events have been fully removed. All other
deprecation events have also either been fixed or hidden from sight.
(commit: 90ebad9)

Clicking on a password protection would actually ADD you to the access
list ..
(commit: f63f8ed)

Towny integration. Protections cannot be made outside of Towns, e.g the
wild. Set core.townyBorders to true. closes #99
(commit: 14ea6bb)

Fix piston exploit that allowed wooden doors and other minor
protectables to be destroyed via: PISTON -> BLOCK -> PROTECTED DOOR -
closes #77
(commit: 64bafbd)

Prevent sticky pistons from pulling away protections
(commit: ae5c269)

Shiny new updater + downloader (old one was scrapped.) At the moment, it
is by default set to update to ANY NEW BUILDS (BLEEDING EDGE) but is not
automatic by default. /lwc admin version will tell you if there's a new
build of the alpha out; /lwc admin update can auto update.
(commit: f1300fc)

Fix a typo, but this commit is mainly to make a build happen
(commit: 1b4941c)

4.0.0-alpha4 - All builds past this are now running on the new update
system; alphas can be updated to the latest alpha very easily now
without manual work. For automatic updating, set  core.updateMethod to
AUTOMATIC (note the caps), or you can manually update via /lwc admin
update
(commit: 90316da)

..changelog should be changed, too!
(commit: 34ba2d2)

Update changelog again with a feature added on a few days ago (ability
to expire protections with /lwc schedule)
(commit: 57622ea)

Fix minor bug when converting old rights
(commit: 5bdc1f5)

Fix double console output
(commit: a205b68)

3.49  #promote
(commit: 6b0f9b5)

Backwards compatibility with permissions 2/3 (without superpermsbridge)
for now
(commit: 187859b)

Backwards compatibility with permissions 2/3 (without superpermsbridge)
for now (again)
(commit: 2a7eca7)

3.50. Remove the permission metadata from defined commands so the
endless onslaught of "LWC throwing Dave error !" stops #promote
(commit: d6dd838)

Gracefully ignore iConomy4
(commit: bd5ec63)

Gracefully ignore iConomy4
(commit: 729864b)

Protection rights have been moved to the 'data' column in protections,
instead of its own. Any rights made to protections after converting to
4.0.0 (but not your 3.xx rights) will be lost upon updating. Also,
permission metadata has been removed for commands (same as 43ace80fbf)
(commit: 33751b1)

Renamer renamed a little bit *too* much
(commit: 8cf8dbd)

The command /lwc admin purgeregion <RegionName> [WorldName] has been
added to the WorldGuard module. If you are using it from the console,
you must also specify the world that the region is in. If the region is
in a different world than the player you use the command from, you must
again also provide the world name.
(commit: 26631cc)

Go around a bukkit bug with pistons
(commit: 807d0fb)

Proper Fix Issue #88, adds full SuperPerms support
(commit: 4082767)

Flags are now in data column and now support data as well. No utility to
set data yet, however. Also fixed a bug where some messages were not
sent to the player after they logged out and back in.
(commit: 9579810)

Default core.locale to en
(commit: 1a15bbc)

Avoid a possible arrayoutofboundsexception
(commit: 2d527cd)

Fix Cleanup
(commit: a468a9c)

Fix /lwc admin cleanup, for real
(commit: e893b7c)

Fix override bundles
(commit: a22cc68)

update thread was not synchronizing, and /lwc admin purge was borked.
Thanks Joy
(commit: 9123e8c)

/lwc admin reload should also reload the loaded locale. And so it shall.
(commit: f8008fa)

/lwc admin dump locale! It dumps the current loaded locale into
plugins/LWC/locale/lwc.properties. Along with /lwc admin reload, it'll
be a ton easier to create custom locale messages now :)
(commit: 99429e1)

Allow LWC.instance to be set again
(commit: 5cb4429)

Fix resource loading - it "should" fix reloading after a new LWC.jar is
thrown in plugins/
(commit: 318b41a)

revert those last changes
(commit: 45bcd27)

Try something so crazy it might just work
(commit: 5d3de7a)

LWC *SHOULD* reload okay now after a new LWC.jar has been downloaded
into there
(commit: 8e88550)

We are now 4.0.0-alpha5 - all builds from this point on can be loaded
with /reload without breaking LWC
(commit: 7cf698f)

if core.locale was set to a locale that didn't actually exist,
complaints would be had. No more, I say
(commit: c593a98)

default lwc.protect to false again [superperms]
(commit: 195bff9)

default lwc.protect to false again [superperms]
(commit: e3249a2)

3.51 - default lwc.protect to false again (superperms) #promote
(commit: 37f77bf)

Use Set<> for flags/access rights and also don't let null objects in
(derp)
(commit: 2aa2811)

Should fix Permissions 2/3 errors
(commit: 2bf370f)

Really does fix Permissions 2/3 errors.
(commit: a73ee5f)

Some null checks
(commit: 9647301)

3.52 #promote
(commit: 6129890)

Show the parser who's boss - i'll give you some input to match
(commit: 66bc1a1)

Add the AUTOCLOSE flag which will make doors automatically close after 3
seconds (configurable in plugins/LWC/doors.yml). /cautoclose on|off,
/lwc flag autoclose on|off. Flags are also settable again (oops)
(commit: 1961bb7)

and the changelog should take note, too!
(commit: 3a9561c)

lwc.flag.autoclose should be defined, too ...
(commit: c46b3f9)

fix plugin.yml
(commit: 581b0ae)

Permissions 2/3 getGroups () support with our fallback hacks
(commit: c68921a)

misc code from last night. Nothing special, just an empty /lwc setup
command
(commit: 1d11c7c)

in regards to #88 - removes reliance on Permission plugin-specific
methods to check for permissions and instead defaults to Superperms.
Legacy Permissions 2/3 support is for the most part dropped in this
build and can be supported with SuperpermsBridge.
Conflicts:

src/main/java/com/griefcraft/integration/permissions/BukkitPermissions.java
src/main/java/com/griefcraft/integration/permissions/NijiPermissions.java
src/main/java/com/griefcraft/integration/permissions/PEXPermissions.java
src/main/java/com/griefcraft/integration/permissions/SuperPermsPermissions.java
src/main/java/com/griefcraft/lwc/LWC.java
(commit: c06d7eb)

Permissions 2/3 getGroups () support with our fallback hacks
Conflicts:

modules/core/src/main/java/com/griefcraft/modules/flag/MagnetModule.java
(commit: 0fca3ae)

I didn't ask for that method, mr. mergetool
(commit: a19fd6f)

Default lwc.protect to true
(commit: 6eb60eb)

3.53 #promote
(commit: fb4756c)

Default lwc.protect to true
(commit: fb971e6)

and lwc.admin to false
(commit: 4d5f265)

Do not show locale messages defined as 'null'
(commit: 47a501e)

Add t:TownName and town:TownName for Towny integration for /cprivate and
/cmodify. Allows residents of the town named to access that protection.
(commit: 0c46aa2)

/lwc admin expire always showed "Expired 0 protections", even if it
removed some >_>
(commit: 9eb014e)

Closes #105 - add lwc.autoregister perm node to allow a player/group to
auto protect all LWC protections to private. not as configurable as it
should be at the moment, however :)
(commit: f4a243c)

Oops
(commit: 863d34e)

Add andrewkm under donations header in credits. And a few others under
'And...'
(commit: 9769887)

Oops, duplicate
(commit: 653ecf0)

Store the known Protection object for History objects early on to save
queries and possible issues later on
(commit: 784abf4)

switch back to delayed insert for the initial history obj on a
protection
(commit: 0852310)

Automatically fix chest block faces from pre-1.7 maps. Also, /lwc fix
will set the chest's face to face towards you, incase it's not facing
the way you want it to :)
(commit: 3ab7de2)

whitespace!
(commit: 003c55d)

Equivilent methods for fixing chest face to the dev branch!
(commit: be3734d)

Equivalent of 94c5b458 for dev branch, but had to retrofit what I
already had instead.
(commit: 261d0f4)

The magnet module was not queueing items properly
(commit: e3e39a6)

Apply blacklist checks before entities are queued for the magnet flag
(commit: 47513b3)

Disable lwc.autoprotect for now
(commit: ebf142c)

Limits will now instead use the group with the highest limit.
(commit: 029b50a)

Update changelog
(commit: 5f01c34)

Destroyer of a protection was not being added to the history on
/cremove. Instead hooked into onPostRemoval which should've been done
originally..
(commit: 8e3fc01)

LWC-Economy + No Econ plugin = Sad Times, but who would try that,
anyway?
(commit: 757d225)

HistoryModule
(commit: 1f160d9)

(and remove from destroymodule)
(commit: 2a488b7)

Add /lwc history. Allows the viewing of all history items for a player
(or everyone.) Dynamic arguments allow you to use the player name or
page name anywhere:   /lwc history, /lwc history Hidendra 2, /lwc
history 2 Hidendra, /lwc history 2, and /lwc history Hidendra   are all
valid and will work! Later on, will work hand-in-hand with /lwc details
<HistoryId>
(commit: 0328e82)

Create /lwc details (it does nothing, however)
(commit: 2cbe6b5)

Add /lwc details which allows you to view some more info known about a
history item
(commit: 4512741)

The player who destroyed a protection was always being shown as the
owner of the protection - reverted to how it's done before and fixed
/cremove not modifying the history items
(commit: 009eca5)

if a non-SuperPerms perms plugin is present, ignore SuperPerms (I'm
looking at you, Permissions 2/3 :3)
(commit: 7d20dc1)

4.0.0-alpha6. LWC is now licensed under the 2-clause BSD license. All
versions before this point are still under the GPL.
(commit: e4fb181)