A make a plugin api...

[cerulean dagger]

why code berg

[small pumice]

Why not Codeberg?

[cerulean dagger]

cus not everyone use codeberg

[small pumice]

So? Not everyone uses GitHub either

[cerulean dagger]

alright bro u win

[small pumice]

I only wanted to understand your question

[severe sphinx]

Because I'm too lazy to configure the GitHub token

[mint moss]

github token? like the remote?

[mint moss]

Perhaps zoidd was just surprised at something that wasn't github, like I was...

[fathom quarry]

Always fun to see new API approaches!

A few criticisms:

• I'm not seeing the benefit of making wrappers of everything - like the block wrapper is pretty much the block class with added helper methods to get the relative blocks (up() -> getRelative(BlockFace.UP))
• If you're going to wrap every Paper API event, that's going to be very time-consuming for you
• The command API appears to be missing a lot of modern comforts like brigadier registration

And the always-criticism for something like this: What happens to someone who becomes dependent on this if you decide to stop maintaining it?

[severe sphinx]

This API might not survive as a plugin for long... I just wrote it on a whim.
But who knows what will happen later.

[split ridge]

There are a lot of reasons, has great features and is maintained by a non profit (and has higher uptime even tho being a lot smaller, not backed by microsoft and gettind ddosed all the time)

[severe sphinx]

Alright... I'm considering refactoring this API... keeping only CommandBuilder, Item, and Messager.
Completely wrapping the Bukkit API really does seem impractical.

[mint moss]

Is codeberg compatible with Git?

[split ridge]

Only with git afaik, but well that's the standard for version control anyway

[mint moss]

afaik...?

[warm bear]

It seems it's archived

[daring pelican]

afaik → As far as I know.

[fathom quarry]

@severe sphinx shall I close this down then?

[severe sphinx]

ok..