Hero
Verified Member
Oh that sucks. I never got to play it either.He said it himself he isn't going to update them.
Oh that sucks. I never got to play it either.He said it himself he isn't going to update them.
Can you please stop crying about every fucking comment?Because I didnt say anything that is remotely rude unlike the other 5 comments before me (You also said y u do dis), so I really didnt mean to offend anyone this time but its clear you meant to offend me. Panda Thumbs Down
._.Can you please stop crying about every fucking comment?
I like this. Gets rid of lagLots of people seem to be unhappy about the changes coming next beta, but keep in mind; it's all optimisation. One of the biggest complaints we've gotten is the amount of lag PK is capable of producing; next beta will be a godsend for a lot of server owners. (And a lot of players! Less "lag" spamming.)
We don't do this to piss you all off. If we could flick a switch to fix it all without having to need developers to update their add-ons, we would've done so.
We all know you can't, but you can't expect people to not complain, especially when it means a recode of almost all addons.Lots of people seem to be unhappy about the changes coming next beta, but keep in mind; it's all optimisation. One of the biggest complaints we've gotten is the amount of lag PK is capable of producing; next beta will be a godsend for a lot of server owners. (And a lot of players! Less "lag" spamming.)
We don't do this to piss you all off. If we could flick a switch to fix it all without having to need developers to update their add-ons, we would've done so.
Im just updating jedcore ... for now.40 individual addons is a lot to plough through, and he has to update jedcore
Yes im serious, addon development keeps geting buttfucked, *cough*1.7.0*cough* then with the config changes (That was easy though so.), and now this. :-/"Are you guys being serious"
Good day
Well if you use eclipse all you need to do is type "extends AddonAbility" and basically eclipse handles the rest and all you need to do is just move your code. Theres not much extra to learnYes im serious, addon development keeps geting buttfucked, *cough*1.7.0*cough* then with the config changes (That was easy though so.), and now this. :-/
So sorry if i'm a little upset that things keep changing, gets really annoying to try and learn something and then it gets changed mid learning process, so yes im serious.
"Good day"
,-,Well if you use eclipse all you need to do is type "extends AddonAbility" and basically eclipse handles the rest and all you need to do is just move your code. Theres not much extra to learn
Look. Quit complaining. This is a much needed recode, that @jacklin213 has presumably spent days on. Pk staff work for free. Show some gratitude to all this work they are doing. Anyway. Would you rather have these changes with gaps in between. or all in one with no dev builds? Thats what i thought. Now stop whining and show some love.,-,
(Deep breath) My point is that things keep changing addon development like every 5 builds, it's annoying af.
I'll complain all I want and I love the beta builds just annoyed. And I love the work that they do, and I know pk staff work for free, and even though i'm "whining" I'm just voiceing my opinion, you don't have to like it.Look. Quit complaining. This is a much needed recode, that @jacklin213 has presumably spent days on. Pk staff work for free. Show some gratitude to all this work they are doing. Anyway. Would you rather have these changes with gaps in between. or all in one with no dev builds? Thats what i thought. Now stop whining and show some love.
I see where your coming from which is why I spent 2 weeks redoing the whole framework so that Addons won't break again hopefully in the near future. The only reasons why Addons have been broken in the past was because we tried building a house on sand without concrete. Obviously you would have to repair the house from time to time which is why I tore down the house laid some concrete so hopefully they house won't need fixes anymore but instead we can focus on improvements.,-,
(Deep breath) My point is that things keep changing addon development like every 5 builds, it's annoying af.
He's a contractor to. I call itI see where your coming from which is why I spent 2 weeks redoing the whole framework so that Addons won't break again hopefully in the near future. The only reasons why Addons have been broken in the past was because we tried building a house on sand without concrete. Obviously you would have to repair the house from time to time which is why I tore down the house laid some concrete so hopefully they house won't need fixes anymore but instead we can focus on improvements.
But nevertheless I totally understand where your coming from and you do have the right to complain
Ever since Beta 13 came out I had to take a look at the CoreAbilities on GitHub to see what have been changed with how abilities should work, and you used remove() in each one of them, then you even used it in the example, I am confused xD.. The method
is optional, should only be implemented if extra things need to be handled by the ability eg) block reverting.Code:remove()
Basically when you have your ability class itself implement AddonAbility, AddonAbility is a subclass of CoreAbility. So when i said remove() was optional what i meant what overriding the current remove() method was optional. If you dont override remove() you will still be able to call it and it will just call CoreAbility.remove() basicallyIt may be a silly question but you mentioned this
Ever since Beta 13 came out I had to take a look at the CoreAbilities on GitHub to see what have been changed with how abilities should work, and you used remove() in each one of them, then you even used it in the example, I am confused xD.
Oh I see, thanks for brighting things up!Basically when you have your ability class itself implement AddonAbility, AddonAbility is a subclass of CoreAbility. So when i said remove() was optional what i meant what overriding the current remove() method was optional. If you dont override remove() you will still be able to call it and it will just call CoreAbility.remove() basically
should be putInstance()putInstances(player, this); // Must be called or ability will not work