We moved our repositories to BitBucket!

If you can't login or you can't register to the forums do not rise an issue, instead please write to support (at) l2jserver.com

Check our wiki!

Report server issues here

Forum has been updated to phpBB 3.2, let's see if this fixes some minor bugs we had.

Thank you for visiting http://www.l2jserver.com/

Questions regarding sending packets to L2JServer

Have you created a useful tool? or Do you want to get help building one? This is the right place!
Forum rules
READ NOW: L2j Forums Rules of Conduct
Post Reply
User avatar
Quantum
Posts: 1
Joined: Wed Jun 28, 2017 11:34 am

Questions regarding sending packets to L2JServer

Post by Quantum » Sun Jul 02, 2017 11:31 am

Hello :wave:

I'm trying to create a web interface that allows me to perform certain operations ingame such as directly adding items to a given player's inventory, or something like opening a dialog window for every player ingame by pressing a button in my web interface.

After looking inside the L2J source code I found that the L2GamePacketHandler.java class is responsible for handling packets which bode well for my little side project. However, it seems in order for a packet to get processed, the L2GamePacketHandler needs a L2GameClient which leads me to my questions:

- Is it possible for anything other than a L2GameClient to get it's packets handled by the L2JServer?
- If this is indeed possible, how would I implement this? (maybe post actual/pseudo code if it's not too much trouble)
- If this is not possible, would it then be possible to create a workaround?

My knowledge regarding the structuring of MMO's is limited which is why I've decided to make this thread, so forgive me if my questions sound stupid.

Thanks

User avatar
UnAfraid
L2j Veteran
L2j Veteran
Posts: 4195
Joined: Mon Jul 23, 2007 4:25 pm
Location: Bulgaria
Contact:

Re: Questions regarding sending packets to L2JServer

Post by UnAfraid » Mon Jul 03, 2017 1:03 pm

Hello,

You might wanna check telnet implementation, or your own REST api within the server source if you like something more modern and secure for usage outside localhost (Because i wouldn't recommend exposing telnet to public internet)
Image

Post Reply