Jump to content

Recommended Posts

Posted

IF you ever get this errors in your server console :

lolfbs.png

 

aply this patch:

 

 

Index: /Gs folder/java/config/server.properties
===================================================================
--- /Gs folder/java/config/server.properties (revision 10)
+++ /Gs folder/java/config/server.properties (revision 443)
@@ -72,4 +72,8 @@
CharMaxNumber = 7

+# Packet Handler Debug
+# DO NOT CHANGE IT
+PacketHandlerDebug = False
+
# Define how many players are allowed to play simultaneously on your server.
MaximumOnlineUsers = 500
Index: /Gs folder/java/net/sf/l2j/Config.java
===================================================================
--- /Gs folder/java/net/sf/l2j/Config.java (revision 422)
+++ /Gs folder/java/net/sf/l2j/Config.java (revision 443)
@@ -1528,4 +1528,5 @@
	/** External Hostname */
	public static String EXTERNAL_HOSTNAME;
+	public static boolean PACKET_HANDLER_DEBUG;
	public static int PATH_NODE_RADIUS;
	public static int NEW_NODE_ID;
@@ -1594,4 +1595,5 @@
				EXTERNAL_HOSTNAME = serverSettings.getProperty("ExternalHostname", "*");
				INTERNAL_HOSTNAME = serverSettings.getProperty("InternalHostname", "*");
+				PACKET_HANDLER_DEBUG = Boolean.parseBoolean(serverSettings.getProperty("PacketHandlerDebug", "False"));
				GAME_SERVER_LOGIN_PORT = Integer.parseInt(serverSettings.getProperty("LoginPort", "9014"));
				GAME_SERVER_LOGIN_HOST = serverSettings.getProperty("LoginHost", "127.0.0.1");
[code][code]ex: /Gs folder/java/net/sf/l2j/gameserver/network/clientpackets/ProtocolVersion.java
===================================================================
--- /Gs folder/java/net/sf/l2j/gameserver/network/clientpackets/ProtocolVersion.java (revision 3)
+++ /Gs folder/java/net/sf/l2j/gameserver/network/clientpackets/ProtocolVersion.java (revision 443)
@@ -42,7 +42,9 @@
		// this packet is never encrypted
		if (_version == -2)
-		{
+		{		
			if (Config.DEBUG)
				_log.info("Ping received");
+            if (!Config.PACKET_HANDLER_DEBUG) 
+                return; 
			// this is just a ping attempt from the new C2 client
			getClient().closeNow();
@@ -50,4 +52,6 @@
		else if ((_version < Config.MIN_PROTOCOL_REVISION) || (_version > Config.MAX_PROTOCOL_REVISION))
		{
+            if (!Config.PACKET_HANDLER_DEBUG) 
+                return;         
			_log.info("Client: " + getClient().toString() + " -> Protocol Revision: " + _version + " is invalid. Minimum is " + Config.MIN_PROTOCOL_REVISION + " and Maximum is " + Config.MAX_PROTOCOL_REVISION + " are supported. Closing connection.");
			_log.warning("Wrong Protocol Version " + _version);
@@ -60,4 +64,6 @@
				_log.fine("Client Protocol Revision is ok: " + _version);
			}
+            if (!Config.PACKET_HANDLER_DEBUG) 
+                return; 
			KeyPacket pk = new KeyPacket(getClient().enableCrypt());
			getClient().sendPacket(pk);

[/code][/code]

Guest Рrototype
Posted

adding it just right now !! Thanks for that awesome share :)

Posted

goodjob you just fixed the first bug i've sended LOL!

 

There are sooo many other bugs I can fool a server with...

 

the one is hacking , the other is fixing :P

Posted

You mean that you don't know how to disable a log?

 

Quit l2j dude..

If people are making patches to disable logs it won't fix anything it will just not show it anymore but the error still exists :)

Posted

If people are making patches to disable logs it won't fix anything it will just not show it anymore but the error still exists :)

You are WRONG! You are just sending EMPTY packets, which don't affect the server! The server crashes because you are flooding the console with errors.

 

Also serk come on.. be serious, this isn't yours. It was made by DrHouse and implemented to L2JServer when DragonHunter released his attacker.

Posted

You are WRONG! You are just sending EMPTY packets, which don't affect the server! The server crashes because you are flooding the console with errors.

 

Also serk come on.. be serious, this isn't yours. It was made by DrHouse and implemented to L2JServer when DragonHunter released his attacker.

PacketHandlerDebug config isnt mine but the fix in protocol it is

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


  • Posts

    • And Discord: https://discord.gg/3aYqWNqb
    • Ofc: https://discord.gg/3aYqWNqb
    • You can find some H5 skins shared in old L2 modding Discords, but most of the higher‑quality ones are either paid or come bundled with full client edits. I usually mix in commissioned work and whatever I can patch myself. On a side note, I fund a lot of these commissions by selling off game items through instant sell cs2 skins, which has been a quick way for me to get some cash for projects.
    • There is no need for gRPC in this case, even tho originally it was gRPC based but since we don't need it to be bi-directional, we switched to simple http requests for the web calls and SSEs for the data streamed from the server. There are distributed locks in place to precent race conditions between actions that can happen between multiple web instances and the server.   Local models can also be slow depending on the model, and most external models can actually be faster than local ones if you use Flash 2.5 or something along those lines. I am running on 512GB of Unified Memory on my Mac Studio M3 Ultra so the speed of the local model for a small model is pretty good but I tested it with Gemini too and it works equally as fast and in some cases faster. The way it works is that I'm using pgvector (one of the benefits of moving to Postgres) to search the data and see what the player can see etc and there is some batching of the next few actions for 2-4 seconds for the user until the next LLM request fires. The batching also includes branching on logic so if they for example fall under some HP they will move to kiting instead of attacking or maybe they heal etc.   Everything is authed and permission-based. The server and the backend of the frontend have secure communication between them, either with a symmetric key (not recommended for production) or a certificate (the recommended way), so there is no worry. It's all tied to the account's access level, etc., so nobody can make an action that they normally wouldn't be allowed to do. Even the MCP is token-based, and there are prompt injection protections in place. The MCP is audited, and every mutation needs confirmation. The admin area is only accessible to the admin account anyway so normal users can't access it.  
  • Topics

×
×
  • Create New...

Important Information

This community uses essential cookies to function properly. Non-essential cookies and third-party services are used only with your consent. Read our Privacy Policy and We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue..