This sound interesting. What makes it superior to something that already exists like bukkit or spigot? I've never made a plugin for a completely server side api, but I would probably like to at some point.
Although Spigot optimizes Bukkit, Spigot is not multi-threaded. Since, Spigot/Bukkit is not multi-threaded, that means that it doesn't use all of the resources available in the CPU. It's just wasting there. With Torch, you get a faster server by using all of the resources and threads in the CPU.
Let me compare this with Sponge.
Faster Updating
Sponge currently has a implementation in Forge, and Forge takes time to update because of the release of MCP and updating their API. Thus, making Sponge's implementation slower to update.
Faster server
Our server modification to the default Minecraft Server allows the server to use multiple threads to make use of the resources available in the CPU and making tasks concurrent inside of the threads, thus making the server faster. (unlike Sponge, Bukkit, Spigot)
Let me compare this with Trident and TridentSDK.
The Trident project is more mature, and introduces multi-threading, we still have advantages to Trident as well too.
Injects into NMS (net.minecraft.server)
Torch injects into NMS, thus making it easier and faster to update than Trident because Trident is made from scratch and needs some networking changes for their server software to upgrade to the next version of Minecraft.
[TORCHSRV-4] Implemented a plugin command (/pl, /plugins, /plugin)
TorchAPI Update:
[TORCHAPI-11] Torch class has been added methods!
[TORCHAPI-12] ChatColor class has been implemented! (ChatColor.GOLD, etc)
Build 3 will be released today, however we're almost done adding the features for the first full alpha release. So, don't expect tons of more features; because after this build; we'll start optimizing and fixing bugs on the software.
We've just announced our BuildTools and our first alpha stable release! Check our post to see our downloads section in the main post to see how to build/create a JAR to make a server from!
TorchServer Update:
[TORCHSRV-1] Fixes loader loading only class files.
[TORCHSRV-2] Allows CLI mode and GUI mode.
TorchAPI Update:
[TORCHAPI-1] Logger implemented
Very close to alpha release!
TorchAPI Update:
[TORCHAPI-2] Implement a location class
[TORCHAPI-3] Implement a entity base interface class
[TORCHAPI-4] Implement a player class
[TORCHAPI-5] Allow getting a player using a username from the Torch class
[TORCHAPI-6] Allow getting a player from a UUID from the Torch class
Compiling and testing release! Will be releasing today!
TorchServer has been released with TorchAPI!
Torch is now multi-threaded!
TorchServer Update:
[TORCHSRV-3] Optimized Torch to be multi-threaded.
TorchAPI Update:
[TORCHAPI-7] Commands are implemented and can be registered.
[TORCHAPI-8] CommandSender and a MinecraftCommand interface has been implemented.
[TORCHAPI-9] Configuration is implemented.
[TORCHAPI-10] Torch main class has been updated to allow registering commands.
TorchAPI will get some bug fixes and build 2 will be released today.
TorchServer and TorchAPI has been updated to build 2, build 1 has been deleted!
Website has been released!
This sound interesting. What makes it superior to something that already exists like bukkit or spigot? I've never made a plugin for a completely server side api, but I would probably like to at some point.
Animate your minecraft builds with Animated Structures: Link Removed
Torch releases, builds, and updates are available at our forums at: http://torchproject.byethost31.com
@Sgt_SuiZ
Hi, thanks for showing interest.
Let me compare this with Bukkit/Spigot.
Although Spigot optimizes Bukkit, Spigot is not multi-threaded. Since, Spigot/Bukkit is not multi-threaded, that means that it doesn't use all of the resources available in the CPU. It's just wasting there. With Torch, you get a faster server by using all of the resources and threads in the CPU.
Let me compare this with Sponge.
Sponge currently has a implementation in Forge, and Forge takes time to update because of the release of MCP and updating their API. Thus, making Sponge's implementation slower to update.
Our server modification to the default Minecraft Server allows the server to use multiple threads to make use of the resources available in the CPU and making tasks concurrent inside of the threads, thus making the server faster. (unlike Sponge, Bukkit, Spigot)
Let me compare this with Trident and TridentSDK.
The Trident project is more mature, and introduces multi-threading, we still have advantages to Trident as well too.
Torch injects into NMS, thus making it easier and faster to update than Trident because Trident is made from scratch and needs some networking changes for their server software to upgrade to the next version of Minecraft.
A example repository for making plugins has been released on the main post!
TorchServer Update:
[TORCHSRV-4] Implemented a plugin command (/pl, /plugins, /plugin)
TorchAPI Update:
[TORCHAPI-11] Torch class has been added methods!
[TORCHAPI-12] ChatColor class has been implemented! (ChatColor.GOLD, etc)
Build 3 will be released today, however we're almost done adding the features for the first full alpha release. So, don't expect tons of more features; because after this build; we'll start optimizing and fixing bugs on the software.
Build 3 has been released! Please view our forums to download the release.
(http://torchproject.byethost31.com/index.php?threads/torch-server-for-1-8-alpha-build-3.2/)
Information has been released on Torch API cross-compatibility feature, please visit this forum link: http://torchproject.byethost31.com/index.php?threads/torch-api-cross-compatible.4/
New post has been released with source code!
All gradle issues are fixed.
We've just announced our BuildTools and our first alpha stable release! Check our post to see our downloads section in the main post to see how to build/create a JAR to make a server from!