Jump to content

Recommended Posts

Posted

Hello Everybody, here is a simple Code. to Avoid Quest stucking and LAGS And more more Shits :)

 

Bypass Flood Protection:

 

### Eclipse Workspace Patch 1.0
#P L2_GameServer_It
Index: java/net/sf/l2j/gameserver/util/FloodProtector.java
===================================================================
--- java/net/sf/l2j/gameserver/util/FloodProtector.java	(revision 3695)
+++ java/net/sf/l2j/gameserver/util/FloodProtector.java	(working copy)
@@ -50,7 +50,7 @@
	// =========================================================

	// reuse delays for protected actions (in game ticks 1 tick = 100ms)
-	private static final int[] REUSEDELAY = new int[]{ 4, 42, 42, 16, 100 };
+	private static final int[] REUSEDELAY = new int[]{ 4, 42, 42, 16, 100, Config.PROTECTED_BYPASS };

	// protected actions
	public static final int PROTECTED_USEITEM		= 0;
@@ -58,6 +58,7 @@
	public static final int PROTECTED_FIREWORK		= 2;
	public static final int PROTECTED_ITEMPETSUMMON	= 3;
	public static final int PROTECTED_HEROVOICE		= 4;
+    public static final int PROTECTED_BYPASS        = 5;

	// =========================================================
	// Constructor
Index: java/config/options.properties
===================================================================
--- java/config/options.properties	(revision 3695)
+++ java/config/options.properties	(working copy)
@@ -16,6 +16,9 @@
# If next switch is set to true every newly created character will have access level 200.
EverybodyHasAdminRights = False

+# Protected Server Bypass.
+ProtectedBypass = 4
+
# Setting for serverList
# Displays [] in front of server name
ServerListBrackets = False
Index: java/net/sf/l2j/gameserver/clientpackets/RequestBypassToServer.java
===================================================================
--- java/net/sf/l2j/gameserver/clientpackets/RequestBypassToServer.java	(revision 3695)
+++ java/net/sf/l2j/gameserver/clientpackets/RequestBypassToServer.java	(working copy)
@@ -32,6 +32,7 @@
import net.sf.l2j.gameserver.model.actor.instance.L2NpcInstance;
import net.sf.l2j.gameserver.model.actor.instance.L2PcInstance;
import net.sf.l2j.gameserver.model.entity.L2Event;
+import net.sf.l2j.gameserver.util.FloodProtector;
import net.sf.l2j.gameserver.serverpackets.ActionFailed;
import net.sf.l2j.gameserver.serverpackets.NpcHtmlMessage;

@@ -64,6 +65,13 @@

		if (activeChar == null)
		    return;
+		
+        if (!FloodProtector.getInstance().tryPerformAction(activeChar.getObjectId(), FloodProtector.PROTECTED_BYPASS))
+        {
+                activeChar.sendMessage("You cannot bypass so fast.");
+                activeChar.sendPacket(new ActionFailed());
+                return;
+        }

		try {
			if (_command.startsWith("admin_")) //&& activeChar.getAccessLevel() >= Config.GM_ACCESSLEVEL)
Index: java/net/sf/l2j/Config.java
===================================================================
--- java/net/sf/l2j/Config.java	(revision 3695)
+++ java/net/sf/l2j/Config.java	(working copy)
@@ -588,6 +588,8 @@

    /** FloodProtector initial capacity */
    public static int              FLOODPROTECTOR_INITIALSIZE;
+    
+    public static int           PROTECTED_BYPASS;

    /** Allow Discard item ?*/
    public static boolean         ALLOW_DISCARDITEM;
@@ -1259,6 +1261,8 @@

                ONLY_GM_ITEMS_FREE                = Boolean.valueOf(optionsSettings.getProperty("OnlyGMItemsFree", "True"));

+                PROTECTED_BYPASS        = Integer.parseInt(optionsSettings.getProperty("ProtectedBypass", "4"));
+                
                ALLOW_WAREHOUSE                 = Boolean.valueOf(optionsSettings.getProperty("AllowWarehouse", "True"));
                WAREHOUSE_CACHE                 = Boolean.valueOf(optionsSettings.getProperty("WarehouseCache", "False"));
                WAREHOUSE_CACHE_TIME            = Integer.parseInt(optionsSettings.getProperty("WarehouseCacheTime", "15"));

 

 

1Thousent -beep-ing Sorrys is is already Shared.

Posted

But won't this affect every single type of bypass in the server? :s

I mean, you'll try to buff, and if you do it fast you'll get pwned ;s

 

Anyway, added at the list.

Posted

But won't this affect every single type of bypass in the server? :s

I mean, you'll try to buff, and if you do it fast you'll get pwned ;s

 

Anyway, added at the list.

Heheh i can't understand you.. When you Buff fast you mean? ??

 

You will get a message you Cannot Bypass So Fast. and the action will fail ( You won't take the effect )

Posted

Heheh i can't understand you.. When you Buff fast you mean? ??

 

You will get a message you Cannot Bypass So Fast. and the action will fail ( You won't take the effect )

 

That's what I mean..

Look at this:

if (!FloodProtector.getInstance().------------>tryPerformAction<---------------(activeChar.getObjectId(), FloodProtector.PROTECTED_BYPASS))
       {
               activeChar.sendMessage("You cannot bypass so fast.");
               activeChar.sendPacket(new ActionFailed());
               return;
       }

 

It won't affect just quests to reduce the lag, it will affect every single action xD

And it can become annoying :P

But since it's a protection, it may be useful to provent a few bugs..

Posted

lol, soz but This is Absolutely Needed for all server ( it won't fail every action you do, the fast actions :) )

With this you can Avoid SERVER POWN :(

 

naaaah every single client packet can be used to right a script and pwn a server, but anyway :P

Posted

:@ :) You Don't Understand ::) This is a simple flood for Bypass ( Anti-Lag )

 

If i have time later i will share a FULL Flood Protection :)

 

Nah I know what this shit is, lol..

Half of IT + Gracia projects use this..

 

My point is that it may become quite annoying for other people, if the value is set to a number > 1

 

But as I told previously, it can become quite useful to prevent server crashes and other little exploits and bugs.

Posted

# ServerBypass - server bypass flooding

FloodProtectorServerBypassInterval = 5

FloodProtectorServerBypassLogFlooding = False

FloodProtectorServerBypassPunishmentLimit = 0

FloodProtectorServerBypassPunishmentType = none

FloodProtectorServerBypassPunishmentTime = 0

Posted

# ServerBypass - server bypass flooding

FloodProtectorServerBypassInterval = 5

FloodProtectorServerBypassLogFlooding = False

FloodProtectorServerBypassPunishmentLimit = 0

FloodProtectorServerBypassPunishmentType = none

FloodProtectorServerBypassPunishmentTime = 0

My Share, is for L2J - IL With no rework on FloodProtection.

 

And is simple.

Posted

# ServerBypass - server bypass flooding

FloodProtectorServerBypassInterval = 5

FloodProtectorServerBypassLogFlooding = False

FloodProtectorServerBypassPunishmentLimit = 0

FloodProtectorServerBypassPunishmentType = none

FloodProtectorServerBypassPunishmentTime = 0

 

L2jCT2.3 files have a few floodprotectors ready and of course reworked.

So you can't compare IT fps and ct2.3 ones.

Posted

Fail, fail fail. It stops just the requestbypasstoserver packet. Not every single packet, rofl. For that you need a flood protector in every packet file. Nubz! that tryPerformAction is just the timer.

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

    • Yeah, for sure. Hardly anyone doesn't use it yet, but those few are gonna give in soon. I'm not judging anyone who uses it – that's not the point. The point is that people do use it. I use it, you use it, we all use it. These days, it's just NORMAL. And it's gonna keep getting more and more normal. But like I said, you still gotta know what you're actually doing.
    • Then that's the problem. Server owners are as bad as they used to be in 2005, 2010 and so on.    This scene has technically mature developers, always money-hungry server owners, but what both these groups lack, is some creativity ... I would never play in a server that needs 7 layers of anti-bot. If it needs 7 layers of anti-bot, it means its a bot friendly server and not something worth playing. 
    • Lineage just has a giga boring quest line / lore and since server owners are not reinventing the wheel, players are forced to F1 F2 spam by server design.
    • Players say: We don't have time, please add auto-farm to the server, after all, farming in L2 is the most repetitive and boring thing, it gives no enjoyment.    Then players say: OMG your server is full of auto-farmers with adrenaline. Use anti-cheat guards.    Excluding the hilarious fact that an auto-farm player is essentiall botting without botting software ...   Noone stops to ask the simple question: If nobody likes farming to that extend that they go as far as building complex bots and ask for server-side bot programs and then for no apparent reason have to build anti-bot guards ... MAYBE the problem is that "farming" is an outdated feature that has to be removed from your servers ?   What you people are building here is software that protects a game feature, nobody likes and nobody wants to use.   Has the mental capacity of server owners and developers fallen so many IQ points the last decade ? One comes back to see the same server setups of a decade ago, with zero innovation, zero creativity and a huge amount of time and resources protecting a game feature nobody wants to even use ... The other dissappointing thing one sees here, is that a lot of GREAT developers who now work full time jobs in corporate, come back here, to bash the work of others because they find their current job tasks not as fullfilling as when they would develope game related code for Lineage 2...   Talking about life choices eh ? 😛
    • Have u seen the message i sent you?
  • 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..