WoWInterface - AceDB not building table

WoWInterface (https://www.wowinterface.com/forums/index.php)

- Lua/XML Help (https://www.wowinterface.com/forums/forumdisplay.php?f=16)

- - AceDB not building table (https://www.wowinterface.com/forums/showthread.php?t=55907)

AceDB not building table

I've been at this for hours and I'm not sure why it isn't working. I've been successful with AceDB with my previous Addon, but the only thing ending up in this addon's SavedVariables table is the profile keys; the data shown in the "defaults" table below is nowhere to be found.

File Structure

Code:

[root_folder][Libs][AceAddon-3.0]

[AceConfig-3.0]

[AceConsole-3.0]

[AceDB-3.0]

[AceEvent-3.0]

[AceGUI-3.0]

[AceHook-3.0]

[AceTimer-3.0]

[CallbackHandler-1.0]

[LibStub]

Ace3.lua

Ace3.toc

load_libraries.xml
core.lua

SuperCrits.toc

load_llibraries.xml

xml Code:

<Ui xmlns="http://www.blizzard.com/wow/ui/">
    <Script file="LibStub\LibStub.lua"/>
    <Include file="CallbackHandler-1.0\CallbackHandler-1.0.xml"/>
    <Include file="AceAddon-3.0\AceAddon-3.0.xml"/>
    <Include file="AceEvent-3.0\AceEvent-3.0.xml"/>
    <Include file="AceConsole-3.0\AceConsole-3.0.xml"/>
    <Include file="AceDB-3.0\AceDB-3.0.xml"/>
    <Include file="AceTimer-3.0\AceTimer-3.0.xml"/>
    <Include file="AceHook-3.0\AceHook-3.0.xml"/>
    <Include file="AceConfig-3.0\AceConfig-3.0.xml"/>
    <Script file="LibDataBroker\LibDataBroker-1.1.lua"/>
</Ui>

TOC File

Code:

## Interface: 70300

## Title: Super Crits

## Notes: Super Crits Description

## Author: Sweetsour

## Version: r01-beta

## SavedVariables: SCritsDB



## OptionalDeps: Ace3, LibAboutPanel



Libs\load_libraries.xml



core.lua

core.lua

Lua Code:

local FOLDER_NAME, SC = ...
 
local SCrits = LibStub('AceAddon-3.0'):NewAddon("SuperCrits", 'AceConsole-3.0','AceEvent-3.0','AceHook-3.0','AceTimer-3.0')
 
local defaults = {
    char = {
        damaging = {
            pet = true,
            dots = true,
            damage = true,
            threshold = {
                enabled = false,
                value = 2000000,
            },
        },
    },
}
    
function SCrits:OnInitialize()
    self.db = LibStub("AceDB-3.0"):New("SCritsDB",defaults)
end
 
function SCrits:OnEnable()
    self:RegisterEvent("PLAYER_REGEN_DISABLED")
end
 
function SCrits:PLAYER_REGEN_DISABLED()
    self:RegisterEvent("COMBAT_LOG_EVENT_UNFILTERED")
    self:RegisterEvent("PLAYER_REGEN_ENABLED")
end
 
function SCrits:PLAYER_REGEN_ENABLED()
    self:UnregisterEvent("COMBAT_LOG_EVENT_UNFILTERED")
    self:UnregisterEvent("PLAYER_REGEN_ENABLED")
end
 
function SCrits:COMBAT_LOG_EVENT_UNFILTERED(event,...)
 
end

I don't know Ace at all so I might be missing something but I see nowhere that defaults gets written (copied) to the SavedVariables table.

Line 20 in core.lua should be doing it. According to the official AceDB docs, it's correct. Just not sure why the table isn't showing up :(

iirc, the only time something gets written to the saved variables with Ace3-DB is when a profile has changed a setting from the defaults.

Not sure, you create defaults for char but you only define the global db?

What Seerah said. AceDB does not write anything to the SV file except for the profile keys, unless something has been changed by the user. If the value in the defaults table is the same as the user settings, there is no change, therefore nothing is written into the saved variables file.

Rilgamon, what Sweetsour wrote in his .toc is correct for AceDB, although you can use saved variables per character as well if you wanted. However, I always felt that was unnecessary since AceDB can use any combination of global, profile, char, faction, and a few other variants.

I do have one suggestion to make about line 20. Change it to include the true argument at the end. This will create a profile called Default when loaded into the game.

Lua Code:

self.db = LibStub("AceDB-3.0"):New("SCritsDB", defaults, true)

Oh, I just noticed that your OptionalDeps line in your .toc is missing LibStub and CallbackHandler-1.0, which should be listed before Ace3.

... And double check the order of your listed Ace3 components in load_libraries.xml. The listed order should exactly match the order listed in Ace3.toc. You do not need to list all the components if you aren't using them, but whichever ones you are using will depend on the load order of other components.