Jump to content

Recommended Posts

  • 3 weeks later...
  • 1 month later...
Posted

works perfectly, new things being added atm, autofighter being reworked, auto-box like walker has has been implemented as well as offset.

  • 1 month later...
Posted

what is better l2.net or l2 walker ?

Depends what you want to do,

 

If you want a super simple click and go and you don't mind spending money... walker is better.

 

If you want absolute control over everything the bot does and the ability to script anything that is missing or doesn't do exactly what you want to do and you want to bot for free... L2.Net is better.

Posted

very much so.... also I'd much rather know the maker of the bot i'm using. Makes me feel alot more comfortable knowing whats behind the scene... I've visited Slothmo in person and I can tell you this, hes one smart guy. I dont doubt him for a second. Mistakes are fixed very quickly and new content added that no other bots have. Also... L2.NET was the first bot to connect to servers IG without client hooks, making it very hard to detect client side. If not possible at all. Unless faulty packets were detected.... but then again anything unknown to IG gets passed on to the client, L2.NET will not touch it.

 

Overall, if you are worried about detection... L2.net will have a much better chance to go "under the radar" on the next bans. OOG on retail is unsafe because GG packets haven't been cracked... this is the case on l2Divine.... and most likely Walker. Most people dont even know that.

 

If you are wanting to go into the programming wold, or just learning about it. L2.net is also a nice baby step. Its not complete programming, but its a heck of a good step into the programming world. Learning c# is a piece of cake for me now.

Posted

why i've got strange lags on l2net ? i runned normal window cilent and second l2NET.

character in l2net were assist char in normal client. I've killed mob but on l2net it was still 'fighting'. On l2NET I saw drop just after few seconds.

Guest
This topic is now closed to further replies.


  • Posts

    • ⚡ Fast order delivery is active 24/7! Upgrade your personal Gmail to Gemini Pro with full 2TB storage and premium Google One features today.
    • Update M54: Global HP/MP/CP consumable handling expanded beyond combat-only usage. Offensive mage idle recovery with learned skill Battle Heal. Spellhowler/Storm Screamer prioritizes Hurricane, using Vampiric Claw mostly below 90% HP. Major structural refactor initialized: Added category/class organization such as Archer, Dagger, Tank, Mage, Healer, Support and Specialized class files. Further structural cleanup. Extracted combat memory/state and more class-policy logic from the main controller. Added global stuck/inactivity watchdog for bots blocked by terrain/geodata. Added unreachable dropped ground-item timeout/temporary blacklist. Reworked Necromancer/Soultaker PvP: Dominator level 78+ maintains learned Arcane Power toggle on. Overlord/Dominator level 44+ maintains learned Soul Guard toggle automatically. Stability/scalability update: Bot controller ticks staggered instead of all starting in the same phase: Same 350 ms update rate retained Reduces simultaneous AI workload bursts. Removed the old manual aggressive-monster EVT_AGGRESSION bridge. Phantoms now use native Lucera setActive() behavior so monsters aggro them naturally. Reduced unnecessary NPC scans and native AI event pressure. Added saved-bot equipment overrides using a separate database table:         lucera_autobots_items Existing lucera_autobots remains the main saved-bot identity/state table. Equipment rows are linked to saved bots through bot_id. Added optional convenience view to show bot name together with equipment overrides:         lucera_autobots_items_view Added editable equipment slots in columns: Weapon Shield Helmet Chest Legs Gloves Boots Necklace Left/Right Earrings Left/Right Rings Equipment override values: 0 = use normal class/level profile item -1 = force slot empty >0 = equip that Item ID Custom equipment works only for saved database bots. Default class/level equipment profiles remain unchanged. Supports custom equipment from No Grade to S Grade, regardless of the bot's current level. Added validation for invalid item IDs and incompatible equipment slots. Added handling for: Two-handed weapons vs shields Full-body armor vs separate leggings Added all-grade Soulshots and Spiritshots to bot inventory/replenishment so custom lower-grade weapons still use the correct shots. Mage profiles that already use Blessed Spiritshots keep that behavior with all relevant grades available. First save the bot normally so it exists in table:         lucera_autobots Then open:         lucera_autobots_items Find the row with the same bot_id and edit only the equipment slots you want. Example: weapon_id = 6608 shield_id = -1 helmet_id = 0 chest_id = 0 legs_id = 0 gloves_id = 0 boots_id = 0 This means: weapon_id 6608 → custom weapon shield_id -1 → no shield all 0 values → keep normal default profile equipment After editing the DB, despawn and respawn the saved bot so M54 reloads its equipment overrides. Do not edit bot_id. Use it only to identify which saved bot the equipment row belongs to.   DOWNLOAD
    • It will be multi client so it will detect the client from the files and adapt the packets and asset loading. I am aiming for C4 and H5 after IL
    • this is just to simplify your life, time, and can be done for free by yourself just watch some tutorials, in case you don't wanna waste time check it out!   https://l2getwork.art   https://l2getwork.art/showcase.html  
    • Good job! Any chance for it to be downgradeable or at least compatible with older chronicles?
  • 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..