Xanderॐ

Since noone is paying taxes for donations :)

You missed the point. There is no seperate webserver here. The L2JServer integrates a web server inside it. Once you run the L2JServer.jar you run the webserver too. And since they are both the same JVM runtime, they dont need to access the database at all. Here's an example. This is direct access on l2jserver. No database. And what it does, is read all online "monsters" and prints them out. Something that database can't do.

I was about to send you a PM regarding this issue wanting your opinion. And then i came here and saw you already replied. Howler and I are thinking to integrate Java Servlet inside the L2JServer. One single JVM instance loading the l2jserver and a website that can have direct access to the L2JServer runtime ( since they are the same runtime ). We were thinking about using Jetty as the webserver. Pros: Direct access to all objects of L2. No need for site to connect to db to drag info to the site visitors. (Imagine what kind of things you can display with js and ajax !! ). Ridiculously fast !! You wont need to access I/O at all to display things at the website. Opinion on that ? DDoS has nothing to do with forum being viewed by unregistered members. Absolutelly nothing.

The following bulletins are things you should not do when making a server. They come from my experience as a player ( that is things that annoy me when i see them in a server ) and as an owner ( things that will make the players blast you ). The order in which they are presented here does not define any kind priority or importance factor. They are layed down as they come forth in mind. 1 ) Do not use private forums that need registration for viewing rights. As a player, before joining a server i always look at the forum activity to get a glimpse of the community. When i see hidden forums that want me to register, it doesnt only make me frustrated but it gives an indication that the owner wants to hide something ( Drama ? Complains ? Low forum activity ? ). 2 ) Do not give many priviledges to your staff. Its proven that at least 1/2 staff members will get corrupted at some point in time costing you money and reputation. Keep an eye on your staff through logs and keep their privs at minimum. 3 ) Do not advertise false promises and do not boast in it. That is, do not use stupid titles that make you look stupid. For example "Perfect balance server" , "The server you've been waiting for" , "Best highrate server ", "Best pack server" , "Great machine with 50000 GB ram" , "234% ANTIHACK Protection" , "Anithack protection: on , anticheat protection: on". You get the point, all those things make you look stupid at the eyes of the experienced clan or player. Make sure to tell the unique story of your server in your ad and not boast about things you do not have or everyone else has. Its not a big deal if you have TvT, everyone has, etc. 4 ) Trust your own powers, not powers for hire. That is, a hired developer/admin/web designer will work for money without passion. He probably wont do good work but thats the minimum. In most cases dissagreement in the payment will leave you damaged and most of the time without the source code making your server frozen in terms of updates. 5 ) Dont use a super cool looking rip of a website but use a functional website. Too much style can make your site unreadable. Be sure to have the most important things, like connection info, features in public and easily accessible view. Noone likes to spend hours just to find out how to register or download your client patch. 6 ) Dont use all the customs just because they are free. Having way too many unrelated and different custom features taken from public shared sources is as bad as having no customs at all. The customization is the identity of your server. Too low and your server is the same as everyone's. Too high and it becomes a circus that noone takes seriously. A server is not evaluated by how many custom features it has, but by how many bad custom features it does NOT have. 7 ) Dont waste resources yourself fixing single players issues. That is, if someone lost his account, it is his problem. Same if he is hacked. Having many players and treating them in person will waste much of your time. The exception is important people that can influence the server. You do treat big clan leaders in person cause they can influence many people. 8 ) Do not forget the stability of the server.People dont like it when they lose things nor when they cant play. Be sure to take frequent backups incase of dissaster. Make sure that you wont need to downgrade effort quality cause people forget the death of their parents faster than the loss of their fortune - Machiavelli 9 ) Dont talk about class balance too much. There is no perfect balance and as much as you try you will always end up arguing with players. The reason is not that you are bad in it. The simplest reason is that in each pvp one man loses , one man wins. The one that loses will always blame the balance. 10 ) Do not be an admin, be a player. Yes you heard right, make an alt character and play your game at least two hours a day. Playing the game gives you a better understanding of its structure than making the code. Even allow your gms/admins to play the game without corrupting themselves ( be sure to check them ). Having a team that consists of player - admin hybrids is better than having a team that is full of technocrats. First time i played my first server i was like "Who's the idiot admin that made such bad class balance ...". Turns out it was myself :)

And you cant. You are a noob.

Nope, still online , he is a noob, cant do shit :)

Besides the recipe of the server which is totally wrong, I have lots of reasons to troll this specific server and the specific pack it uses. It has its roots in a time far far away ... PS: Player count removed i see. Didnt reach the anticipated number eh ?

We are still online , whats up big boy , cant hack shit ?

Here, exfire.eu , i doubt you can hack us at all ...

Smells as if someone got a remote 0day exploit in his hands. Or is just a big liar ... Who knows. PS: If your server got hacked/crashed or something by this guy, pm me, (And have wireshark if your server is windows or tcpdump if it is linux ).

Well, not that i wanna bush the effort or something, it's just that the concept they selected was wrong. Noone will waste time leveling and farming in 2012. And as for the "lowrate" argument, if you check the donations they got boosted 50% exp/sp premium account. That alone says much about the rate they consider their server to be.

100 players online at start at rush hour. Turns out i was right after all ... Facepalm not if you want ...

Save the facepalms for the opening. Cause chances are , you will need to use many. Not that i wish i'm right, but i have a feeling I will be.

Question, is your Panthcodes using A-Star algorithm or the Panther searching method ?

I assume this was such a big change that you had to write a post about it. Tons of lines of codes to change that ... @iddQ We will talk in 1-2 days again after the "results" are out. I hope you will still be in this forum. Also, about that idiot , what was his name i forgot, the one that said you will be 80 in one day. Well guess what captain obvious, if you need 1 day to get to 80, better start 80 at default since leveling has no point. Fail squared.

You are being so lame saying the same catch phrase all the time. Noone is hating, they are just stating that your server wont succeed because the concept is totally wrong. Just check your forum, its empty ... Your flag counter is low ... The site is an amateur work without much attention. To me it looks a bad attempt without much passion in it.

I would like to play a server with acis pack. Have any suggestion ?

Greeks > All ;)

Καλά το κατάλαβα -.-'. Αν θες να μάθεις να κάνεις μαγικά, διάβασε το 3 μόνο. Εκεί είναι όλο το ζουμί.

Δεν είναι για newbies, ξαναδιάβασε :)

Όσοι ασχολείστε με L2J σίγουρα θα έχετε δει την παρακάτω πρόταση: L2PcInstance target = activeChar.getTarget(); Κάποιοι έχουν ίσως δει και μια παραλλαγή της: final L2PcInstance target = activeChar.getTarget(); Η μόνη διαφορά είναι η λέξη final στην αρχή της πρώτης πρότασης. Η λέξη final το μόνο που κάνει άμεσα είναι να μην επιτρέψει την αλλαγή μιας μεταβλητής μετά την πρώτη της ανάθεση. Δηλαδή από τη στιγμή που η μεταβλητή target πήρε τιμή, η τιμή αυτή δεν θα αλλάξει. Για παράδειγμα το παρακάτω θα δώσει error κατά τη διάρκεια του compile : L2PcInstance target = activeChar.getTarget(); L2PcInstance target = null; <--- Error: the final variable cannot be reassigned. Οι λόγοι που χρησιμοποιούμε final : 1)Θέλουμε να δώσουμε τιμές σε μεταβλητές που δεν μπορεί να αλλάξει κανείς άλλος ώστε να μη προκαλέσει προβλήματα στον κώδικα από ελλειπή γνώση. 2)Θέλουμε να αυξήσουμε την απόδοση του κώδικα. Όταν ο compiler δει την λέξη final εκτός μιας συνάρτησης βρίσκει όλα τα μέρη στα οποία υπάρχει η μεταβλητή και την αντικαθιστά με την τιμή της. Για παράδειγμα Κώδικας: final int x = 10; System.out.println(x); Μετά το Compile : final int x = 10;; System.out.println(10); Αυτό που έκανε ο compiler για εμάς είναι να βάλει όπου βρει το x την τιμή 10 μιας που η μεταβλητή δεν γίνεται να αλλάξει. Αυτό που κερδίζουμε είναι ότι όταν φτάσει η εκτέλεση στη γραμμή Sustem.out.println... δεν θα ψάξει να βρει στη μνήμη τη μεταβλητή x καθώς την έχει αντικαταστήσει, κάνοντας έτσι τον κώδικα πιο γρήγορο. 3)Κάνουμε τον κώδικα ακόμα πιο γρήγορο και μικρότερο ταυτόχρονα. Ας δούμε το παρακάτω παράδειγμα: public boolean log = false; if(x){ Do logging bla bla ... } Κάθε φορά που τρέχει ο παραπάνω κώδικας ελέγχεται η τιμή του χ και αν είναι false δεν προχωράει μέσα στις αγκύλες. Ο έλεγχος όμως γίνεται κάθε φορά καθώς το x μπορεί να αλλάξει και ταυτόχρονα ο κώδικας μέσα στις αγκύλες παραμένει. Αν όμως γράψουμε τον κώδικα ως εξής : final boolean x = false; if(x) { Do logging } Η τιμή του x δεν μπορεί να αλλάξει γιατί είναι final. Ο Compiler όταν το δει αυτό θα καταλάβει ότι η εκτέλεση δεν θα φτάσει ποτέ μέσα στις αγκύλες οπότε διαγράφει από το class/jar όλο το τμήμα if ().... με αποτέλεσμα να μη χρειαστεί να κάνει ποτέ τη σύγκριση κάνοντας τον κώδικα πιο γρήγορο. Ταυτόχρονα επειδή διαγράφει το τμήμα του κώδικα το παραγόμενο class/jar είναι μικρότερο. 4)Η λέξη final μέσα σε μια συνάρτηση δεν αυξάνει την απόδοση τόσο όσο αναφέρθηκε προηγουμένως καθώς η τιμή της ορίζετε κάθε φορά που εκτελείται η συνάρτηση. void foo() { final L2PcInstance target = getTarget(); bla bla ... } foo(); <-- Δίνει τιμή στην final foo(); <-- Ξαναδίνει τιμή στην final foo(); <-- Ξαναδίνει τιμή στην final 5)Η λέξη final αναφέρεται στην αναφορά προς ένα αντικείμενο και όχι προς το αντικείμενο αυτό για παράδειγμα : final L2PcInstance target = getTarget(); target.sendMessage("BlaBla"); <-- True, μπορεί να γίνει, δεν το εμποδίζει η final. Τα 1,2,4,5 είναι βασικά πράγματα, το 3 είναι magic ;) Αυτά :)

None, in contrast to Sternwal, i did not say anything about code copying, but merely offended everyone, cause I am indeed a bad troll :) The Mirror

Then, before you open your snake mouth and start spilling out poison towards other projects timeline, go watch the timeline of the project you support first. "Because you have done this, "Cursed are you above all the livestock and all the wild animals! You will crawl on your belly and you will eat dust all the days of your life." - Genesis 3:14 The saint.

Actually, to be in a war technically, there must be two sides fighting. I'm still waiting for L2JFrozen to respond, but it seems they are only good in attacking newbie projects while having their shields down. PS: Lets not forget that people from your project along with l2jfrozen devs started the troll wars. So instead of cleaning first, hold back your boys ;) It's about cleaning the town from the bacteria. You know, infection reasons. The Penilus Gigantus

Thats all you got ? Come on its like , 5 l2jfrozen members "poluting" this topic and you cant pick a programming fight with me ?? Cowards ... Whatever, go place final keywords in every method-local variable for no apparent reason, stupids ...