Command Issue about combattagplus HOT 12 CLOSED

Just noticed, in "FBasics" there is the code:
WILDERNESS(CmdWilderness.class, new String[]{"wilderness", "wild", "w"});

if it helps.

from combattagplus.

What is CommandTagPlus?

I bet it's an issue with the config file encoding.
Windows prefers UTF-16, but linux uses (the far supperior) UTF-8.
If you're editing with notepad, make sure to save the file as 'UTF-8', not 'Unicode' (which is actually UTF-16).

from combattagplus.

@Techcable I meant FBasics, just got confused. Yeah I have just tried editing the fbasics plugin code myself now and I will get back to you. Instead I am going to make /wild a command that is using commands.yml as part of bukkit.

Windows somehow blocks /wild and linux doesn't - using same .jars and same configurations, very odd

from combattagplus.

Again, have you checked that the config file is saved as UTF-8 on windows? Regardless, we should probably support UTF-16 natively, since it's so common.

from combattagplus.

Yeah both saved in UTF-8, still doesn't fix the /wild command issue. :(

from combattagplus.

Actually, it looks like the problem is the opposite of what I expected. Since we don't specify a charset explicitly, Java assumes UTF-16 on windows and UTF-8 on linux. I'll fix it by using UTF-8 as default, and UTF-16 as a fallback.

from combattagplus.

Thanks that will fix blocking /wild? I have been so confused haha. @Techcable

from combattagplus.

It looks like it's actually a bug in bukkit I can't fix from inside the plugin.
JavaPlugin.reloadConfig() doesn't support UTF-8 on windows, and I can't override it.
However, you can't use UTF-16, since the plugin saves the file as UTF-8.
Unless bukkit fixes it, you'll have to just avoid windows if you want proper unicode support.

EDIT 1: Nevermind, bukkit actually does support unicode properly. I was looking at an old version. However, it's still probably some mysterious encoding issue that's not really our fault. One more idea would be to change the default encoding to UTF-8 by adding -Dfile.encoding=UTF-8 at the command line.

from combattagplus.

@Techcable I use linux, but what I'm saying is - windows is blocking /wild whereas combattagplus on linux won't. I really need to try and fix this and I can't change anything for command line. This: https://dev.bukkit.org/projects/combatlog blocks it somehow, but clearly this plugin isn't as great as combattagplus. Please help, much appreciated

from combattagplus.

I'm on Linux. I use FBasics. I block wild and a bunch of other commands that are provided by FBasics in combat. I can't reproduce this issue. Download the latest dev build. Remove all plugins except CombatTagPlus and FBasics. Use a fresh CombatTagPlus configuration. This issue is very clearly specific to your setup.

from combattagplus.

@Techcable I indeed use linux but what I'm saying is my issue doesn't exist on windows with the /wild blocking

from combattagplus.

@CheatSupport I'll admit that's very odd, but we still can't reproduce this issue.
As @Byteflux said, we need you to check if this issue occurs with the latest FBasics and CombatTagPlus, no other plugins, and a clean configuration.
Even if you can reproduce it, there's still not much we can do unless you find a way for us to reproduce it on our computers.

Relevant XKCD

from combattagplus.