Jump to content
  • 0

[AuthD] ServerList packet


Question

Posted

Following NetPro data i interests the additional block what was added since Freya.

 

<?xml version="1.0" encoding="UTF-8"?>
<packet id="LS_SM_SERVER_LIST" xmlns="http://www.l2emu-unique.net" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.l2emu-unique.net ../../../schemata/packet.xsd">
	<byte alias="Game server count" id="gs_list" />
	<branch id="gs_list" condition="serverlist.ServerListPrelude">
		<byte alias="Last game server" type="GameServerName" />
	</branch>
	<loop id="gs_list">
		<byte alias="Game server" type="GameServerName">
			<scriptAlias id="__INVASIVE_AUTO_EXTRACT_GS_ID" />
		</byte>
		<branch id="gs_list" condition="serverlist.ServerListNamed">
			<bytes alias="Server name" type="auth.CustomServerName">
				<length>40</length>
			</bytes>
		</branch>
		<bytes alias="IPv4" type="IPv4">
			<length>4</length>
			<scriptAlias id="__INVASIVE_AUTO_REPLACE_GS_IP" />
		</bytes>
		<dword alias="Port">
			<scriptAlias id="__INVASIVE_AUTO_REPLACE_GS_PORT" />
		</dword>
		<branch id="gs_list" condition="serverlist.ServerListPrelude">
			<byte alias="Minimum player age" />
			<byte alias="PvP allowed" type="YesOrNo" />
			<word alias="Online players" />
			<word alias="Maximum players" />
			<byte alias="Online" type="YesOrNo" />
			<branch id="gs_list" condition="serverlist.ServerListC1">
				<dword alias="Type(s)" type="GameServerKind" />
				<branch id="gs_list" condition="serverlist.ServerListC2">
					<byte alias="Region" />
				</branch>
			</branch>
		</branch>
	</loop>
	<branch id="gs_list" condition="serverlist.ServerListFreya">
		<word alias="Non-padded bytes" id="bytesize" />
		<branch id="bytesize" condition="Positive">
			<branch id="bytesize" condition="serverlist.ServerList5Ex2">
				<bytes alias="Characters" type="ServerCharacterCount" />
			</branch>
			<branch id="bytesize" condition="serverlist.ServerList5Ex1">
				<byte alias="Game server count" id="gs_list" />
				<loop id="gs_list">
					<byte alias="Game server" type="GameServerName" />
					<byte alias="Total characters" />
					<byte alias="Pending deletion" id="timestamp_list" />
					<loop id="timestamp_list">
						<dword alias="Date of removal" type="SecondsSinceEpoch" />
					</loop>
				</loop>
			</branch>
		</branch>
	</branch>
	<!-- The rest is padding, except for 2nd last DWORD, which is the checksum -->
</packet>

 

Somebody to knows how the "ServerListFreya" block must to look in example? If i'm not mistake it's must add into every server list row the character count of this account for all servers in list. Or client isn't processing this data?

 

Thanks in advance.

4 answers to this question

Recommended Posts

  • 0
Posted (edited)

I am pretty sure that the character count per server is what is contained in that second loop, though personally i have not bothered with a  new Auth yet. i am pretty sure the loop is something like count of servers with characters, then a for each server, how many characters exist.

Edited by pada
  • 0
Posted

@pada ofc, i wanted to example of this loop. Working code. I checked many examples from L2J forks and nothing happened in my client. Maybe it's client side problem, but need be sure what server sent correct info. Otherwise it will looks like searching the black cat in dark room even his is not exists.

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

    • UPDATE M63 Introduced the first major Party Logic system: Bots can join and operate under a real-player party leader. Party members: follow the real player, assist the leader in combat, coordinate around the party leader, support party combat instead of behaving purely as independent farmers. Added initial party formation/follow behavior. Added party-aware PvP assisting.   Expanded Party Support / Party Combat behavior: Improved party coordination across different bot classes. Added broader healer/support participation. Expanded combat equipment/ammunition support, including all six arrow grades. Party members became more coordinated in PvP and group combat. Added improved bot reaction to resurrection situations. Added compatible resurrection-answer handling. Refined party formation behavior. Party combat became more persistent when members were attacked. Party members maintain combat participation more reliably instead of immediately dropping engagement.     Major Party Logic expansion:   Changed party travel formation Added temporary main assister leadership: if the real-player leader dies, a random living damage dealer becomes combat leader, other bots assist that damage dealer, if the assister dies, another DD can take over. Added special Bishop/Cardinal real-player leader logic: bots continue following the real player, a damage-dealer bot becomes the party’s combat assister. Added 5-second idle Party Logic: if the real-player leader stops moving/actively controlling combat for 5 seconds, bots can resume autonomous farming around the leader. Temporary main assisters use the bot’s already configured PvP mode instead of a separate Party Logic PvP system. Existing modes remain authoritative: Idle AttackFlagged AttackEveryone Temporary main assister can independently acquire PvP targets according to its configured mode. Other party bots assist that selected combat leader. Made Party Logic target acquisition party-location aware. While operating in a party, autonomous PvE/PvP searches can be centered around the real player’s current location rather than only the bot’s original farming position. Existing bot farmRadius remains the effective acquisition radius. This allows parties to travel away from their original farming areas while continuing to operate dynamically.     Expanded Bishop/Cardinal Party Logic behavior:   Bishop/Cardinal parties now use the same 5-second activity/idle model as normal real-player-led parties. While the Bishop/Cardinal leader is moving or active: bots prioritize staying with the real player, maintain the ~70–100 unit random formation. After the Bishop/Cardinal remains idle for 5 seconds: party bots may return to autonomous farming around the leader. When the Bishop/Cardinal starts moving again: party members transition back to following the leader. PvP remains independent of the PvE idle condition: valid PvP targets can still trigger combat according to each bot’s configured PvP mode.     Optional Hero System: Added a new hero_enabled option for Autobots. Bot creation gained Hero appearance: No / Yes. Existing bots default to hero_enabled = 0. Bots with hero_enabled = 1 spawn with native Lucera Hero status/aura/appearance through Player.setHero(true). Hero weapons configured through the existing Autobots item system can be equipped normally. This is intentionally visual/status Hero only: no Hero skill injection, no automatic native Hero skills, no changes to combat AI or targeting. Hero state can also be changed directly in the database and takes effect after respawning the bot.     DOWNLOAD
    • Throw a free cloudflare SSL cert in there. 😄
    • Nextarget was a LT international clan in Dawn and  Evoke and other servers, playing most in Interlude, so dunno if you try use this name to atrack the players or smth.
    • Server Specs ChapterInterlude Classic EXP / SP Ratex50 Adena Ratex30 Drop Ratex20 Spoil Ratex15 Max Level78 Website https://l2nextarget.com/ Start On Today At 22:00
    • Since last forums fail, I decided to introduce a little website over PTS server holder - just to make basic informations more reachable. You can discover it over http://anothercrappyinterludeserver.com/   Discord channels ACCESS TO SOURCES and SERVER INSTALLATION were also reworked to be easier to handle.
  • 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..