- Priority: Normal
- Number: 586
- Type: Bug
- Status: Accepted
- Age: 12 Days
Description
The problem is best shown with the results (and queries underneath) taken at the same time: http://puu.sh/2yHZa/aee7e79564 http://puu.sh/2yHZB/3875e3b2b6
Unless I interpreted the documentation incorrectly, it seems to be a bit aggressive in culling information, and more importantly inconsistent. A piston move event is shown for both, but the non-extended one excludes the ones I just did before.
History
dykam April 12, 2020 4:44 PM
Issue reported.
botsko April 12, 2020 4:52 PM
It's an issue caused by the fact that we don't group by dates. I've debated doing that to better conform to SQL standards but there's some trickiness around it too. If there are multiple piston move events, we group by the action type, player, block_id, and data but if they occur twelve hours apart we can only use one of those dates. By showing the results individually, we can use the correct date for each event.
I'll see what I can do to better group by dates.
- Status → Accepted
Update Issue
Add your comments to this issue!
Creating a free account will let you immediately report issues on this project, as well as comment on existing issues, save your filters, and more!!
