[Development] Java Conquer Server

1. Login and account creation
2. Character information and other start up packets
3. Spawn me to other players, retrieve surrounding entities when walking or jumping around
4. Monster spawning
5. Magic skill proficiency and animation

• Better balance between the various professions
• Higher loot chances; higher item qualities and socketed items
• Higher gem mining chance
• More quests / kill quests
• More interaction with NPC's (for example quest teaming or a more interactive tutorial)

<server gameport="5816" authport="9958">
   <model class="net.co.java.model.Mock"/>
</server>

<server gameport="5816" authport="9958">
   <model class="net.co.java.model.PostgreSQL" host="jdbc:postgresql://host:port/database" username="username" password="password"/>
</server>

Quote:

Originally Posted by Spirited The socket system is very weak. If you are open to suggestions, I would recommend the use of asynchronous sockets using Java's NIO channel classes. Example: Code: public class AsynchronousSocket { // Composition of networking classes for the asynchronous socket class: AsynchronousServerSocketChannel socket; CompletionHandler<AsynchronousSocketChannel, Void> acceptHandler; public AsynchronousSocket() { try { socket = AsynchronousServerSocketChannel.open(); } catch (Exception e) { System.out.println(e); return; } acceptHandler = new CompletionHandler<AsynchronousSocketChannel, Void>() { @Override // Invoked when the client is accepted from the backlog. public void completed(AsynchronousSocketChannel result, Void attachment) { try { System.out.println("Accepting connection from " + result.getRemoteAddress().toString()); } catch (Exception e) { System.out.println(e); } finally { socket.accept(null, this); } } @Override // Invoked when the client is rejected from the backlog. public void failed(Throwable exc, Void attachment) { System.out.println("Asynchronous Connection Event Failed"); } }; } public boolean Bind(int port, int backlog) { try { socket = socket.bind(new InetSocketAddress(port), backlog); return true; } catch (IOException e) { System.out.println(e); } return false; } public void Listen() { socket.accept(null, acceptHandler); System.out.println("Ready for incoming connections."); } }

Quote:

Originally Posted by Korvacs Nice to see something different around here though personally not a fan of Java, or its associated IDEs. Thanks for the wiki mention also, did you find most of the packet structures to be accurate?

• Different offsets for the Message packet, there seems to go something wrong in the 5017 table. To-length starts at 26 + fromLength, toStr at 27 + fromLength, immediately followed by msgLength at 28 + fromLength + toLength and message at 29 +... .
  
• Interact packet required a bit of shifting with the identity, we've rewritten one of the solutions from a C# source. Offset 24 seems to be SkillID instead of damage, but we've might not have implemented most uses for this packet yet.

Quote:

Originally Posted by Spirited The socket system is very weak. If you are open to suggestions, I would recommend the use of asynchronous sockets using Java's NIO channel classes.

Quote:

Originally Posted by L1nk1n*P4rK Oh Java! Nice, glad to see that someone here is not bound to C# and/or tries (and fails) to make a solid C++ source. I should not be the one to talk, but still, good job guys! Keep it up.

Quote:

Originally Posted by CptSky Mhm. My C++ source is not a big fail ;)

Quote:

Originally Posted by Spirited No, he has a very valuable point. The point might be from the advice we gave him in his thread asking about programming languages and why we don't use Java, but it's still a good point. Java's socket layer is much slower than C#. There are uses for Java, and making a massive multiplayer server isn't one of them. Is it a useless project though? Well, the original programmer didn't know about NIO before posting here, and now he has something to research into and learn from. He learned Java in class and now he's going above and beyond what was taught by studying on his own, and I have no problem with that. Will the server be stable? Probably. Will the server be efficient? Probably not. Does that make the project useless? Not in my opinion.