Jump to content

Recommended Posts

Posted

Just a heads up this is a very old version and a spammer brought it up! use it at your own risk!

That's What i call crazy dev :D Support on you and l2jhellas team (andon19)

thanks

  • 1 month later...
Posted

Hey dude i have an error on L2PcInstance  ----    if (CastleWars.CastleWarsRunning && (isinZodiac && pk.isinZodiac))

{

sendMessage("You will be revived in your spot");

 

}

if((pk.isinZodiac&&pk.isinZodiac)  && CaptureThem.CaptureThemRunning)

pk.ZodiacPoints ++;

  • 3 weeks later...
Posted

it's fully outdated this one :P i MIGHT do an adopted one with the new version only for l2jacis..

and when will release it any info about that ?

Posted

That's the worst approach to choose the lucky chest as there is a big possibility that no one will get the reward.

 

	public static void LuckyOne(L2PcInstance killer)
	{
		if (Rnd.get(50) == 2)
		{
			Announcements.getInstance().announceToAll(killer + " killed the lucky chest!");
			killer.addItem("Reward", Config.ZODIAC_REWARD, Config.ZODIAC_REWARD_COUN, killer, true);
			cleanthemess();
		}
	}

I suggest doing it like.
 

	private static int kills_req;
	private static int kills;

Inside the startevent() method:

 

		kills_req=Rnd.get(40);
		kills=0;

and

	public static void LuckyOne(L2PcInstance killer)
	{
		
		if (kills==kills_req)
		{
			Announcements.getInstance();
			Announcements.announceToAll(killer + " killed the lucky chest!");
			killer.addItem("Reward", Config.ZODIAC_REWARD, Config.ZODIAC_REWARD_COUN, killer, true);
			cleanthemess();
		}
		else
		{
			
			kills++;
			
			
		}
	}
Posted

 

That's the worst approach to choose the lucky chest as there is a big possibility that no one will get the reward.

 

 

	public static void LuckyOne(L2PcInstance killer)
	{
		if (Rnd.get(50) == 2)
		{
			Announcements.getInstance().announceToAll(killer + " killed the lucky chest!");
			killer.addItem("Reward", Config.ZODIAC_REWARD, Config.ZODIAC_REWARD_COUN, killer, true);
			cleanthemess();
		}
	}

I suggest doing it like.

 

	private static int kills_req;
	private static int kills;

Inside the startevent() method:

 

 

		kills_req=Rnd.get(40);
		kills=0;

and

	public static void LuckyOne(L2PcInstance killer)
	{
		
		if (kills==kills_req)
		{
			Announcements.getInstance();
			Announcements.announceToAll(killer + " killed the lucky chest!");
			killer.addItem("Reward", Config.ZODIAC_REWARD, Config.ZODIAC_REWARD_COUN, killer, true);
			cleanthemess();
		}
		else
		{
			
			kills++;
			
			
		}
	}

oh for christs shake i told 10000 times this is an old revision it's already changed!!!!!!!!!!!!!!!!!!!

  • 4 weeks later...
  • 4 years later...
  • 3 months later...

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

    • ## [1.5.1] - 2026-01-30   ### 🐛 Bug Fixes - **Top Voters**: Top voters list now loads correctly for inactive servers (previously showed "Server not found"). - **View Counter**: Server info page view count now records correctly for inactive servers.   ### 🔄 Improvements - **My Servers – Hide/Active**: The hide/active toggle now works correctly and is only shown when the server is approved (active) by an admin. Owner hide/show is separate from admin status. Toggling no longer causes a full page refresh. - **Accessibility**: Form fields across the site now have proper labels and IDs for screen readers and autofill — server info edit form, add server form, My Servers edit, Admin Panel (Email, Vote System, pricing, filters, logs), and related inputs.
    • LIVE VERIFICATION? SUMSUB? “IMPOSSIBLE”? ▪ Spoiler: it is possible — if you know who to work with. A client came in with a task to pass **live verification** on **WantToPay**, a Telegram virtual card service. On the platform side — **Sumsub**: liveness check, SMS, manual review. “Fast” and “by eye” simply don’t work here. › What was done: → analyzed the verification scenario and Sumsub requirements → built the correct flow: phone number, email, timing → **completed live verification remotely, without account handover** → handled SMS and confirmation codes → brought the process to final approval ▪ Result: → verification passed → access granted → no flags or repeat requests ▪ Live verification is not luck. It’s scenario-based preparation — not hope. › TG: @mustang_service ( https:// t.me/ mustang_service ) › Channel: Mustang Service ( https:// t.me/ +6RAKokIn5ItmYjEx ) *All data is published with the client’s consent.* #verification #sumsub #livecheck #kyc #case
    • IMPORTANT INFO: In a few days, I will switch to completely new code, written from scratch with a new download system, patch building and management system. The Updater will become true 2026 code with "foolproof systems". I'm going to create a Discord server for customers to request new ideas and features. FIRST CUSTOMERS ARE ALREADY USING THE NEW UPDATER ON LIVE SERVERS! Watch this topic for upcoming info because the new updater is around the corner! Yes, you can still use self-update on the previous updater! No, the new updater won't be compatible with the old patch system! A new build is required, but players who already have game files won't have to download the entire patch again! New templates and updates to existing templates are coming soon! Sneak peek:  
  • 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..