Refrain from using adventure in the PluginManager's
Otherwise we have the same issue in the ServerUtilsUpdater plugin with the different adventure shadings
This commit is contained in:
parent
0f9c6f4041
commit
11a5c5140b
10 changed files with 55 additions and 61 deletions
|
|
@ -44,7 +44,6 @@ import net.frankheijden.serverutils.velocity.reflection.RVelocityEventManager;
|
|||
import net.frankheijden.serverutils.velocity.reflection.RVelocityPluginContainer;
|
||||
import net.frankheijden.serverutils.velocity.reflection.RVelocityPluginManager;
|
||||
import net.frankheijden.serverutils.velocity.reflection.RVelocityScheduler;
|
||||
import net.kyori.adventure.text.minimessage.Template;
|
||||
import org.slf4j.Logger;
|
||||
|
||||
public class VelocityPluginManager extends AbstractPluginManager<PluginContainer, VelocityPluginDescription> {
|
||||
|
|
@ -93,7 +92,7 @@ public class VelocityPluginManager extends AbstractPluginManager<PluginContainer
|
|||
dependency.getId()
|
||||
);
|
||||
return loadResults.addResult(description.getId(), Result.UNKNOWN_DEPENDENCY,
|
||||
Template.of("dependency", dependency.getId())
|
||||
"dependency", dependency.getId()
|
||||
);
|
||||
}
|
||||
}
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue