Jump to content
  • 0

[HELP]Problem with a java code


Question

Posted

Hey guys i was trying to apply this java code:  http://maxcheaters.com/forum/index.php?topic=196515.0  . And i changed the id's of the classes that i didn't want to wear heavy .But now these classes in game do not equip any armor ! Btw i'm using interlude pack and eclipse to add the code!

 

Waiting for possible solutions!

14 answers to this question

Recommended Posts

  • 0
Posted

Hey guys i was trying to apply this java code:  http://maxcheaters.com/forum/index.php?topic=196515.0  . And i changed the id's of the classes that i didn't want to wear heavy .But now these classes in game do not equip any armor ! Btw i'm using interlude pack and eclipse to add the code!

 

Waiting for possible solutions!

try to make the l2pcinstance part like this

 

L2ItemInstance chest = getInventory().getPaperdollItem(Inventory.PAPERDOLL_CHEST);
        if (chest != null)
        {       
              L2ItemInstance[] unequipped = getInventory().unEquipItemInBodySlotAndRecord(chest.getItem().getBodyPart());
              InventoryUpdate iu = new InventoryUpdate();
              for (L2ItemInstance element : unequipped)                 
            	  iu.addModifiedItem(element);
              sendPacket(iu);           
        }

  • 0
Posted

the only this i've done is to change the id's of classes:

 

 

if ((item.getItem().getItemType() == L2ArmorType.HEAVY) && (activeChar.getClassId().getId() == 8) ||  (activeChar.getClassId().getId() == 9) ||  (activeChar.getClassId().getId() == 92) ||  (activeChar.getClassId().getId() == 93) ||  (activeChar.getClassId().getId() == 23) ||  (activeChar.getClassId().getId() == 24) ||  (activeChar.getClassId().getId() == 101 ) || (activeChar.getClassId().getId() == 102 ) || (activeChar.getClassId().getId() == 36) || (activeChar.getClassId().getId() == 37) || (activeChar.getClassId().getId() == 108) || (activeChar.getClassId().getId() == 109))

                    {

                        activeChar.sendPacket(new SystemMessage(SystemMessageId.CANNOT_EQUIP_ITEM_DUE_TO_BAD_CONDITION));

                        return;

                    }

  • 0
Posted

hey guys! the problem is located here!:

 

if ((item.getItem().getItemType() == L2ArmorType.HEAVY) && (activeChar.getClassId().getId() ==  ||  (activeChar.getClassId().getId() == 9) ||  (activeChar.getClassId().getId() == 92) ||  (activeChar.getClassId().getId() == 93) ||  (activeChar.getClassId().getId() == 23) ||  (activeChar.getClassId().getId() == 24) ||  (activeChar.getClassId().getId() == 101 ) || (activeChar.getClassId().getId() == 102 ) || (activeChar.getClassId().getId() == 36) || (activeChar.getClassId().getId() == 37) || (activeChar.getClassId().getId() == 108) || (activeChar.getClassId().getId() == 109))

                        {

                            activeChar.sendPacket(new SystemMessage(SystemMessageId.CANNOT_EQUIP_ITEM_DUE_TO_BAD_CONDITION));

                            return;

                        }

 

 

 

 

 

 

 

 

 

I deleted it and i could wear all armors with all classes.SO there must be a prob there! Any1 that knows rly well the java language can help me??I'm using Interlude pack ( i repeat it!)

 

Waiting

  • 0
Posted

hey guys! the problem is located here!:

 

if ((item.getItem().getItemType() == L2ArmorType.HEAVY) && (activeChar.getClassId().getId() ==  ||  (activeChar.getClassId().getId() == 9) ||  (activeChar.getClassId().getId() == 92) ||  (activeChar.getClassId().getId() == 93) ||  (activeChar.getClassId().getId() == 23) ||  (activeChar.getClassId().getId() == 24) ||  (activeChar.getClassId().getId() == 101 ) || (activeChar.getClassId().getId() == 102 ) || (activeChar.getClassId().getId() == 36) || (activeChar.getClassId().getId() == 37) || (activeChar.getClassId().getId() == 108) || (activeChar.getClassId().getId() == 109))

                        {

                            activeChar.sendPacket(new SystemMessage(SystemMessageId.CANNOT_EQUIP_ITEM_DUE_TO_BAD_CONDITION));

                            return;

                        }

 

 

 

 

 

 

 

 

 

I deleted it and i could wear all armors with all classes.SO there must be a prob there! Any1 that knows rly well the java language can help me??I'm using Interlude pack ( i repeat it!)

 

Waiting

so make it this way

if (activeChar.getClassId().getId() == 93 || activeChar.getClassId().getId() == 98 || activeChar.getClassId().getId() == 108 || activeChar.getClassId().getId() == 101 || activeChar.getClassId().getId() == 8 || activeChar.getClassId().getId() == 23 || activeChar.getClassId().getId() == 36)                         
                    {                            
                    	if (item.getItemType() == L2ArmorType.HEAVY)                             
                    	{                                        
                    		activeChar.sendMessage("Cannot equip item due to bad condition");
                            return; 
                         }    
                    }

;-)

  • 0
Posted

Ugly code :

 

if ((item.getItem().getItemType() == L2ArmorType.HEAVY) && (activeChar.getClassId().getId() ==  ||  (activeChar.getClassId().getId() == 9) ||  (activeChar.getClassId().getId() == 92) ||  (activeChar.getClassId().getId() == 93) ||  (activeChar.getClassId().getId() == 23) ||  (activeChar.getClassId().getId() == 24) ||  (activeChar.getClassId().getId() == 101 ) || (activeChar.getClassId().getId() == 102 ) || (activeChar.getClassId().getId() == 36) || (activeChar.getClassId().getId() == 37) || (activeChar.getClassId().getId() == 108) || (activeChar.getClassId().getId() == 109))
                        {
                            activeChar.sendPacket(new SystemMessage(SystemMessageId.CANNOT_EQUIP_ITEM_DUE_TO_BAD_CONDITION));
                            return;
                        }

 

Not ugly code :

 

if (item.getItem().getItemType() == L2ArmorType.HEAVY)
{
    switch(activeChar.getClassId().getId())
    {
        case 8:
        case 9:
        case 92:
        case 93:
        case 23:
        case 24:
        case 101:
        case 102:
        case 36:
        case 37:
        case 108:
        case 109:
            activeChar.sendPacket(new SystemMessage(SystemMessageId.CANNOT_EQUIP_ITEM_DUE_TO_BAD_CONDITION));
            return;
    }
}

 

It means IDs used ARE GOOD ONES. If you failed giving good classes Ids, don't expect it works fine.

  • 0
Posted

This is not a code beauty contest.

 

switch is more easy to read, and from what I know is faster than a serie of if.

Added to that, a clear code == less errors at the end.

 

@one_1, glad my code works.

  • 0
Posted

hey tryskell now that we 're  talking about java codes could u repair this code coz it's not working : http://www.maxcheaters.com/forum/index.php?topic=121108.0

 

I add this and i get paralized only in adding subclass and however after the subclass loads i do not get unparalized ( lol ) :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

    • 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]!      
  • 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..