Complete
Last edited:
Thanks cole I really appreciate itVouch for this kid, becoming a really good developer and this core is good.
Okay. Try to follow OOP principles, namely, encapsulation.If i wanted someone to be annoying i'd get disclearing to reply.[DOUBLEPOST=1571257033][/DOUBLEPOST]Added proof of ownership to the thread.
no lol its the only name I could think of at the timeThis come from the ocean?
Just joking althoughno lol its the only name I could think of at the time
Sure I can provide other code snippets if people request them though the version of IHCF i based from did not have a cooldown manager in which i made one. i can provide a screenshot of something like the kill the king manager or somethingYou should show a class that is a little more relevant in my opinion, you only showed a cooldown class when iHCF already comes with its own cooldown system.
Do not take this as me trashing your thread, but I think that people will be able to see the quality of your code better if you show a longer class or something more impressive code-wise other than a cooldown class.
I would suggest to provide a different class in your original thread, it would show the quality of your added-on work quite well if you show something more complex. GLWS!Sure I can provide other code snippets if people request them though the version of IHCF i based from did not have a cooldown manager in which i made one. i can provide a screenshot of something like the kill the king manager or something
ofc I'll probably add more proof of ownershipI would suggest to provide a different class in your original thread, it would show the quality of your added-on work quite well if you show something more complex. GLWS!
Some people just don't like them in which they are entitled to their opinions though you are correct not every iHCF fork is dog shit.ihcf forks aren't that shit LMAO
thanksGreat guy to talk & work with. Vouch.

