• Very cool world-generation with awesome structures and loot chests
• Very strong theme integration with Enderium, Dragon Scales and adding world-gen to the End
• A lot of content with quite unique items

• Loot chests seem very overpowered
• The Dust Fabricator throws a lot of stacktraces into the console
• Your code violated a lot of naming conventions (e.g. nahkdSchematic2.java), lots of one-liner functions
• Your pom includes a local file:// repository which will break on anyone trying to work on this
• Don't use Random#nextInt() in a for loop if you are not gonna use it, let that entropy come from the algorithm itself
• Lots of missing access modifiers which could lead to unexpected results
• Redundant classes with some unneeded utilities, part of which are already in Slimefun
• Seemingly unnecessary static fields, some unused class
• Lack of visual cues on machines, the guide could display their recipes for example

Feature-wise this is really awesome but the Code Quality leaves a lot of room for improvement.
The idea of adding structures to the end was really good and on point with the theme.
This Addon adds a ton of items and content and introduces some really nice concepts.
But internally it lacks quite a bit of work and isn't the most user-friendly too.

• Very interesting mechanics with lots of stuff to keep you occupied, even endgame items to work towards
• Very cool machines that see their inspiration in Quantum Mechanics
• Awesome visual effects
• Lots of content
• Very user-friendly items, even comes with a written book explaining you everything

• Code-wise a few naming conventions were violated, such as the package name "Lists".
• You should never store a Player Object in a collection, it will lead to severe memory leaks
• Your custom RecipeType extends RecipeType but you never use instances of that class, you only ever use the static fields which defeats the points of inheriting from that class
• Way too many unneeded static imports, some rather redundant API classes, the architecture seems kinda copied from Slimefun
• The guide should probably be craftable, as players can be rather stuck without it and a Server could add the plugin mid-way through
• Very few items actually revolve around "The End", it seems like the theme was mostly ignored here except for some end-related machines or machines that "only work in the End"

A very user-friendly plugin with many awesome mechanics. Really a very unique addon for sure with lots of stuff to keep you occupied. The code does contain some rather bad practices though and the theme was mostly ignored.

• Lots of fun to play around with the items, especially the Panda Bazooka.
• Quite a few items but none of them are boring or a waste of time
• Some nice Theme incorporation with Mythril and other items

• Mythril is almost impossible to find and the code behind it is really not good at all.
• Some items are way too overpowered
• The code is quite inefficient, especially because you perform up to 4 map operations that could have all been reduced to one
• Lack of a README file, just pointing it out there, the README was not subject to the review
• Some formatting errors
• Lots of hardcoded values, such as world names
• You should always declare constants as "final", especially your collections in MainListener which shouldn't be static btw
• Never compare Enums using .equals(), always use the == operator
• Single-line functions

There is not too much to say about this addon, it's fun. But the code has a lot of room for improvement but is despite all those comments rather clean in general. The Theme was incorporated somewhat good.

• Very cool concept of repairing tools
• Nice ideas and items are fun to use
• Very accurate implementation of the theme
• The Trapped Shulker is just ingenius

• The Category has a very generic name
• Several naming conventions have been violated (e.g. "deepFreezer")
• Empty classes ("RandomInt")
• Uses static and star imports where it may cause some harm
• EnderStaff and EnderStaff2 class should probably be merged into one super class
• Sometimes == was used where .equals() would have been correct, huge potential for bugs there
• Version 12 really breaks some conventions there, should better use semantic versioning
• Your git setup hasn't been configured correctly, it's not linked to your GitHub Account
• You have all classes in one single package, you should group them in subpackages
• You seem to call a FoodLevelChangeEvent manually which does not really seem to make any sense?
• The ideas were good but content-wise we think it lacked a little "Innovation" there.

The plugin is fun and interesting. It is a good interpretation of the theme too. However the items all seem rather basic, which isn't inherently bad but costs a little on the "Innovation" score. The code is mostly clean but contains a couple of bad practices and goes against a few conventions.

• Very clean code
• Ideas are fun and quite a cool gimmick
• Nice particle effects

• Lack of visual cues
• Missing lore, not even a line stating that a machine needs power
• A bit buggy, all armor recipes are broken since they use illegal shapes for the Ancient Altar, missing catalysts
• A few redundancies in the code
• Misconfigured pom.xml, a system-dependent output file
• The version inside the plugin.yml is not automatically inferred by the pom.xml which leads to inaccurate or redundant versioning
• Missing researches
• Quite few content

The code is very clean and this addon is fun. However it isn't as user-friendly as it could have been and the mechanics do not really challenge the player a lot. It's good but small.

• Very innovative ideas, quite a unique system
• A new Research System that is definitely something new
• Nice addition of random research notes, especially that it incorporates the "Luck" effect
• A nice Quarry
• Utilisation of Lombok to reduce complexity
• Cool concept of spells and wands

• This Plugin does not even compile in the first place, you used "Spigot" as a dependency when it should have been "Spigot-api" at least
• This is also a Spigot-exclusive title, meaning it only works on Spigot, this will impose a very unnecessary limitation to the user
• No checks were made whether this "Spigot-exclusivity" condition is met, on CraftBukkit most stuff will simply refuse to work and throw errors, errors which could have been handled by the code
• The Void Attractor does not work, as it wants to act like a block but is an Entity, this was fixed in post but sadly only after the Jam had already ended, so we cannot take that into account for our review
• You can take items out of the Void Research Bench if timed correctly
• The Research Bench throws a NullPointerException on every tick if you manage to remove an item from it
• The lore is very colorful and hard to read, also conveys little information on how to use these items
• The Theme seems mostly ignored, the End was simply replaced with "Void", however we couldn't really find any links back to the End dimension or other End-related things at all
• The Research Table is very slow and not too user-friendly
• The code is very hard to read as it is all very cramped and unconventionally formatted
• The code is quite often very inefficient, frequent calls to ItemStack#getItemMeta() which create a new instance on every call
• Way too many and completely unnecessary Objects.requireNonNull(...) checks which just add unnecessarily complexity
• Objects.requireNonNull(ItemMeta) is a tautology, it will always be true and it will create a new ItemMeta object which will just waste computational resources, such as RAM or CPU usage
• Usage of YAML for machine serialization which is slow and inefficient, this should also have been implemented on a higher level rather than in the addon itself
• Redundant setInstance() method
• The api-version in the plugin.yml is specified as "1.13" but the project itself is built against 1.15
• The version inside the plugin.yml is not automatically inferred by the pom.xml which leads to inaccurate or redundant versioning
• Cramped one-line functions
• RegEx patterns are compiled at runtime which is very slow but done repeatedly throughout the code, these should be compiled once and then be re-used instead. Most common patterns are also already included in Slimefun itself, see PatternUtils
• When comparing user input Strings, you should use .equalsIgnoreCase()
• random.nextInt(2) == 0 should really be changed to Random#nextBoolean()
• Potential memory leak: Not removing Player UUIDs from Maps on every possible occasion, such as server-leaving or kicking, small but can stack up on large servers
• Void Bag's Namespaced Key violates the format of namespaced keys, use "bag_location" instead of "bagLocation"
• Needless creations of instances of Random for every instance of a custom VoidMenu
• Overuse of return; statements, a proper if/else structure is usually considered more readable
• static instances are never nullified on plugin disable, not that server reloads are encouraged but this will make them a lot more severe, especially not nullifying the plugin's instance
• On many occasions you add @Getter or @Setter annotations to almost every field, Lombok also allows you to add that to a class to add it for all fields at once
• Your persistent data calls could have been handled by CS-CoreLib2's PersistentDataAPI which automatically returns an Optional too
• Over use of ChatColor.SOMETHING when you could just use '&x' instead to make it more readable
• You shouldn't loop through values and then perform a .get() operation, Map#entrySet() exists for this very reason and saves a ton of performance

Generally good ideas, very innovative for sure. But the Theme seemed a bit neglected, the code is very slow and inefficient, lots of redundancies and bad practices but mostly just inefficient. The plugin is a Spigot-exclusive title which is rather discouraged, especially if not using Spigot just causes tons of errors rather than a proper handling of that circumstance. It generally contains quite a few bugs and the code looks more like a "proof of concept" rather than a thoughtfully crafted system. It definitely scores in Innovation, Gameplay and Creativity but the code quality and accuracy sadly make this land on the last place. We also had to deduct some points on Gameplay and Mechanics due to all the bugs we encountered and the fact that this only works on Spigot.