[nodebb-plugin-minecraft-integration] Minecraft Integration!
-
He, I was just trying this out, and on NodeBB 0.8.1 its impossible to add a server since the pop up to add a new server doesn't pop up.
Nevermind! I am a potato! And forgot to install the plugin. -
It still looks functional. Just need to test it with a friend who runs a Bukkit server.
-
I'm all new to NodeBB, I might sounds nooby but I have to be taught some way or another.
I have no clue how to head to the setup page, I am in the "Installed Plugins" section but I can't figure out how to go to the "Minecraft Integration" page to configure the plugin.
Thank you for reading.
-
@Victhetiger After you Install the plugin and Activate it on the Installed Plugins page, restart NodeBB then refresh the admin page. There should now be a "Minecraft Integration" link under the main Plugins menu.
-
@Archeon Interesting idea, it would work well with some of the future plans I have for the plugin.
I checked out a few of the most popular voting sites, and only some of them had an exposed API, I'll have to investigate further and possibly contact them.
Which of the voting sites are you most interested in? I'll make sure I get it working with them first.
-
http://minecraftservers.org/
http://minecraft-server-list.com/The two major ones at the moment server / network owners care about.
-
@yariplus plugin doesn't show up, in admin menu
I'm using nodebb 0.9.0 and i tried installing through npm, ACP and grabbing the latest version from git. If you have any ideas what I'm doing wrong, that be really nice, request logs and I'll send you whatever you need!edit: and yes I activated the plugin in the ACP
edit2: figured it out, the plugin needs lwip a requirement which isn't specified for whatever reason as dependency, to fix run "npm install lwip" in the nodebb root folder -
@phit said:
@yariplus plugin doesn't show up, in admin menu
I'm using nodebb 0.9.0 and i tried installing through npm, ACP and grabbing the latest version from git. If you have any ideas what I'm doing wrong, that be really nice, request logs and I'll send you whatever you need!edit: and yes I activated the plugin in the ACP
edit2: figured it out, the plugin needs lwip a requirement which isn't specified for whatever reason as dependency, to fix run "npm install lwip" in the nodebb root folderAhh, thanks for the heads up. As @julian says, lwip was originally in core, which is why I don't have it in dependencies.
Jimp definitely looks doable. I'll switch to that asap.
-
Grr, jimp doesn't have the nearest-neighbor algorithm I require.
-
v0.6.0 Changes
This plugin now REQUIRES the Bukkit plugin NodeBB-Integration
The plugin no longer pings or queries Minecraft servers, you need to add the plugin's API key to your NodeBB-Integration config in order for this plugin to work. This means you can no longer add a widget of someone else's server, and you may have trouble configuring this plugin if your server uses an old version of Minecraft. I made this change for my own sanity. Interpreting pings and queries added a lot of complexity to the code. Interacting with a Minecraft plugin is much cleaner and simpler to code, and now I can more easily add new features.
New Features
Admin page now has tabs showing all data cached in the database with some buttons for management.
Configurable avatar borders and chart colors are back.
Added extra Widget color options.
Added an Avatar CDN for Mojang (now the default) and The Brony ModPack.
Added a Steve default avatar if the configured CDN fails.
Chat widget now sends web messages to the server.
Redid a lot of the client scripts for better loading times.
Changed image manipulation library from lwip to jimp.
Vault Integration: The plugin will now add the Vault prefixes of your player to your forum name.Note: Upgrading to 0.6.0, you will lose all of your <v0.6.0 settings.
-
@Kowlin It's very much alive at the moment.
From what I can tell, the DMCA thing was a case of license abuse from one of Bukkit's own devs. Do to the viral nature of GPL, the dev was able to make some rather ludicrous claims. And since Repo's would rather not get involved in legal concerns despite the circumstances, they shut it down immediately. The situation seems to have ironed itself out, devs with local access to the code removed the salty dev's commits and development continues.