SweeTs

Long story short, you should trash that code. It's old and shitty using gargoyle, lol.

@deMEV

No errors, no warnings = nothing to do. Leave it as it is. Period.

Nop, you made it private. It's visible only to you.

I was not referring to the copyrights and whatsoever, I said that in my first words, read again if necessary. I was saying about doing the right thing. He agreed on his terms which were "do not share, do not sell". Yet, he shared it. He broke his word. And you are 'attacking' me, bcs I said that people should act right. Again, what's disguisting here? That doesn't make sense. Stop with the law and such. Too much law books or law serials. If we look at law, even this site should be shut down for not paying taxes, bcs I highly doubt Maxtor do.

Acting right in real life or through internet, keeping a word is wrong? What's wrong with you? Seriously. It's not about the project, it's about his time spent coding customs. Pack itself is free and it comes as package. Think like that. Yeah, I will code custom feature and sell it as a diff or whatever. Then, I sell it to you and you decide to share it just bcs you want so. You simply destroy someones 'business' doing so and that shows how 'disgusting' person you are. Sounds legit and fair as fak. Seriously.. Back to the pack. If the pack would be coded ESPECIALLY for him, sure, do whatever the fack you want. But, if its not, then respect the author and his work. Bonus. - Jump! I will catch you! - Are you sure? - Yeah, jump... ... ... - Oops.

Put a race check under the method you use to retrieve possible subclasses, if is! = than actual, skip it aka continue under a loop.

Licensed or not, it's always up to us to act rightly or not. No one wants his code to be shared, especially when you sell it. So, we try to protect each other by removing such 'leaks'. That sounds right. Topic from spam section junked. I wonder, why he/you shared it there rather than share section o.O As always excuses about old, bad code. So common.. BTW, you don't need to close connection when you use try with resources, it's auto, lol. No, you would not be banned if you share acis files, at least not on mxc. On acis forums ofc. Such 'leaks' happens when you are dick to another person. Once, even Elfo shared acis file when he get mad on me :D While I'm here, chat banned for 5 days for notorious flaming/inappropriate, offensive language/and so on. Watch your language.

Sure thing. Check some one wannabe forums mxc like, you may find it there or l2jbrasil or so.

Finding (shared) diffs may he hard, so..

Checkout free svn, if you want to test, rip code. Diff is way too fat.

Why not, vampir decompiled the sources after all. Once he get the sources, he can add it ^_^

Scale bubble effect (signet skills), perhaps.

Yeah, hero weps have disabled enchant glow, matter of weapongrp edit. Locked then.

While you can't find it, what's stopping you to copy/paste original hero weapons and create them as a new, custom ones with enabled enchant color?

class String, you have to rename it. Guess error is clear and even one Google search would give you the answer.

Bha, as I said.. Bad code, go to that line and fix it.

I bet it's custom. Reward kill or 'anti bot' with wrong cast.

So how you call people like above, hating, flaming, basically shitting around? Use the psychology concept and put an diagnose for all of you. Yoo

Normal people like skynet, a cancer to humanity.

That's common, from a normal discussion it turns into a hate && flame shit. Not worth to read 2 last pages.

At least I was funny, you never did ;(

It wasn't troll, it was a true statement :D

Never saw a perfect code from you there were always flaws. You can say you do stuff for free and so it's not perfect, but that's false for your perfectionist statement :D Anyway, enough with that chit chat. Wait for Tk =D

Nice.. I did NOT said you are working or was on frozen file, just you are working LIKE them. You do mistakes, people cry about the code, you fix fixed fix and after all that, finally it's OK. All bcs you don't test your codes. Code, test, sell. That's the proper order.