Vowbound
A marriage plugin for Spigot with a real ceremony, built on the eco framework.
Propose, get engaged, walk into a church, speak your vows, and get married in front of whoever came to watch. Vowbound runs a real six phase ceremony rather than a single command, and everything about it, the lines the Father speaks, the delays between them, the sounds, the rewards, is a config key.
New here? Start with Installation. It covers the requirement on eco, the install steps, and what the first run writes to disk.
Quick facts
| Server software | Spigot or a fork |
| Minimum version | 1.21.4 |
| Java | 21 |
| Needs | eco, installed and running first |
| The Father | FancyNpcs, then Citizens, then a plain villager, whichever is installed |
| Author | zArrowTan |
Getting started
Download
Where to get Vowbound and what to do once you have the jar.
Installation
Requirements, the install steps, the first run and what the plugin folder looks like afterwards.
Features
Marriage
Propose, accept or decline, a distance limit if you want one, and a cooldown after a divorce.
Churches
Set the region, the altar, the entrance and as many seats as you like, all from where you are standing.
NPC providers
FancyNpcs first, then Citizens, then a plain villager if neither is installed.
The ceremony
Procession, welcome, vows, the question, pronouncement, cleanup.
Menus
Every command is also a button, right down to picking who to propose to from a list.
Married life
A shared home, teleport requests, private couple chat, gifts, a kiss, and a yearly anniversary.
Configuration
Configuration
A walk through config.yml section by section.
Messages & language
Edit the built in messages, or add a translation of your own alongside English, French and Spanish.
Permissions
Every command node Vowbound registers, and its default.
Storage
Vowbound has no database of its own, marriage data goes through eco's.
Reference and help
Commands
Every player and admin command under /marry, with the permission each one needs.
Placeholders
The five PlaceholderAPI placeholders Vowbound registers.
FAQ
The questions that come up most often about installing and running the plugin.
Support
Where to get help and what to include so you get an answer on the first reply.
How much Vowbound actually leans on eco
More than "you need it installed." eco isn't optional plumbing here, large parts of Vowbound run directly through it rather than being built from scratch:
| What | Comes from eco |
|---|---|
| All player and server data | eco's own storage, backend picked in eco's settings, not Vowbound's |
| The in-game menus | eco's own menu system |
| Items like the wedding ring | eco's own item system |
| The marriage and divorce fee | eco's own economy/fee system |
| Config file updates | eco's own updater |
| Scheduling delays and timers | eco's own scheduler |
Database settings are not in Vowbound's config.yml at all. data-handler,
mysql: and mongodb: are keys in eco's config.yml, in eco's own plugin
folder. Vowbound has no storage section of its own to configure, on purpose, see
Storage for the exact keys and where to find them.
Practically: if you're used to a plugin owning its own database section, its own GUI
framework, its own item parsing, Vowbound doesn't have any of those, eco already does
all of it and Vowbound just calls into it. That's also why eco is a hard depend rather
than a soft one, Vowbound genuinely can't function without it.
Reload without a restart
/marry admin reload reloads config.yml, menus.yml, the active language file and
churches.yml in one go, and re-places every NPC in case npc.provider changed.