Storage
Vowbound has no database of its own, marriage data goes through eco's persistent data layer instead.
This is the single most missed thing about Vowbound. There is no storage: block
in Vowbound's config.yml, no mysql: section, nothing. If you came here looking for
it, skip straight to Setting the backend below.
Vowbound stores nothing of its own, no JDBC, no connection pool, no data.db. Every
piece of marriage data goes through eco's own persistent data layer instead.
Setting the backend
The server owner already has this pointed at one of three backends, set in eco's
config.yml, in eco's own plugin folder, not Vowbound's:
# plugins/eco/config.yml
data-handler: yaml # or mysql, or mongodb
mysql:
host: localhost
port: 3306
database: database
user: username
password: p4ssw0rd
mongodb:
url: ''
database: eco
collection: profilesWhichever one is chosen, Vowbound's data rides along with every other eco plugin already on the server. There's nothing to configure on Vowbound's side, and no separate database to install or point anywhere.
What is stored
For each player: whether they're single, engaged or married, who to, when they married, when they last divorced, their shared home, and their chat/teleport/gift toggles.
Server-wide: how many couples are currently married and how many ceremonies have run,
for the placeholders, and the list of couples that
/marry list shows.
Churches are admin setup rather than player data, so they're kept separately in
churches.yml on disk instead of going through eco at all, see Churches.