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

    • I saw a few similar systems and came up with this one to help keep players on the server. It simply grants daily items every 24 hours just for logging in. There’s also the daily mission system—which assigns different tasks each day—where if you don't complete them within that 24-hour window, you get a new set of missions the next day. Sometimes, when starting out on a low-rate server (like x3), that little bit of help comes in handy—especially if you're playing solo without a clan or friends. I know there are quests to earn adena, but imagine being able to create an item that provides minor buffs or potions—nothing that would affect base stats or unbalance the server, of course; everyone can use the system however they like. I’m not looking to argue about this, haha; if anyone is interested, feel free to reach out. I’m open to criticism, too—no worries there. I just thought I’d post it. Thanks for the advice; I’ll keep improving the system and the interface. Tomorrow—or whenever I can—I’ll upload a short video so you can get an idea of what it’s like. I simply looked at what others had done and wanted to create something different, that's all, my friend. Cheers!
    • Your standard daily login reward is pointless. Why would you implement something like this? Where did this idea even come from?   No, it’s called OneDayReward, not Daily Missions. That’s the name used by the game client. Anyways. Good luck!
    • What you're talking about, my friend, is the "daily mission reward" system—that’s something different. This one is a standard daily login reward: if you don't log in on a given day, you miss that prize, and once you reach the final day (Day 28), it resets to Day 1. Check the forums or other sites; you'll see it's not the same thing. I also have that "daily mission reward" mod you're referring to—the one involving levels, mob counts, and class changes—but this is different; it's strictly for logging in. You have to stay online for half an hour to claim it, though that duration can be adjusted (from fewer to more minutes). It also features IP protection, and if you haven't claimed the prize for the day, the window opens automatically when you log in with your character so you don't forget. If you *have* claimed it, the window won't pop up automatically until the next day (though the auto-open feature can be enabled or disabled). Plus, as I mentioned, you can customize the item quantity, item ID, and the item icon. Cheers! I understand it's not finished; in fact, it's the V1 version I created. It is vulnerable, of course—since it relies only on IP, anyone could just use a VPN to bypass it—but I’ll keep working on adding security measures like MAC address and HWID checks, or anything else I come up with. Also, as you know, these are tradeable items; you can set the trade attribute to "false" in the item's XML file. It’s just an example of a system I started building. Cheers!
    • What’s the point of giving away free items every day just for logging in? That’s only about 5% of what the feature is supposed to be. If you want to implement the One Day Reward system from Classic/Essence, there’s a lot more to it: triggerType=KILL/LEVEL_UP, conditionLevel, canLevelMin, canLevelMax, classFilter, killCredit=SOLO/PARTY/CLAN, npcIds, isNoble, isHero, IsDayOfTheWeek, olympiad conditions, etc.
    • Yes, it's L2J—specifically L2Lucera—but it can be adapted for L2jAcis and Lucera; I imagine it would work for High Five as well. For now, I've only implemented it in L2Lucera (Interlude), but it will be available for L2jAcis too. Regards. As soon as you log in with your character, the window opens automatically so you can collect your reward. You can change the daily item ID and icon, and even set a waiting period—like 30 minutes—before collection is allowed. It includes IP protection, so players can't claim rewards using other accounts or create new ones to exploit the system; you can also adjust the number of days (e.g., 28, 1, or however many you prefer), and every feature can be enabled or disabled. The player command is `.daily`, and there are also four GM commands. I’ll be uploading a short video tomorrow to show everything more clearly. I also plan to improve the HTML window design and add MAC and HWID systems to prevent users from bypassing IP restrictions via VPNs or abusing the system with multi-accounting—basically, I’ll be continuously refining the system.
  • 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..