Player Auto-Loot Corpse Item 2025-2-13

Auto-Loot Script Functionality Description

1. Core Features​

• Auto-Loot Configuration: Players can open a configuration interface (Gump) by entering the AutoLoot command to manage the list of items to be auto-looted.
  • Add Items: By clicking the "Add Item" button, players can select a target item, and the system will record its type name, ID, hue, and display name.
  • Remove Items: Each item has a delete button next to it, allowing players to dynamically remove items from the configuration.
  • Pagination: Up to 20 items are displayed per page, with support for multi-page navigation.
• Profile Storage:
  • Each player's configuration is saved independently as an XML file (path: Data/AutoLoot/{PlayerSerial}.xml).
  • Stored fields include the item type name, ID, hue, and display name (custom item names are prioritized).
• Auto-Loot Logic:
  • When a player opens a corpse (e.g., a loot container after defeating an enemy), the system triggers auto-looting after a 100-millisecond delay.
  • Based on the player's configuration, items of matching types are automatically transferred to the player's backpack, and a notification message is sent (e.g., "Auto-Loot: Gold").

---

2. Script Collaboration Workflow​

1. Player enters the AutoLoot command → Calls AutoLootCommand → Opens the configuration interface.
2. Player adds/removes items → Data is saved to an XML file via AutoLootProfile.
3. Player opens a corpse → Triggers the modified logic in the Corpse class → Checks the configuration and auto-loots matching items.

---

3. Potential Considerations​

• Matching Rules: Matching is based on the item type name (e.g., Gold, Bandage), not the item name or ID. If items of the same type have different uses, the configuration may need refinement.
• Thread Safety: The delayed looting (Timer.DelayCall) must ensure that the corpse and item states do not change during the delay.
• Performance Optimization: If a corpse contains a large number of items, traversal checks may impact performance. Consider using a hash table (e.g., HashSet<string>) to speed up type matching.
• Configuration Conflicts: When multiple players modify configurations simultaneously, ensure proper file locking mechanisms to avoid data corruption.

---

4. Extensibility Suggestions​

• Conditional Filtering: Add conditions for looting (e.g., item quality, quantity thresholds).
• Category Management: Support grouping configurations by item categories (e.g., weapons, potions).
• Logging: Record auto-loot actions for player tracking.

---

This script provides players with a convenient auto-loot management feature, combining a configuration interface with backend logic to significantly improve in-game looting efficiency.