Fixes for Velocity-CTD#243
Closed
UserNugget wants to merge 1 commit into
Closed
Conversation
UserNugget
force-pushed
the
velocity-ctd-hacks
branch
from
685e11e to
5133396
Compare
Member
Author
|
Closed in favor of https://github.com/GemstoneGG/LimboAPI |
|
Our fork is now fully set up, the latest LimboAPI fork that works with Velocity-CTD can be downloaded here: https://github.com/GemstoneGG/LimboAPI/releases/latest. We'll try our best to keep it up-to-date with upstream. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes for Velocity-CTD (because someone use it)
Will never be merged, see this for more information: #240 (comment)