Jump to content

Recommended Posts

Posted (edited)

Hey,  correct me if i am wrong, but what i have noticed that 99% interlude packs still have this bug. I saw this in Acis, Frozen, Mobius and actually in all older packs.

 

DIFF:

Index: java/net/sf/l2j/gameserver/network/serverpackets/CharInfo.java
===================================================================
--- java/net/sf/l2j/gameserver/network/serverpackets/CharInfo.java	(revision 5)
+++ java/net/sf/l2j/gameserver/network/serverpackets/CharInfo.java	(working copy)
@@ -34,7 +34,7 @@
 		writeD(_activeChar.getX());
 		writeD(_activeChar.getY());
 		writeD(_activeChar.getZ());
-		writeD(_activeChar.getHeading());
+		writeD(0);
 		writeD(_activeChar.getObjectId());
 		writeS(_activeChar.getName());
 		writeD(_activeChar.getRace().ordinal());
@@ -180,7 +180,7 @@
 		
 		writeD(_activeChar.getAppearance().getNameColor());
 		
-		writeD(0x00); // isRunning() as in UserInfo?
+		writeD(_activeChar.getHeading());
 		
 		writeD(_activeChar.getPledgeClass());
 		writeD(_activeChar.getPledgeType());

 

Edited by Vilmis
Posted (edited)
		writeC(0x03);
		writeD(_activeChar.getX());
		writeD(_activeChar.getY());
		writeD(_activeChar.getZ());
		writeD(_activeChar.getHeading()); /* Removing this because it's Vehicle ID */

You are fixed character model heading only for known players, but for self in UserInfo forgot.

Edited by Rootware
Posted (edited)
43 minutes ago, Rootware said:

		writeC(0x03);
		writeD(_activeChar.getX());
		writeD(_activeChar.getY());
		writeD(_activeChar.getZ());
		writeD(_activeChar.getHeading()); /* Removing this because it's Vehicle ID */

You are fixed character model heading only for known players, but for self in UserInfo forgot.

I know this and yep, it's vehicle id.
Btw, what's about userinfo i think this  is client bug (ncsoft bug) or am i wrong? UserInfo even can not send heading. That's why never tried to fix it. I saw this bug in new clients and etc.

Edited by Vilmis
Posted (edited)
1 hour ago, Vilmis said:

I know this and yep, it's vehicle id.
Btw, what's about userinfo i think this  is client bug (ncsoft bug) or am i wrong? UserInfo even can not send heading. That's why never tried to fix it. I saw this bug in new clients and etc.

 

When you entering to the world you can see own/another character always with wrong heading. It's client bug, because model in client always spawns w/o server heading - always look to the east. While teleporting the heading saving and processing correct for all characters own or another.

Edited by Rootware
Posted
32 minutes ago, Rootware said:

 

When you entering to the world you can see own/another character always with wrong heading. It's client bug, because model in client always spawns w/o server heading - always look to the east. While teleporting the heading saving and processing correct for all characters own or another.

I know that as well, mate, but thanks for your info.
For example: UserInfo doesn't send heading at all, but for some reason many l2j packs still have this heading in UserInfo. Instead of heading should be vehicle id as well, but not heading.

Posted (edited)
1 hour ago, Vilmis said:

I know that as well, mate, but thanks for your info.
For example: UserInfo doesn't send heading at all, but for some reason many l2j packs still have this heading in UserInfo. Instead of heading should be vehicle id as well, but not heading.

 

Sure. You are right, my mistake. I meant TeleportToLacation packet. You can send him with special params (for disable black screen for teleport) after UserInfo packet while character entering onto the world and you will see correct character rotation.

Edited by Rootware
Posted (edited)

the only heading mistake on mobius god clients* is on teleport etc  

 

i havent see something else wrong

 

 

edit* i just read u talk about c6

 

my bad

Edited by Pamela32
Posted (edited)

It has been fixed since Kamael on L2J, so postIL chronicles, and probably few downgrades, aren't impacted.

 

If you ask "why", I would answer "why not" ? If we use a base L2J IL, we inherit from all L2J issues. Whoever use L2J IL shares a common pool of issues than people can eventually see and fix.

 

I won't blame you if you don't have EventTrigger, ShortCutDelete (than L2J doesn't even have nowadays, btw), ExDuelEnemyRelation or ExMPCCPartyInfoUpdate packets. Or one of the 20+ PvP event.

 

It's all about seeing it, first. That's simply tell you than every project shares the same mommy DNA.

 

Ty for the find.

 

@sotid Everytime you addKnownObject a Player on your knownlist. Which is : teleport and enterworld. Few appreciations of that edit is on a market, people won't be on the same heading anymore, or if you want to backstab correctly a Player (which didn't yet move) upon teleport on pvp grounds.

Edited by Tryskell
Posted
23 minutes ago, Tryskell said:

@sotid Everytime you addKnownObject a Player on your knownlist. Which is : teleport and enterworld. Few appreciations of that edit is on a market, people won't be on the same heading anymore, or if you want to backstab correctly a Player (which didn't yet move) upon teleport on pvp grounds.

Thank you!

Posted (edited)
4 minutes ago, sotid said:

Thank you!

 

For self teleport heading, you have to correctly address Player heading upon TeleportToLocation packet. CharInfo is only for others people who are appearing on a zone you are "seeing the first time".

 

Will be part of aCis rev 382, it is validated on L2OvC.

Edited by Tryskell
Posted
59 minutes ago, Tryskell said:

 

For self teleport heading, you have to correctly address Player heading upon TeleportToLocation packet. CharInfo is only for others people who are appearing on a zone you are "seeing the first time".

What you want do in TeleportToLocation packet? It doesn't have heading in interlude packet. Also, on teleport you don't need add correction or something like that for heading, because heading stays same after teleport and broadcasting correctly for others. 
Just only one main problem is to fix heading on first log in for yourself, because it's a visual bug of UserInfo which doesn't send heading at all.

Posted
2 minutes ago, Vilmis said:

What you want do in TeleportToLocation packet? It doesn't have heading in interlude packet. Also, on teleport you don't need add correction or something like that for heading, because heading stays same after teleport and broadcasting correctly for others. 
Just only one main problem is to fix heading on first log in for yourself, because it's a visual bug of UserInfo which doesn't send heading at all.

 

Try this up.

 

	@Override
	protected final void writeImpl()
	{
		writeC(0x22);
		
		writeD(_objectId);
		writeD(_x);
		writeD(_y);
		writeD(_z);
		writeD(_isFastTeleport ? 1 : 0); // 0 - with black screen, 1 - fast teleport (for correcting position)
		writeD(_heading);
	}

 

Posted (edited)
1 hour ago, Rootware said:

 

Try this up.

 


	@Override
	protected final void writeImpl()
	{
		writeC(0x22);
		
		writeD(_objectId);
		writeD(_x);
		writeD(_y);
		writeD(_z);
		writeD(_isFastTeleport ? 1 : 0); // 0 - with black screen, 1 - fast teleport (for correcting position)
		writeD(_heading);
	}

 

Did you try? This „FastTeleport“ works in interlude, but heading doesn't look like would be working as i mentioned before or maybe i'm wrong? You can add almost everything whatever you want to writeImpl() if they are in the bottom they won't break the packet.

btw, if  TeleportToLocation would send heading which means //goup should fix your heading when entered to world again and have heading from database, but it doesn't.

Edited by Vilmis

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

    • Added the protection module to the demo.   DDoS Guard Pro v2.0 is a system protection module for PlayMMO CMS designed to reduce the load on the website during HTTP floods, bot activity, suspicious frequent requests, and attacks on individual pages or API methods. Unlike simple global limiters, DDoS Guard Pro v2.0 supports flexible rules based on routes and HTTP methods. This allows you to block the entire site in a targeted manner, rather than blocking the entire site equally. You can set up protection for specific areas of the site, such as login, registration, APIs, administration, forms, and other sensitive areas. What is the purpose of the module? DDoS Guard Pro v2.0 helps protect your site from basic L7 attacks at the HTTP request level. The module is useful when your site receives: frequent requests from a single IP address; HTTP page floods; login or registration form flooding; automatic requests from bots; URL scanning; frequent API requests; suspicious activity spikes; load on individual CMS methods or pages. The module helps to reduce the load on PHP and CMS by limiting suspicious activity before it starts to create a serious load on the site. Main features Per-route and per-method Rate Limit In the new version, protection is configured not only globally, but also according to specific rules. You can set limits separately for: GET; POST; PUT; PATCH; DELETE; ALL. This allows you to flexibly protect different parts of your website. For example: for the login page, you can set a strict limit; for registration, you can set a separate limit; for the API, you can set a limit for reading and a limit for changing data; for regular website pages, you can set a soft limit or not set a limit at all. This approach reduces the risk of accidentally blocking regular users and makes the protection more accurate. Flexible rule system The module supports setting rules in the following format: METHODS|PATTERN|LIMIT|WINDOW|BURST_LIMIT|BURST_WINDOW|BLOCK_SECONDS|IDENTITY|NAME Example of rules: POST|*login*|10|60|5|10|600|ip|login_post POST|*register*|8|60|4|10|600|ip|register_post GET|*api*|300|60|80|10|120|ip|api_get PUT,PATCH,DELETE|*api*|80|60|20|10|300|ip|api_write This allows you to specify exactly: which HTTP methods to protect; which URLs or URL patterns to consider; how many requests are allowed; over what time period; what burst limit to use;  how many seconds to block the offender;  by which ID to count the limit;  what the rule is called. Burst protection against sharp spikes  In addition to the regular request limit, the module monitors sharp spikes of activity.  This is useful when a bot makes many requests in a few seconds. In this case, the protection can be activated faster, without waiting for the overall limit per minute.  Burst protection is especially useful for: authorization pages; registration; API; search; data submission forms; administrative sections. Support for different types of requests DDoS Guard Pro v2.0 works not only with POST requests. The module can control: GET — regular pages, API requests, search; POST — forms, login, registration, data submission; PUT — updating data via API; PATCH — partial data update; DELETE — data deletion; ALL — all methods at once. This makes the module suitable not only for regular sites, but also for CMS with API, personal accounts, game panels and administrative actions. Limit storage: Redis, APCu and file fallback In the new version, the module supports several options for storing temporary data. Available modes: Redis; APCu; file fallback. The auto mode tries to use the most suitable option: Redis; APCu; file storage as a fallback. Redis or APCu are suitable for more efficient operation, while the file storage is left as a fallback option for simple hosting environments that do not have additional extensions. JSONL logging The module records protection events in JSON Lines format. Logs are saved in the following file: storage/logs/ddos_guard.jsonl This format is more convenient than a regular text log, because each event is stored as a separate JSON record. The logs can record the following information: event time; IP address; HTTP method; URL; name of the triggered rule; reason for blocking; number of requests; action status; user-agent; protection mode. The JSONL format is convenient for analysis by external tools, log agents, and monitoring systems. Prometheus metrics DDoS Guard Pro v2.0 adds an endpoint for receiving metrics in Prometheus format. Endpoint: /?ddos_guard_metrics=TOKEN The token is set in the module settings. Metrics allow you to track: the number of processed requests; the number of rule activations; the number of blocks; activity by limits; protection events; module status. This allows you to connect monitoring and configure alerts so that the administrator can see when suspicious activity starts on the site. LOG ONLY mode The module has a LOG ONLY mode. In this mode, DDoS Guard Pro does not block users, but only records events and potential triggers in the log. This mode is recommended to be used after installation, in order to first see which rules are triggered, and only then to enable the real blocking.  This helps to avoid too strict limits and random blocking of regular users.  Support for Cloudflare and proxy  The module supports working behind Cloudflare or another reverse proxy.  With proper configuration, it is possible to take into account the real IP of the user, and not the IP of the proxy server.  This is important for sites that use:  Cloudflare; nginx reverse proxy; load balancers; CDN; hosting proxy protection. Nginx-recommendations DDoS Guard Pro v2.0 contains an example nginx-config: modules/ddos_guard/nginx-ddos-guard-example.conf This allows you to use the module as an additional application layer of protection, and to move the main coarse limits to the nginx level. Recommended protection scheme: Cloudflare / nginx / firewall → DDoS Guard Pro → PlayMMO CMS This approach is more correct than trying to solve all problems only at the PHP level.
  • 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..