This change adds a new config option, logEnvironmentalKills. When set to true,
Logblock will record entity deaths not directly caused by another entity.
(for example, suffocation, or burning to death)
- Allow use of "both" as a query parameter. This will search for created and destroyed blocks, but not chestaccess. This is useful for situations where the query defaults to "all" e.g. rollbacks. Fixes#210, #252
- Add block negation query parameter. Like with player names, you can now precede a block name with "!" to query for all except the specified blocks. Fixes#452, #216
- Allow use of area parameter with location parameter, as long as location is specified first. Fixes#458
- Better error when asking for kill log without world specified
- Don't try to process events where the block is null. Fixes#463
- Replace problematic characters in world names with underscores when deciding on a default table name. Fixes#409
- Adjust for cocoa beans having reversed attachment direction in smart logging
- Prevent out of bounds exception if a single-word timespec ends in a number. Fixes#354
- Prevent error when specifying a killer or victim in a teleport lookup. Fixes#333
As there are more inventory types now, it is worthwhile including the inventory name in the output
e.g:
11-07 20:47:15 frymaster took 64x iron ingot from furnace
11-07 13:42:14 frymaster put 1x iron ingot into beacon
As there are more inventory types now, it is worthwhile including the inventory name in the output
e.g:
11-07 20:47:15 frymaster took 64x iron ingot from furnace
11-07 13:42:14 frymaster put 1x iron ingot into beacon
Make a decison on whether or not to return chest access data based on the
BlockChangeType (ALL or CHESTACCESS) rather than partly on the block parameter
as these are the only two query types that don't enforce type != replaced
This is helpful because the list of blocks to request chest access for was
outdated and is duplicated in 3 different places, whereas the new method
will return whatever results have been logged regardless of type.
In addition, if the query type is CHESTACCESS (but not ALL), we can use
an alternate query that is vastly more efficient. In tests (26 million
row log table, 400,000 row chest table) the query time for all chest results
was reduced from 30 seconds to 3.
Allows the chestaccess parameter to return data from the following inventory types:
- Brewing stand
- Trapped chest (fixes#483)
- Dropper
- Hopper
- Beacon
Note that this only affects lookup of logged items; the logging process has not
been touched, so #433 and similar have not been addressed
Also, update the list of valid container types, which will improve logging of
broken containers.
An INSERT IGNORE query will still increment when using innodb, even if no row is inserted. We can work around this by using a slightly convoluted query, but this only works if the table is non-empty, so also check for that on startup and create a dummy record if necessary.
This commit adds the ArrayIndexOutOfBoundsException to onCommand's exception-catcher. This is so the user gets more specific information than "Error, check server.log" when they don't give any arguments.
We just ran into the problem where new users didn't make any edits and after some digging I just found out why:
The playerid in the kb-players table was a SMALLINT. Changing that to an INT should work for some more years now ;-)
Philip Cass
md-5
Sahir
Marcos Vives Del Sol
Ammar Askar
frymaster
Dark Arc
Björn Teichmann