Status: ✅ All code complete and ready for in-game testing
Date: October 27, 2025
Estimated Time: 15-30 minutes
Test the new API validation system in-game to:
- ✅ Verify it works correctly
- 📊 Get actual numbers for missing items
- 🔍 Identify specific items to add
- 📝 Generate data for database v2.1
IMPORTANT: You have developer addons enabled! Let's use them first.
-
Open the Ascension API Documentation addon:
- Check your AddOns menu or keybindings
- Search for "Vanity" or browse to "C_VanityCollection"
- ✅ Document available functions (screenshot if possible)
- ✅ Note function signatures and parameters
-
Open the Developer Console:
- Check UI Development Tools menu/keybindings
- ✅ Verify console is accessible
- ✅ Test basic Lua execution:
print("Dev console works!")
-
Test the Vanity API directly in console:
-- Check if API exists print(type(C_VanityCollection)) -- Get total categories local categories = C_VanityCollection.GetNumTransmogCategories() print("Categories: " .. categories) -- Test getting sources for first category local sources = C_VanityCollection.GetAllTransmogSources(0) print("Category 0 sources: " .. #sources) -- Inspect structure of first item if sources[1] then for k,v in pairs(sources[1]) do print(" " .. k .. " = " .. tostring(v)) end end
- ✅ Document the structure you see
- ✅ Note any unexpected fields or values
- ✅ Screenshot console output if possible
-
Document API findings:
- Total categories found: _______________
- Fields in each source: _______________
- Data structure matches expectations: ☐ Yes ☐ No
- Any surprises: _______________
-
Launch Project Ascension and log in to your character
-
Test the API dump command:
/av apidump- ✅ Wait for completion message
- ✅ Verify you see category counts
- ✅ Note the total item count
-
Save the data:
/reload- ✅ UI reloads
- ✅ SavedVariables file should now contain the dump
-
Test the validation command:
/av validate- ✅ See validation summary
- ✅ Note API total vs Database total
- ✅ Note number of missing items
- ✅ Note number of mismatches
-
Save validation results:
/reload
-
Open PowerShell in the repository folder:
cd D:\Repos\AscensionVanity
-
Run basic analysis:
.\utilities\AnalyzeAPIDump.ps1
- ✅ Verify it finds the SavedVariables file
- ✅ Check validation summary matches in-game results
- ✅ Review category breakdown
-
Run detailed analysis:
.\utilities\AnalyzeAPIDump.ps1 -Detailed- ✅ Check
API_Analysis\folder was created - ✅ Review the markdown report
- ✅ Check the raw Lua export
- ✅ Check
-
Open SavedVariables file:
<YOUR_WOW_PATH>\WTF\Account\<YOUR_ACCOUNT_NAME>\SavedVariables\AscensionVanity.lua- ✅ Search for
APIDump = { - ✅ Find
totalItems =and note the count - ✅ Search for
ValidationResults = { - ✅ Find
apiOnly = {section - ✅ Review first few missing items
- ✅ Search for
-
Document findings in this file (add to bottom):
- Total API items: [NUMBER]
- Total DB items: [NUMBER]
- Missing items: [NUMBER]
- Mismatches: [NUMBER]
- Sample missing items: [LIST A FEW]
-
Generate updated database:
.\utilities\UpdateDatabaseFromAPI.ps1 -Backup- ✅ Verify backup was created
- ✅ Check
VanityDB_Updated.luawas generated - ✅ Note total mappings count
-
Compare databases:
# Use your favorite diff tool code --diff .\AscensionVanity\VanityDB.lua .\AscensionVanity\VanityDB_Updated.lua
- ✅ Review added items
- ✅ Check for changed mappings
- ✅ Verify format is correct
- API Total: ~2000 items (could be more/less)
- Database Total: 1857 items (current count)
- Missing Items: ~144 items (the ones we're looking for!)
- Mismatches: Unknown (hopefully small number)
- How many items are in the API total?
- How many items are missing from our database?
- Are the missing items distributed across all categories or concentrated?
- Are there any unexpected mismatches?
- Do the item names look correct in the API dump?
You have access to powerful development tools:
-
Ascension API Documentation
- Browse available APIs and functions
- Real-time documentation lookup
- Useful for: Discovering new C_VanityCollection functions
-
Ascension UI Development Tools
- Frame inspection and debugging
- UI element analysis
- Useful for: Debugging our addon's UI components
-
Ascension Resources For Custom UI
- Custom UI resources and helpers
- Additional development utilities
Opening the Dev Console:
- Look for console commands in the UI Development Tools addon
- Typical commands:
/console,/devconsole, or button in addon menu
Useful Console Commands for Testing:
-- Test API availability
C_VanityCollection.GetAllSourceInfo()
-- Inspect specific creature
C_VanityCollection.GetItemInfo(123, 1) -- Replace with real CreatureID
-- Check if function exists
print(type(C_VanityCollection))
-- Dump all C_VanityCollection functions
for k,v in pairs(C_VanityCollection) do
print(k, type(v))
end
-- Quick validation check
/av validate
-- Get specific item details
/av iteminfo 12345 -- Replace with ItemID
-- Check category stats
/av statsAdvanced Debugging:
-- Enable verbose logging
AscensionVanity.DEBUG = true
-- Watch API calls in real-time
hooksecurefunc(C_VanityCollection, "GetAllSourceInfo", function()
print("GetAllSourceInfo called!")
end)
-- Inspect our database
/dump AscensionVanityDB
-- Check loaded item count
/dump #AscensionVanityDB.creatureToItem- Check if
C_VanityCollectionAPI exists:/av api - Make sure you're logged into Project Ascension (not retail WoW)
- Try
/reloadand run again
- Update the path in the script:
-SavedVariablesPath "YOUR_PATH" - Default path:
<YOUR_WOW_PATH>\WTF\Account\<YOUR_ACCOUNT_NAME>\SavedVariables\AscensionVanity.lua - Make sure you ran
/reloadafter/av apidump
- Make sure VanityDB.lua is loaded (check addon is enabled)
- Run
/av debugto verify database is loaded - Try
/reloadand run/av validateagain
Date Tested: _______________
Character: _______________
API Dump Results:
- Total items in API: _______________
- Categories found: _______________
- Processing time: _______________
Validation Results:
- API Total Items: _______________
- Database Total Items: _______________
- Exact Matches: _______________
- Missing Items (API only): _______________
- Mismatches: _______________
Sample Missing Items (first 5):
- [CreatureID] Item [ItemID]: _______________
- [CreatureID] Item [ItemID]: _______________
- [CreatureID] Item [ItemID]: _______________
- [CreatureID] Item [ItemID]: _______________
- [CreatureID] Item [ItemID]: _______________
Sample Mismatches (if any):
- Creature [ID]: API has [ItemID], DB has [ItemID]
-
PowerShell Analysis:
- Script ran successfully: ☐ Yes ☐ No
- Reports generated: ☐ Yes ☐ No
- Data looks correct: ☐ Yes ☐ No
Database Generation:
- Updated database created: ☐ Yes ☐ No
- Total mappings in new DB: _______________
- Looks ready to use: ☐ Yes ☐ No
Issues Encountered:
Additional Notes:
Once you've completed testing and documented results:
-
Review the findings and verify everything looks correct
-
Decide next steps:
- Option A: Use generated database immediately (if it looks good)
- Option B: Manually review missing items first
- Option C: Investigate mismatches before updating
-
Update this repository:
- Add your test results to this file
- Update PROJECT_STATUS.md with validation findings
- Commit the documentation updates
-
Let me know the results and we can:
- Fix any issues discovered
- Update the database with missing items
- Prepare for v2.1 release
- Full Guide: docs/guides/API_VALIDATION_GUIDE.md
- Quick Reference: docs/guides/API_QUICK_REFERENCE.md
- Session Notes: docs/SESSION_NOTES_2025-10-27_API_VALIDATION.md
Ready to test? Let's find those 144 missing items! 🔍