Enchantments Concept

Socratic_Phoenix · February 12, 2016, 7:52pm

I’ve created a custom enchantment system, and started to implement some of it. Currently only the “Smite” enchantment is implemented. I figured I’d share what I’ve got so far, so here’s a proof of concept video:

For anyone interested in how it’s done, the basic idea is that there are 2 implementable elements, Enchantment Handlers and Event Processors. The Enchantment handlers, obviously enough, handle enchantments, and function as doctored event listener type things. Event Processors are responsible for determining whether or not a certain event should be considered, and for obtaining all the enchanted items associated with the event.

The Smite enchantment implementation can be found below:

gist.github.com

https://gist.github.com/SocraticPhoenix/9f956e1dbed4dd7240bd

SmiteEnchantment.java

/*
 * The MIT License (MIT)
 * 
 * Copyright (c) 2015 [email protected]
 * 
 * Permission is hereby granted, free of charge, to any person obtaining a copy of this software and
 * associated documentation files (the "Software"), to deal in the Software without restriction,
 * including without limitation the rights to use, copy, modify, merge, publish, distribute,
 * sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is
 * furnished to do so, subject to the following conditions:

This file has been truncated. show original

doot · February 12, 2016, 8:18pm

It would be quite nice if Sponge had a custom enchantment API.

Aaron1011 · February 12, 2016, 9:00pm

This won’t be possible without a client-side API. In almost all cases, the server sends enchantment ids to the client, which requires them to be registered client-side.

Socratic_Phoenix · February 12, 2016, 9:03pm

I think @DotDash means ‘fake’ enchantments, that run server side and stuff, but are independent of Minecraft’s actual enchantment system.

I mean, that’s how what I did works in the first place… Still trying to make the items shiny though…