Official Ovenuç® Flame topic (L2J Professionals)

[Ovenuç®]

oh god not again

 

 

THAT IS YOUR ANSWER?

 

SO WHY YOU NEED DOUBLE NULL CHECK INSIDE TO DOATTACK IF YOU CANT BYPASS THE CLIENTPACKET! EXPLAIN IT!!

[Intrepid]

Ovenuc, we explained to you alredy many times. Your retardness makes my head spin, but beeing good guy Intrepid i'll explain it again. AttackRequest packet does have nothing to do with that method because attackrequest is not exclusively used in the doAttack method. Also the doAttack method needs the null check so that in case of somehow you manage to cast something without any target, the NPE gets caught instead of just causing a mess with no log about it.

 

Now i understand that you want to act like a big guy, but just like the rest you stuck on the level of "peasant" and instead of improving and trying to understand the code you rage about you just rage about it calling others noobs. Thing is you should stop doing that, stand on your own 2 feet, start coding and the shut the hell up. When you gained some decent knowledge we will talk about such things, since so far its pointless to talk with you about java because you are totally clueless.

[Guest Elfocrash]

To start with, in java you should have null checks as much as possible in your methods either way but i cant explain how it is more. I mean

xdem explains exactly how it works.

[xdem]

 

THAT IS YOUR ANSWER?

 

SO WHY YOU NEED DOUBLE NULL CHECK INSIDE TO DOATTACK IF YOU CANT BYPASS THE CLIENTPACKET! EXPLAIN IT!!

 

forget the packet moron, put ur head that the packet is called ONCE and the facking method doAttack is looped

 

gtfo

 

listen, I dont care if your iq is less than 50 but look how it goes

 

the packets triggers ONCE the doAttack takes place until u stop it or until u cant attack anymore, which means IT WORKS LIKE A LOOP

 

so you have double method for null check pro developer!!

 

 

 

You still can't get it do you ?

 

RequestAttack comes when the player decides to attack a target, the packet is send ONCE it triggers ONCE but the doAttack method which is called by RequestAttack schedules more doAttack(s) according to the player's attack speed.

 

already done 3 times  :you serious?:

[Ovenuç®]

Ovenuc, we explained to you alredy many times. Your retardness makes my head spin, but beeing good guy Intrepid i'll explain it again. AttackRequest packet does have nothing to do with that method because attackrequest is not exclusively used in the doAttack method. Also the doAttack method needs the null check so that in case of somehow you manage to cast something without any target, the NPE gets caught instead of just causing a mess with no log about it.

 

Now i understand that you want to act like a big guy, but just like the rest you stuck on the level of "peasant" and instead of improving and trying to understand the code you rage about you just rage about it calling others noobs. Thing is you should stop doing that, stand on your own 2 feet, start coding and the shut the hell up. When you gained some decent knowledge we will talk about such things, since so far its pointless to talk with you about java because you are totally clueless.

 

EXPLAIN ME INTREPID WHY YOU NEED DOUBLE NULL CHECK IF YOU CANT BYPASS WITH PHX THE CLIENTPACKETS

 

ALL IN MXC KNOWS L2PHX WORKING WITH CLIENTPACKETS SO YOU ARE WRONG! NOT ME

[Ovenuç®]

To start with, in java you should have null checks as much as possible in your methods either way but i cant explain how it is more. I mean

xdem explains exactly how it works.

 

[GR]

 

ESI ME DOULEUEIS TIN ALLI FORA SOU EXIGOUSA OTI TO DOATTACK DEN EXEI KAMIA SXESI ME TO DOCAST KAI MOU ELEGES PIGENE NA AFERESIS TO NULL CHECK KAI KANE TO SKILL TOU SORCER XORIS TARGET NA DEIS.. -beep-E ME ELFO..

 

min mou peis oti ta bgazo apo to mialo mou...

[xdem]

Forget about doAttack ovenuc, next question plis, prove us ur knowledge !! clean ur rep !!!!!  :troll:

[Ovenuç®]

Forget about doAttack ovenuc, next question plis, prove us ur knowledge !! clean ur rep !!!!!  :troll:

 

i didnt get answer l2phx working with clientpackets? YES OR NO?

[xdem]

i didnt get answer l2phx working with clientpackets? YES OR NO?

 

yeap, phx sends the same packet as the client sends

for example

 

client sends FF AB FF 6A 00 00 00

phx sends FF AB FF 6A 00 00 00

 

server gets FF AB FF 6A 00 00 00

[Ovenuç®]

yeap, phx sends the same packet as the client sends

for example

 

client sends FF AB FF 6A 00 00 00

phx sends FF AB FF 6A 00 00 00

 

server gets FF AB FF 6A 00 00 00

 

 

SO HOW YOU WILL GO TO INSIDE CODE doAttack IF YOU HAVE CHECK METHOD ON ATTAACKREQUEST CLIENT PACKET SO INSIDE doAttack the code is bad you never use it!!!

 

 

[GR]

 

ELLINIKA POS 8A PERASIS TO CLIENTPACKET ME TO PHX AN EXEIS IDI EKEI ENA NULL CHECK!!! EFOSON TO PHX DOULEUEI MONO ME CLIENTPACKETS!

 

EXIGISE TO MOU AUTO KAI 8A PW NAI RE EXEIS DIKIO K EXO ADIKO!

[Intrepid]

EXPLAIN ME INTREPID WHY YOU NEED DOUBLE NULL CHECK IF YOU CANT BYPASS WITH PHX THE CLIENTPACKETS

 

ALL IN MXC KNOWS L2PHX WORKING WITH CLIENTPACKETS SO YOU ARE WRONG! NOT ME

 

Okay mister i do it again(btw i just requested maxtor to make a dumbest user award just for you), The null checks are safety checks as a part of the code style you use and they are needed for the reason of beeing NPE safe, sometimes yes you'll have unnecessary null checks but in EVERY case when an object can be null you should have a null check, thats just common sense in java.

 

As for the AttackRequest and doAttack, i say it again the AttackRequest null check is a null check for l2pcinstance class means that if the gameclient which is l2pcinstance is null than the AttackRequest fails and the packet not beeing send, altho when you look at the doAttack method it applies to players,monsters(and all their subclasses), also to summons and pets. Now since a pet for example cant be a pcinstance aka a player you'll need a null check. So its not a double null check but a necessary addition because it does matter if l2pcinstance is null or l2character is null(or l2summon for that matter).

[`NeverMore]

Java fighting :O

Well lets get real , for sure it will work without the second check.

On the other hand i will agree with

To start with, in java you should have null checks as much as possible

But i thnk there's no reason to fighting for such stupid things.

[xdem]

 

SO HOW YOU WILL GO TO INSIDE CODE doAttack IF YOU HAVE CHECK METHOD ON ATTAACKREQUEST CLIENT PACKET SO INSIDE doAttack the code is bad you never use it!!!

 

 

[GR]

 

ELLINIKA POS 8A PERASIS TO CLIENTPACKET ME TO PHX AN EXEIS IDI EKEI ENA NULL CHECK!!! EFOSON TO PHX DOULEUEI MONO ME CLIENTPACKETS!

 

EXIGISE TO MOU AUTO KAI 8A PW NAI RE EXEIS DIKIO K EXO ADIKO!

 

re panivlaka sou ipa 5 fores oti to ena trexei mia fora enw to alo den stamataei pes tpt alo arketa me to doAttack ena gamimeno null check einai re stoke

[Ovenuç®]

re panivlaka sou ipa 5 fores oti to ena trexei mia fora enw to alo den stamataei pes tpt alo arketa me to doAttack ena gamimeno null check einai re stoke

 

 

ahahah re ta pisteueis auta pou les? EILIKRINA? TA PISTEUEIS? PANTA PANTA PANTA MA PANTA TO PHX XTIPAEI CLIENTPACKETS!!! KAI META PAEI STA INNER CODING ELA EXETE LA8OS KAI DEN TO PARADEXESTE!!! APLA EGINES GELIOS APO TIN STIGMI POU MILISES GIA PHX KAI LES GAMA TA CLIENTPACKETS POS NA GAMISO TA CLIENTPACKETS OTAN TO PHX DOULEUEI MONO ME AUTA KAI TO BAD CODING TOUS!!

[Ovenuç®]

Okay mister i do it again(btw i just requested maxtor to make a dumbest user award just for you), The null checks are safety checks as a part of the code style you use and they are needed for the reason of beeing NPE safe, sometimes yes you'll have unnecessary null checks but in EVERY case when an object can be null you should have a null check, thats just common sense in java.

 

As for the AttackRequest and doAttack, i say it again the AttackRequest null check is a null check for l2pcinstance class means that if the gameclient which is l2pcinstance is null than the AttackRequest fails and the packet not beeing send, altho when you look at the doAttack method it applies to players,monsters(and all their subclasses), also to summons and pets. Now since a pet for example cant be a pcinstance aka a player you'll need a null check. So its not a double null check but a necessary addition because it does matter if l2pcinstance is null or l2character is null(or l2summon for that matter).

 

 

intrepid you get your answers if i go to post on l2jserver community that they will be lough all with you you know it that allready.. so say yes i am wrong!

or i will go now on l2j community to post you code

 

 

SO YOU ARE BETTER DEV FROM L2J DEVS BECAUSE L2J DEVS THEY DIDNT USE NULL CHECK IN doAttack