Jump to content

Question

Recommended Posts

  • 0
Posted

Try this:
 

	public void joinParty(L2Party party)
	{
		if (party != null)
		{
			_party = party;
			party.addPartyMember(this);
+			this.getAppearance().setNameColor(nameColor);
		}
	}

L2PcInstance.java;line ~5269;aCis

  • 0
Posted (edited)

Try this:

 

	public void joinParty(L2Party party)
	{
		if (party != null)
		{
			_party = party;
			party.addPartyMember(this);
+			this.getAppearance().setNameColor(nameColor);
		}
	}

L2PcInstance.java;line ~5269;aCis

 

thats shitty.

  • Others can see it
  • Its permanent
  • You dont handle party leave
  • not what he asked for
  • you dont need a null check as far as your pack is coded properly
Edited by xxdem
  • 0
Posted (edited)

You have to edit packets and check if is player inside activeChar's party and then broadcast another color.

Edited by St3eT
  • 0
Posted (edited)

 

thats shitty.

  • Others can see it
  • Its permanent
  • You dont handle party leave
  • not what he asked for
  • you dont need a null check as far as your pack is coded properly

 

Yeah I forgot to remove party color,but shouldn't others see it?What is the point of it if you are the only one who can see it?

 

+	int orgColor;
	public void joinParty(L2Party party)
	{
		if (party != null)
		{
			_party = party;
			party.addPartyMember(this);
		}
+		orgColor = this.getAppearance().getNameColor();
+		this.getAppearance().setNameColor(nameColor);
		
	}

	/**
	 * Manage the Leave Party task of the L2PcInstance.
	 */
	public void leaveParty()
	{
		if (isInParty())
		{
			_party.removePartyMember(this);
			_party = null;
		}
+		this.getAppearance().setNameColor(orgColor);
	}

If this isn't what thread author wanted,then I am sorry for misunderstanding.

or like St3et said:

 

if(_activeChar.isInParty())
    writeD(color);
else
    writeD(_activeChar.getAppearance().getNameColor());
Edited by StealthyS4m
  • 0
Posted

I doube that would change something. Since all party will have "same color". Else, you code it to give random color and store them, so another party won't take the same color.

  • 0
Posted

You need to send different nameColor in CharInfo packet. There are 2 places where you can inject the code:

1. In constructor of CharInfo. In my sources i have forPlayer parameter.

2. writeImpl() method in CharInfo.java. You can get info to who the packet is sent(getClient().getActiveChar()).

 

The code itself should look something like this:

if(player.getParty() != null && player.getParty().equals(forPlayer.getParty())
	_nameColor = 0x666666;
else
	_nameColor = player.getVisibleNameColor();

Take in mind you most likely have different sources than mine, so the exact code will not work but the way of doing this feature will be the same.

  • 0
Posted

A good idea is to be only self view and leader can have a different color name (well its not useless but its also useless) 

 

well vampir gaved the solution i guess

  • 0
Posted

You need to send different nameColor in CharInfo packet. There are 2 places where you can inject the code:

1. In constructor of CharInfo. In my sources i have forPlayer parameter.

2. writeImpl() method in CharInfo.java. You can get info to who the packet is sent(getClient().getActiveChar()).

 

The code itself should look something like this:

if(player.getParty() != null && player.getParty().equals(forPlayer.getParty())
	_nameColor = 0x666666;
else
	_nameColor = player.getVisibleNameColor();

Take in mind you most likely have different sources than mine, so the exact code will not work but the way of doing this feature will be the same.

 

getClient().getActiveChar() the dude that recieves

constructor parameter the guy who is broadcasted

  • 0
Posted

getClient().getActiveChar() the dude that recieves

constructor parameter the guy who is broadcasted

thats a good tip for me as a starter :D thanks lmao

  • 0
Posted

and you know how much random colors you can work on l2 :P

 

I doube that would change something. Since all party will have "same color". Else, you code it to give random color and store them, so another party won't take the same color.

10 or more? :D

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

    • Some new features that we added: - 2 new quests - PvP Arena (to get hero status) Olympiad is disabled - Love Event - Dressme for armor/weapons/accessories - HWID Protection - More monsters - New farm zone - New autofarm system (works almost like adrenaline) - Auto enchant - Auto augment - 3 levels of armors - 3 levels of weapons - Anti KS System - Rebirth Manager - 30 days checking rewards - Small event (daily checking with small reward for all online players)
    • Added FloodProtector utility to prevent packet flooding for actions like item use and dice rolling. Integrated flood protection checks in relevant client packet handlers and registered/removal hooks in player lifecycle. Updated movement logic in L2PcInstance for improved position synchronization and geodata handling. Minor fixes and refactoring in attack logic, private store handling, and admin NPC editing. Refactored AI classes to enhance movement, attack, and skill usage logic for characters and mobs. Improved distance checks, attack range calculations, and skill casting conditions. Removed unused intention command logic from L2CharacterAI. Updated configuration to enable CellPathFinding. Minor code cleanups and bug fixes for more reliable AI behavior. Enhanced GeoPathFinding with detailed debug and error messages for region loading, including success/failure counts and file checks. Refactored L2AttackableAI and L2CharacterAI to improve attack range tolerance, immediate attack behavior, and added safety checks for missing targets. Updated configuration to disable CellPathFinding by default and added a new ShowRedName option for aggressive mobs. Minor config and log updates included. Applied TCP socket optimizations (e.g., TCP_NODELAY, buffer sizes, keepalive) in ClientThread, Connection, and SelectorThread to reduce latency and improve throughput. Enhanced L2AttackableAI with better random walk, aggro, and attack logic, including silent move checks, quest monster handling, and improved faction/raid/minion behavior. Added silent move support to L2PlayableInstance and quest monster flag to L2NpcTemplate/L2NpcInstance. These changes aim to improve server responsiveness, AI realism, and overall stability.
    • I’ve been using this Escape from Tarkov Hack for about a week now with no issues at all. ESP works great without any lag, and the aimbot is smooth and doesn't feel obvious. Had a quick setup with the loader, and support answered my questions right away. The HWID spoofer also did its job without messing with my system. So far, the cheat's staying undetected on my side.
  • Topics

×
×
  • Create New...

AdBlock Extension Detected!

Our website is made possible by displaying online advertisements to our members.

Please disable AdBlock browser extension first, to be able to use our community.

I've Disabled AdBlock