Skip to content

Conversation

jamierocks
Copy link
Member

@jamierocks jamierocks commented Dec 23, 2017

Preface

This PR marks the beginning of CanaryLib 2.0 - plugins may well break
This PR is built off some work that I did way back in early 2016, in preparation for 1.10(?)

Changes

  • 1.9
    • Attributes
    • Criteria Types
    • Particle Types
    • Statistics
    • Arrow Types
    • Block Types
    • Enchantments
    • Potion Effects
    • Tree Types
    • Sound Effects
  • 1.10
    • Block Types
    • Polar Bear
    • Sound Effects
    • Particle Types
  • 1.11
    • Particle Types
  • 1.12
    • Dependency Updates
    • Advancements
      • Remove old Achievement API
      • Introduce Advancement API

Since this PR will become CanaryLib 2.0.0, this PR will eventually address some of the following:

  • Removal of MC version specific APIs (e.g. packet/protocol API) note that these APIs may become available through a separate library, that is versioned with MC - as such plugins will be able to specific which MC version they target, and Mod won't run then on other versions
  • The replacement of Logman, perhaps with slf4j?

@jamierocks jamierocks self-assigned this Dec 23, 2017
*/
public Logman getLogman() {
return Logman.getLogman(getName());
public Logger getLogger() {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is not just likely to break all plugins but will 100% make all old plugins unable to be loaded.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah - Canary is going to start following semver, and this will be a major version bump, all plugins should expect to break.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are you on Telegram? Throw me your handle and I'll get you in chat.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants