This is merely a problem with config not the plugin. You can disable the moves that are unfixable and then fix the ones that have potential just with the config.JedCore is very unbalanced
This is not true. If it breaks for one it should break for all. If it's only breaking for some, that means they're doing something wrong.JedCore breaks ProjectKorra in most cases.
JedCore is excellently coded. Not only that, but it's being updated all the time which we can't say for ProjectKorra.nor well coded
Can't recall 100% but I'm pretty sure that some people currently involved in ProjectKorra have made some of the moves in JedCore. I don't disagree that they'd do a better job but I think they'd be less efficient at it. They're struggling to work with what they currently have, no point in adding to the stress.ProjectKorra would probably do a better job making jedk1's moves
We're not struggling. Every developer is too busy with life at the moment to dedicate time to pk, so there's just been a long period of time where nothing is being done. It will pick back up eventually, just gotta be patient.They're struggling to work with what they currently have, no point in adding to the stress.
This is what I mean by struggling. You’re struggling to find time or have time at all to work on the project. When there’s no time to work on what you already have, why add to it? That’s my point.Every developer is too busy with life at the moment to dedicate time to pk
Exaclty.This is merely a problem with config not the plugin. You can disable the moves that are unfixable and then fix the ones that have potential just with the config.
Can you stop this argument? You're thinking too higly PK devs. They're not some almighty beings that code on a godlike level. Their level of programming is like most other people. It's of a standard that's expected of most people who call themselves a developer.We should implement more balanced JedCore moves into ProjectKorra (Core)
nor well coded. ProjectKorra would probably do a better job making jedk1's moves because they are more up to date on how ProjectKorra works.
This is honestly the server owner's fault. Are you failing at matching versions and dropping a JAR in a folder? Your fault really. What are you doing trying to set up a server if you fail at this.- JedCore breaks ProjectKorra in most cases.
Why would it be the hassle?If his moves were to be implemented, the code would be altered little to not. It wouldn't be worth the hassle.
From what I've been reading your only problem is that JedCore is it's own plugin, but you'd be fine if it was merged with ProjectKorra.
Which, to me, makes it sound like this guy has a problem with Jedk1 as a person, not the plugin.Because Finns point is saying that if they're going to add JedCore moves into Core then they'd be exactly the same. So if this dude is going to be consistent with his point, he'd then be upset with ProjectKorra rather than Jed.
So that's where this comes into play:
That is fine, your opinion is completely valid. Different people have different tastes.Am I the only one who likes PK without jedcore?
We should implement more balanced JedCore moves into ProjectKorra (Core)
Thus why he's suggestions fall flat here.JedCore is very unbalanced, and I think ProjectKorra would do a good job balancing it. I think jedk1