TitleManager not working correctly on paper 1.16

[AirCraze]

Describe the bug A clear and concise description of what the bug is. 1.16 paper To Reproduce Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior A clear and concise description of what you expected to happen. Placeholders aren't shown completly. Screenshots If applicable, add screenshots to help explain your problem.

Stacktrace / Error Please check the console for any errors that TitleManager might be producing.

14:56:04 WARN: at java.util.HashMap$HashIterator.nextNode(Unknown Source) 14:56:04 WARN: at java.util.HashMap$EntryIterator.next(Unknown Source) 14:56:04 WARN: at java.util.HashMap$EntryIterator.next(Unknown Source) 14:56:04 WARN: at java.util.AbstractCollection.toArray(Unknown Source) 14:56:04 WARN: at com.google.common.collect.Iterables.toArray(Iterables.java:295) 14:56:04 WARN: at com.google.common.collect.ImmutableMap.copyOf(ImmutableMap.java:406) 14:56:04 WARN: at com.google.common.collect.ImmutableMap.copyOf(ImmutableMap.java:391) 14:56:04 WARN: at me.clip.placeholderapi.expansion.manager.LocalExpansionManager.getExpansion(LocalExpansionManager.java:120) 14:56:04 WARN: at me.clip.placeholderapi.replacer.CharsReplacer.apply(CharsReplacer.java:144) 14:56:04 WARN: at me.clip.placeholderapi.PlaceholderAPI.setPlaceholders(PlaceholderAPI.java:69) 14:56:04 WARN: at me.clip.placeholderapi.PlaceholderAPI.setPlaceholders(PlaceholderAPI.java:97) 14:56:04 WARN: at io.puharesource.mc.titlemanager.internal.placeholder.PlaceholderAPIHook.replacePlaceholders(Hooks.kt:18) 14:56:04 WARN: at io.puharesource.mc.titlemanager.internal.services.placeholder.PlaceholderServiceText.replaceTextFromHooks(PlaceholderServiceText.kt:171) 14:56:04 WARN: at io.puharesource.mc.titlemanager.internal.services.placeholder.PlaceholderServiceText.replaceText(PlaceholderServiceText.kt:158) 14:56:04 WARN: at io.puharesource.mc.titlemanager.internal.services.features.ScoreboardServiceSpigot.setScoreboardValue(ScoreboardServiceSpigot.kt:137) 14:56:04 WARN: at io.puharesource.mc.titlemanager.internal.services.features.ScoreboardServiceSpigot$createScoreboardValueSendableAnimation$4.invoke(ScoreboardServiceSpigot.kt:222) 14:56:04 WARN: at io.puharesource.mc.titlemanager.internal.services.features.ScoreboardServiceSpigot$createScoreboardValueSendableAnimation$4.invoke(ScoreboardServiceSpigot.kt:33) 14:56:04 WARN: at io.puharesource.mc.titlemanager.internal.model.animation.PartBasedSendableAnimation.update(PartBasedSendableAnimation.kt:90) 14:56:04 WARN: at io.puharesource.mc.titlemanager.internal.model.animation.PartBasedSendableAnimation$update$2.invoke(PartBasedSendableAnimation.kt:97) 14:56:04 WARN: at io.puharesource.mc.titlemanager.internal.model.animation.PartBasedSendableAnimation$update$2.invoke(PartBasedSendableAnimation.kt:10) 14:56:04 WARN: at io.puharesource.mc.titlemanager.internal.services.task.SchedulerServiceAsync$scheduleRaw$1.run(SchedulerServiceAsync.kt:44) 14:56:04 WARN: at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) 14:56:04 WARN: at java.util.concurrent.FutureTask.run(Unknown Source) 14:56:04 WARN: at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(Unknown Source) 14:56:04 WARN: at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source) 14:56:04 WARN: at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) 14:56:04 WARN: at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) 14:56:04 WARN: at java.lang.Thread.run(Unknown Source) Server information:

• TitleManager version: [Example:. 2.1.5]
• Spigot version: [Example: Spigot 1.14.4 or PaperSpigot 1.12] Latest titlemanager 2.3.3 with paper 1.16 Additional context Add any other context about the problem here.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale[bot]]

The issue is being closed as it's stale. If you still need support with this issue, please re-open the issue.