Jump to content

Question

12 answers to this question

Recommended Posts

  • 1
Posted (edited)
3 hours ago, Edasbeast said:

not working this.

you could search about 1 sql query at google as @SweeTs mentioned.

 

The correct query is 

DELETE FROM droplist WHERE itemid <> 57

probably nightwolf made a mistake and used operators from SELECT command but the thought is the same

 

P.S. this query will delete drops even from raidbosses/grandbosses. in case you want an exception for those types you can edit the query 

Edited by melron
  • 0
Posted
1 hour ago, SweeTs said:

Execute proper sql query, delete all from spawnlist except adena. 

maybe you know navicat command to remove droplist from monsters?

  • 0
Posted (edited)
DELETE * FROM `items` WHERE `item_id`!='57'

analyzing the query.

delete (everything) from (table name) where item id(column name) is not equal (!=) to adena (57)

 

12 hours ago, Solomun said:

Depends on what client u are working on. High5 stores droplist in npcs.xml


he asks for frozen so its obviusly GoD !

Edited by Nightw0lf
  • 0
Posted
54 minutes ago, Nightw0lf said:

DELETE * FROM `items` WHERE `item_id`!='57'

analyzing the query.

delete (everything) from (table name) where item id is not equal (!=) to adena (57)

 


he asks for frozen so its obviusly GoD !

Oh lul, i didn't notice....My bad

  • 0
Posted
3 hours ago, Nightw0lf said:

DELETE * FROM `items` WHERE `item_id`!='57'

analyzing the query.

delete (everything) from (table name) where item id(column name) is not equal (!=) to adena (57)

 


he asks for frozen so its obviusly GoD !

not working this.

  • 0
Posted (edited)
2 hours ago, Edasbeast said:

not working this.

this is why I analyzed it for, so you can change it according to your database.. its not out of the box I just created it without having any idea what table or what l2jfrozen calls the item id in the database since you dont provide more info about it, it works but you have to be smart to edit it.

 

22 minutes ago, melron said:

you could search about 1 sql query at google as @SweeTs mentioned.

 

The correct query is 


DELETE FROM items WHERE item_id <> 57

probably nightwolf made a mistake and used operators from SELECT command but the thought is the same

I just wake and saw that and replied without having a coffee :)

 

additional conditions for raid bosses

DELETE FROM items WHERE item_id <> 57 AND npc_id <> 2222

OBVIOUSLY where 2222 is the example boss that you want this query to ignore

and where npc_id is your table column that holds the monster id

if you want more (you should) you continue with

AND npc_id <> number AND npc_id <> number AND npc_id <> number AND..

Edited by Nightw0lf
  • 0
Posted (edited)

Ok @Nightwolf now i'm laughing about 5 minutes non-stop. the guy want to delete drops not items at inventory. we are both so blinds

giphy.gif

 

 

DELETE FROM droplist WHERE itemid <> 57

 

 

Edited by melron
  • 0
Posted
57 minutes ago, melron said:

you could search about 1 sql query at google as @SweeTs mentioned.

Pointless as it's better to wait day or even two to get ready answer. =) 

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 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?
    • Fermata now runs in a web browser too. Try it here: https://web.fermata.gg/    
  • 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..