Search results

Extension is currently broken due to the new forum updates. It messes up the new forum theme AND notification don't even work currently so... Please disable it in the meantime.

Of course. However, you shouldn't expect an immediate update. The changes to 1.13 are very large and will effect ProjectKorra immensely, so it will most likely take a lot of work (and time) updating to 1.13.

Your report is not detailed enough. I haven't come across this issue, so unless you tell me exactly how it happens and give me some more info (e..g a bending debug file), I cannot help you. I can add it to the "to-lookout-for" list, but don't expect a quick fix without giving me more info lol

Here are some things that could stop bending in another world: The world is set as a disabled world for bending in the config file for ProjectKorra The player doesn't have permission to use bending in that world (per world permissions) The player doesn't have permission to build in that world...

There are 3 main permissions related to choosing elements. bending.command.choose - Allows a user to choose an element on their own. Default permission. bending.command.rechoose - Allows a user to rechoose their element when they have already chosen one. Defaults to op only...

Although we've found the cause, this is still a complex issue so we are still working on getting this resolved. You probably will not have a solution anytime soon, so we just ask for your patience. Additionally, could you provide a bending debug file for us? That may help narrow things down.

Sorry, that didn't answer my question specifically enough. I need confirmation that throwing items into lava causes the error; nothing else. This means that if you do the ability normally (with no items falling into lava), the error does not occur. But when items do fall in the lava, that is...

This is truly an odd error indeed. After some pondering, can I get you to do a bit of testing for me to verify the source of the error? It shouldn't be caused by just bending, to say the least. Anyway. Could you try throw an item into lava created by LavaFlow? That's the only way I can see this...

Hi @RoboToe, guess you're trying to fulfil your promise of "crushing my server" :/ Our players know that our community is welcoming and warm. You got backlash from them because you were arrogant, annoying, patronising and you caused issues for our staff team, mainly me, on a daily basis. You got...

I love how as soon as he gets punished for breaking the rules, he posts here saying what a bad server it is. What happened to all the love? </3

Yes, all moves have permissions. If a player doesn't have access to bending.ability.MOVENAMEHERE then they won't be able to use that ability. But of course, it depends on the order the permissions are checked in. Players are granted bending.player by default, which grants them bending.water...

It's not possible without programming a custom plugin right now, but if you just want the prefix, use {element} or {elementcolor}

You may like WaterBubble when you didn't have to hold shift but... I'm gonna say it's technically not canon. Also, there is a click version of WaterBubble as well. Why not just increase the time of that?

Restart the server. That's really the only way to get things functioning again. If it still doesn't work after that, then something else is messing things up, because /reload only breaks things while they are running and doesn't effect things after a restart. If this issue is as big as it is...

There are plans to make this possible, but the implementation of such thing is still a long way off. A lot of people would like a way for ProjectKorra to become RPG like (so you can train/level up skills, etc), and so do I. But, it's probably a while off before being possible, sadly. Also...

Yes, within the eclipse project directory. Should be very easy to find lol

Those warnings are normal, but you are looking for the big -------------------- BUILD SUCCESS ----------------------- or something. If it doesn't say that, does it say build fail? If so, there will be an error above that and that's what we need If it does succeed, then the jar can be found in...

Since you really can't see it, paste the entire Maven install log