Search results

  1. AuroraLS3

    Plan | Player Analytics

    AuroraLS3 updated Plan | Player Analytics with a new update entry: Login Page - Change log 5.1 build 545 Read the rest of this update entry...
  2. AuroraLS3

    Plan | Player Analytics - 5.1 build 505

    5.1 build 505 This update fixes some corner case bugs and a security vulnerability in the password brute-force protection. More details below. Change log Data gathering Fixed lag on some operating systems when gathering CPU load during high CPU activity by moving CPU, RAM and Disk Space...
  3. AuroraLS3

    Plan | Player Analytics

    AuroraLS3 updated Plan | Player Analytics with a new update entry: 5.1 build 505 Read the rest of this update entry...
  4. AuroraLS3

    Plan | Player Analytics

    AuroraLS3 updated Plan | Player Analytics with a new update entry: Change log 5.1 build 497 Read the rest of this update entry...
  5. AuroraLS3

    Plan | Player Analytics - Change log 5.1 build 497

    More bugfixes to reported issues Bugfixes Fixed Html customized resources being overwritten & not being used Fixed ERR_INVALID_REDIRECT when server.properties has empty IP Possibly Fixed ERR_TOO_MANY_REDIRECTS with default server name Fixed Some error pages not having css Fixed /server/Server...
  6. AuroraLS3

    Plan | Player Analytics

    AuroraLS3 updated Plan | Player Analytics with a new update entry: Bugfixes - 5.1 build 486 Change log Read the rest of this update entry...
  7. AuroraLS3

    Plan | Player Analytics

    AuroraLS3 updated Plan | Player Analytics with a new update entry: Bugfixes - 5.1 build 486 change log Read the rest of this update entry...
  8. AuroraLS3

    Plan | Player Analytics

    AuroraLS3 updated Plan | Player Analytics with a new update entry: 5.1 build 474 - Page Extension API Read the rest of this update entry...
  9. AuroraLS3

    Plan | Player Analytics

    AuroraLS3 updated Plan | Player Analytics with a new update entry: 5.0 build 415 - Change log Read the rest of this update entry...
  10. AuroraLS3

    Plan | Player Analytics - 5.0 build 415 - Change log

    5.0 build 415 - Change log This is a bugfix release Bugfixes #1332 Fixed error in BentoBox Extension #1333 Fixed common error with 'string_value' String truncation on MySQL. This was a regression bug due to my refactoring and affected multiple extensions that stored String values over 50...
  11. AuroraLS3

    Plan | Player Analytics

    AuroraLS3 updated Plan | Player Analytics with a new update entry: 5.0 build 410 - Change log Read the rest of this update entry...
  12. AuroraLS3

    Plan | Player Analytics - 5.0 build 410 - Change log

    5.0 build 410 This update brings some bugfixes that have been ready for a while, I've just been super busy and haven't had time for releasing them. In addition to this I've begun work on Page Extension API which will allow adding new pages to Plan by other plugins. This seems to be a pretty...
  13. AuroraLS3

    [Solved] Is EntityDeathEvent fired when PlayerDeathEvent is fired?

    Hi. On Bukkit EntityDeathEvent fires when PlayerDeathEvent is fired, allowing to use this event for player deaths as well by checking if Entity dead = event.getEntity(); if (dead instanceof Player) { However I got a report that says that player kills are not recorded (I'm using the...
  14. AuroraLS3

    Nukkit 2.0 Alpha

    Please consider writing a shim for PluginBase.getLogger() (PluginLogger) - It's likely the one method that every single plugin calls, making every plugin incompatible with 2.0, without warning as it was never even deprecated. - The alpha version also crashes because this method doesn't exist...
  15. AuroraLS3

    Plan | Player Analytics

    AuroraLS3 updated Plan | Player Analytics with a new update entry: 5.0 build 382- Change log Read the rest of this update entry...
  16. AuroraLS3

    Plan | Player Analytics - 5.0 build 382- Change log

    5.0 build 382- Change log New Added Webserver.Security.Disable_authentication setting This setting allows disabling Plan authentication when https is set up, and it defaults to false to avoid previously secured servers from being exposed. Added %plan_player_favorite_server% placeholder...
Top