Jump to content
  • 0

Guards attackable


Question

Posted

Hi:)

I have less than 10 posts so I have to post my question here.

 

I would like to make Guards attackable as a small kind of "bot protection". Bot choses targets randomly but cant target a PK Guard (ctrl needed). I would like to set a guard to be targeted without a ctrl.

 

I found this:

L2GuardInstance.java

if (containsTarget(player))

{

if (_log.isDebugEnabled())

_log.debug(player.getObjectId() + ": Attacked guard " + getObjectId());

 

// Set the L2PcInstance Intention to AI_INTENTION_ATTACK

player.getAI().setIntention(CtrlIntention.AI_INTENTION_ATTACK, this);    <-----this should be modified

 

Please help me and give any info how do do this.

 

Thank you.

Regards.

8 answers to this question

Recommended Posts

  • 0
Posted

Well dude.. im not a pro but i dont think that this should be changed, cuz i think this sends packet that guard is auto-attackable... and as i understanded u wanna have a guard auto-attackable.

>> if (containsTarget(player))  this is checking if player is in aggroList (if he got karma or he had attacked guard), so...

 

Delete everything else and keep just the ATTACK_INTENTION or put something else instead  "if (containsTarget(player))" this.

  • 0
Posted

well the control intention just the attack state the basic thing is applied to all kind of npc instance at the same place so i guess you need to lookup the l2npc.java maybe(idk what chronicle you use maybe its not there) or the attackableai.java

  • 0
Posted

Dunno.. i just tried to delete aggroList check and Interact check, and put just an AI_INTENTION_ATTACK and it kinda worked...

 

well thats really depends on the ai engine so you cant say its work generally :)

  • 0
Posted

what chronicle you use maybe its not there)

 

Gracia Final

 

Dunno.. i just tried to delete aggroList check and Interact check, and put just an AI_INTENTION_ATTACK and it kinda worked...

 

So code should be like this?

 

public void onAction(L2PcInstance player)
{
	if (!canTarget(player))
		return;

	// Check if the L2PcInstance already target the L2GuardInstance
	if (getObjectId() != player.getTargetId())
	{
		if (_log.isDebugEnabled())
			_log.debug(player.getObjectId() + ": Targetted guard " + getObjectId());

		// Set the target of the L2PcInstance player
		player.setTarget(this);
	}
	else
	{
                player.getAI().setIntention(CtrlIntention.AI_INTENTION_ATTACK, this);
	}
       }

 

Once again thank you guys for your time to help me ;)

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

    • 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:  
    • i used guytis IL project and source. i found in his project there are 3 Client version source... 1,CliExt_H5   --->this one cant be compiled in VS2005,i did know why..is it for H5 client? 2,CliExtNew  --->this one is IL version ,but when i compiled it and use it.player cant login game,MD5Checksum wrong.i check the source code,but not found any hints. 3,L2Server    --->this one for HB client?im not sure...   so my question is what are the differences between these three versions of cliext.dll?how can i fix the issue of the MD5Checksum not matching problem?   01/29/2026 21:04:11.366, [CCliExt::HandleCheckSum] Invalid Checksum[1130415144] vs [-721420287] packet[dd] len[29] sum[2698] key[30] HWID[] Account[]! 01/29/2026 21:04:11.366, SocketLimiter::UserSocketBadunknownprotocol 11111111111 01/29/2026 21:04:11.366, [usersocket]unknown protocol from ip[113.137.149.115]!      
    • ## [1.4.1] - 2026-01-29   ### ✨ New Features - **Short Description**: Server owners can add a short tagline (up to 240 characters) on the server info page, under the "Online" status. It appears in the server list (By Votes) for VIP, Gold VIP, and Pinned servers so players see a brief summary at a glance.   ### 🔄 Improvements - **Server Info Page**: Description field is limited to 3000 characters with a character counter; the textarea is vertically resizable. A second **Save Changes** button was added at the bottom (after the description) for easier saving. - **Server Name**: In My Servers → Edit, the server name is read-only and can no longer be changed (avoids accidental changes and naming conflicts). - **Server Rows (By Votes)**: Short descriptions wrap correctly and no longer affect row height; long text is clipped to two lines so the list stays tidy and consistent.   ---
  • 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..