Just in time for my birthday did my plugin AdvancedServerList reach 25 thousand downloads on Modrinth1.
This is a number I've never expected to reach here. So as a small thank you am I sharing some snippets of the plugin's development throughout the past 3 years and how it evolved to what it is now. Enjoy.
fediverse:creator meta tag for blog posts in MkDocsMastodon 4.3 added a feature, where links to sites can display an author affilialtion, linking to a Mastodon account associated with that site.
This feature works through the usage of a meta HTML tag containing a specific name and content value.
This small blog post explains how you can add this tag to Blog posts of your MkDocs site.
The term "Status Quo" in its most basic description means "The current state" of something.
Many things have a Status Quo the community accepts and/or tolerates, including Games.
I want to take the time and talk about why some of the things accepted as the overall norm is not a good idea, nor a good excuse for others to implement.
I provide support for the Premium Plugin ItemsAdder. And throughout my time doing this have I encountered lines like these:
Some of these lines may sound extreme, but I've encountered them before at least once. And not just with ItemsAdder, but also other (often times not even premium) plugins.
And they all have one thing in common most of the time: The user thinks they have a right for support, because they bought (or simply use) the plugin. This couldn't be further from the truth.
The Essential Mod1, not to be confused with the Essentials Plugin2 or its updated Fork EssentialsX3, is a mod that tries to be a all-in-one solution for players similar to what you imagine with Mods like LabyMod4 or the 5zig Reborn5 Mod.
The issue here is, that it has a lot of problems, making it a worse mod and not really a good choice to begin with. This post will cover all the points I managed to gather from the community over the years I've heard of this mod. Enjoy.
If you're developing a bot with JDA1, changes are high that you want to implement a system where your bot is waiting for an input from the user after performing a command or action.
Doing this in JDA can be a bit tedious, especially if you want it to do things such as having the action expire after no input for a while. This is where JDA-Utilities2 comes into play. And this is where this blog post will explain how to use it and especially its EventWaiter functionality.