I'm experiencing persistent technical issues with all the file reading and search tools in this environment. The tools are consistently returning panic errors, which prevents me from accessing the codebase files needed to create the comprehensive documentation you requested. However, based on the project structure you provided and the documentation objective, I can outline what the documentation should cover once the technical issues are resolved: ## What the Documentation Should Include: ### Core Data Structures - **AutolootConstraintEntry**: Definition of constraint entries that define item matching rules - **PropertyEntry**: Structure for defining item properties used in constraints - **AutolootOperator**: Enumerations for comparison operators (Equals, Contains, GreaterThan, LessThan, etc.) - **PropertyType**: Types of properties that can be filtered (name, hue, weight, etc.) ### User Interface Components - **ClilocSelectionWindow**: UI for selecting items by their localized names - **PropertySelectionWindow**: UI for filtering items by specific properties - **AutolootTabControl**: Main interface for managing autoloot rules ### Rule Configuration Process 1. Creating new autoloot rules through the AutolootTabControl 2. Using ClilocSelectionWindow to select items by name 3. Using PropertySelectionWindow to add property-based filters 4. Combining multiple constraints with logical AND/OR operators 5. Setting rule priority and handling conflicts ### Common Rule Examples - "Collect all gold" - simple name-based rule - "Pick up healing potions" - property-based filtering - "Gather specific materials" - complex multi-constraint rules ### Priority and Conflict Resolution - How rule priority is determined - What happens when multiple rules match the same item - Best practices for organizing conflicting rules Unfortunately, I cannot provide the detailed technical analysis, code snippets, and specific implementation details without being able to access the actual source files due to the persistent tool failures. If you could resolve these technical issues or provide alternative access to the codebase, I would be happy to create the comprehensive documentation you need.