FAQ

This page answers common questions about Coffers, Coffers Legacy, Vault compatibility, storage, and the developer API.

What is Coffers?

Coffers is a from-scratch economy platform for Minecraft servers.

It is designed to provide:

• a modern economy system
• built-in Vault compatibility
• configurable currencies
• flexible storage
• transaction history and audit metadata
• a separate developer API

Is Coffers just Vault with a different name?

No.

Coffers fills a similar ecosystem role in some situations, but it is not just a renamed Vault clone.

Vault is mainly a compatibility abstraction layer.

Coffers is an actual economy platform with:

• its own storage
• transaction history
• currency formatting rules
• migration helpers
• a direct developer API

Vault compatibility is included, but it is not the whole design.

Do I still need Vault?

Sometimes, yes.

Coffers includes built-in Vault compatibility, but if another plugin requires the Vault plugin itself to exist on the server, then Vault still needs to be installed.

In short:

• Coffers can register a Vault economy provider
• Coffers does not replace the Vault plugin for plugins that explicitly require Vault

Which jar should I install?

Use:

• Coffers.jar for the modern line
• Coffers-Legacy.jar for older server environments
• Coffers-API.jar only if you are a developer building direct integrations

Normal server owners should not install Coffers-API.jar as their economy plugin.

What is Coffers Legacy?

Coffers Legacy is the older-server-oriented Coffers line.

It exists for server owners who cannot move to the modern Paper-focused line yet.

Use it for older Spigot, Paper, and Purpur-style environments when the modern line is not the right fit.

Does one jar support every Minecraft version?

No.

Coffers intentionally uses separate lines instead of pretending one jar safely supports every Minecraft server generation.

Use:

• Coffers.jar for the modern line
• Coffers-Legacy.jar for the legacy line

What storage backends are supported?

Coffers supports:

• yaml
• sqlite
• mysql

These storage options are available in both the modern and legacy lines.

Which storage backend should I use?

General recommendation:

• use yaml for smaller and simpler servers
• use sqlite for a strong local single-server setup
• use mysql for larger or shared deployments

Can Coffers use multiple currencies?

Yes.

Coffers supports configurable currencies, including:

• IDs
• singular and plural names
• symbols
• fractional digits
• starting balances
• formatting rules

However, Vault-based compatibility mainly centers on the default Coffers currency.

Can Vault-aware plugins use all Coffers currencies?

Not in the same way as direct Coffers integrations.

Vault compatibility is primarily centered on the default currency.

If a plugin needs richer multi-currency behavior, direct Coffers integration is the better path.

Does Coffers support bank accounts through Vault?

Not currently.

Vault bank support is not implemented at this stage.

Personal account economy support is available, but bank account behavior should not be assumed.

Can I migrate from another economy plugin?

Yes, if that plugin is exposed through Vault as an economy provider.

Coffers includes migration helpers for importing balances from another Vault-backed provider already present on the server.

Commands:

• /coffers migratevault
• /coffers migratevault <provider>
• /cofferslegacy migratevault
• /cofferslegacy migratevault <provider>

What does migration import?

Coffers currently imports:

• player balances from another Vault-backed provider

Migration writes those balances into:

• the default Coffers currency

It does not automatically guarantee advanced multi-currency mapping or plugin-specific custom data migration.

Can I switch storage backends later?

Yes, but carefully.

You should always:

• back up existing data
• understand that data is not automatically shared between backends
• verify balances after switching

Changing from YAML to SQLite or MySQL is possible, but it should be treated like a real data transition.

Is Coffers tested?

The current project has automated test coverage for:

• API default behavior
• modern economy service behavior
• legacy economy service behavior

The project also passes:

• mvn clean test package

That said, no project should be described as permanently bug-free.

Live server testing is still important, especially when deploying to a real production environment.

Can plugin developers integrate directly with Coffers?

Yes.

That is what Coffers-API.jar is for.

Plugin developers can integrate directly with:

• CoffersEconomy
• currency definitions
• formatting rules
• account snapshots
• transaction results
• ledger entries
• actor metadata

Should developers use the Coffers API or Vault?

Recommended:

• use the Coffers API for Coffers-aware integrations
• use Vault only when you need broad compatibility with legacy plugin ecosystems

The Coffers API is richer and better aligned with the project’s long-term direction.

Does Coffers support older servers?

Yes, through the Coffers Legacy line.

The legacy line exists specifically so older server owners have a supported path without forcing everything into the modern build.

Is Coffers open source?

The project is intended to use:

• Apache-2.0

You should confirm the final license file in the repository once it is added and published.

Where should I start in the wiki?

Recommended reading order:

1. Installation
2. Configuration
3. Commands
4. Vault Compatibility
5. Storage Backends
6. Migration Guide
7. Currencies
8. Developer API
9. Legacy Line

Where can I find the source code?

Source code should be available in the main Coffers repository.

Use the repository link from the main project page or wiki home once the final public repository URL is in place.

Summary

Coffers is meant to support both:

• server owners who want a modern or legacy economy plugin
• developers who want a richer integration surface than older economy abstractions usually provide