xxdem

can't confirm anything, I only used rev 180, even now (h5) so I don't know the state of other revs

very slow .. Instead of giving just +1 at _pvpKills, you should run the entire increasePvPKills function and bypass the recursion, only then it will be a real PvP assist

what the fck? you post code from my source without credits? First of all this does absolutely nothing if you dont have the SoulshotEffect enum which I am not willing to share

he is probably the only server that welcomes you in

It can be exploited, you MUST first destroy the item and only if that succeeds you can continue with the new item generation. do this: + if (redStones != null && activeChar.destroyItem("MakeAA", redStones, null, true)) + { + count += redStones.getCount(); + aa += redStones.getCount() * 10; + }

this guy is completely mentally handicapped, I thought I was the only one to notice that he indeed reported himself

https://prnt.sc/kotudb the above test with x1000 more tests, compare the two results and you will realize the power of my code

Test it? I never share trash, its obviously working with high accuracy https://prnt.sc/kott70

This is from my private source, you may consider yourself lucky... https://pastebin.com/WhaKF4gV to call it use the IJackpot interface, for example jackpotPick(allItems, L2DropItem::getChance);

don't downgrade your database then, just update the old sql data to make it compatible with ur current database, it can be as simple as multi-replace on notepad++

"foreign key can be null" No shit Sherlock, but on his case null makes no use. I'm so done with you, just do your thing (you won't), I am out

gtfo trash can @.Elfocrash which exactly my above comment is, with added sugar because the target is the legendary god coder access

Right now you are talking outside of your own self, realistically you can't even imagine yourself trying to make these trols learn something (some guys are exceptions, but the whole image of the forum consumes them) my 2 cents, good luck making the forum better

by the way, after bashing AccessDenied, I've created a proper share with unique content and very good code that I use personally on my server, I didn't bash the shit out of him and then left with nothing I even left the caching of the EnchantScrolls which I am sure none noticed, its my idea to cache the stats of the scroll on the Map by their ID rather than storing on a private variable, that makes the scroll change it's rates/fails without requiring a restart for the player after the admin updated and hit the //reload

Are you sure they won't? Then go greedy and don't pretend the polite beginner guy, but the godlike arrogant developer that makes a shitload of money with his legendary developing skills that "happened" to know shit about SQL or some basic principles and is asking a completely irrelevant question, guess what would happen (because this is the case on mxc, not the "polite begginer trying to learn"

this is how it works, there is no community that will take trashcode lightly (if it has serious devs inside), try to post a shitcode on stackoverflow politely as a beginner, even famous guys will bash the shit out of you if you manage to get their attention. Why would this change is mxc?

spammer? I said your database is a mess and that your codes are dangerous and you didn't even cared to correct yourself. @.Elfocrash so it will be better sharing trashcode that unaware victims add to their servers and get destroyed? this is why the community is broken in the first place, not because a guy pointed out why the code is shit with one way or another

This share is gold for those who know how to use it, it basically unhard-codes all enchant scrolls and gives you the ability to create any scroll with a simple //reload items. Tested on L2AEPvP (Beta), more details: sample XML (very basic) <item id="45000" type="EnchantScroll" name="Scroll: Enchant Weapon"> <set name="default_action" val="skill_reduce" /> <set name="etcitem_type" val="scrl_enchant_wp" /> <set name="is_oly_restricted" val="true" /> <set name="is_stackable" val="true" /> <set name="handler" val="EnchantScrolls" /> <set name="scroll_binds" val="WEAPON" /> <rates rate="0"> <tiertarget tier="ANY" rate="0" disprate="80"> <enchtarget enchants="0-3" rate="100" /> <!-- SAFE --> <enchtarget enchants="4-8" rate="80" /> <enchtarget enchants="9-11" rate="75" /> <enchtarget enchants="12-15" rate="70" /> <enchtarget enchants="15" rate="45" disprate="60"/> <enchtarget enchants="16,17" rate="60" /> <enchtarget enchants="18" rate="40" /> <enchtarget enchants="19" rate="20" /> </tiertarget> <tiertarget tier="COMMON" rate="90" maxench="25" > <enchtarget enchants="0,1,2,3,4" rate="100" maxench="25" /> <!-- SAFE --> </tiertarget> </rates> <fails penalty="CRYSTALLIZE" > <tiertarget tier="UNCOMMON" penalty="NONE" basevalue="0" >  <enchtarget enchants="7,8,9,10,11,12" penalty="NONE" value="4"/> <enchtarget enchants="13,14,15" penalty="DEC" value="1"/> </tiertarget> </fails> </item> Features: The possibilities are hundreds, you can create enchant scrolls that can enchant a very specific tier, enchant scrolls that have their own max enchant and so on You can calculate the enchant rates and inform the player before the enchant Item Grades are obviously ignored Things you have to do to get this working: 1) Create TIERS (enum) and assign it to items 2) Create EnchantFailed (enum) and implement the penalty code 3) Create ScrollBinds (enum) and assign it to each paperdoll Additional things you will need public static <V extends Enum<V>> EnumSet<V> toEnumSet(String enumStr, Class<V> enumClass) { if (enumStr == null) return EnumSet.noneOf(enumClass); final String[] enumStrings = enumStr.replace(" ", "").split(","); final EnumSet<V> enums = EnumSet.noneOf(enumClass); for (String e : enumStrings) enums.add(Enum.valueOf(enumClass, e)); return enums; } public static int[] toIntArrayEx(String[] strArray) { final ArrayList<Integer> intList = new ArrayList<>(strArray.length); for (int i=0;i<strArray.length;i++) { try { final String strNum = strArray[i]; if (strNum.contains("-")) { final String[] explode = strNum.split("-"); final int min = Integer.parseInt(explode[0]); final int max = Integer.parseInt(explode[1]); if (min < max) for (int j = min; j <= max; j++) intList.add(j); } else intList.add(Integer.parseInt(strNum)); } catch (Exception e) { e.printStackTrace(); } } return intList.stream().mapToInt(i->i).toArray(); } Good luck

got to admit that I didn't notice the LinkedList here I've just seen Queue and skipped the whole post. Why would you hardcode something like this

we posted it simultaneously

didn't even read your trashposts mate, I just got a quick glance over what was debated

aka linkedlist

shitcode fest, GG mates. onDie(...) { final int nextspawnId = template.getNextSpawnId(); if (nextSpawnId) spawn(nextspawnId

At least your English isn't corrupted like the others from your team, you must be the marketing guy

I know, I just want to know his own pov