Addon resource quantification #14

New issue

Closed

opened 2026-08-27 19:55:38 +00:00 by Xeplosion · 0 comments

Xeplosion commented

2026-08-27 19:55:38 +00:00

Owner

What's the question or topic?

How should add-ons that grant MORE of a resource already tracked elsewhere
(RAM, storage, instance slots, backup capacity) be captured, so an
offering's effective total (base + purchased add-ons) is computable
downstream instead of buried in free-text notes?

Context / background

Example: BisectHosting's "BisectOne+" is a single $4.99/mo add-on that
grants +2 instance slots, +40GB storage, +2 backup slots, +40GB backup
storage, +4 daily backup slots, plus some non-quantitative perks. Today
this can only be recorded as one addon with the itemization in notes —
there's no structured way to sum "config.storage_gb + whatever add-ons add"
per offering.

Deeper issue found while investigating: "instance slots" (relevant to
multi-instance-panel providers like BisectHosting) isn't in the schema
AT ALL yet — not in config, not as a feature — independent of the add-on
question.

Options or approaches considered

Recommended: two connected schema additions —

Add instance_slots to the offering config vocabulary (baseline
count, addon-independent).
Add a resource_deltas object to addon: a flat, closed-vocabulary
map of resource -> increase amount, e.g.
{ "instance_slots": 2, "storage_gb": 40, "backup_slots": 2,
"backup_storage_gb": 40 }. Keys span both the config vocabulary and
backup-specific keys (conceptually mapping to feature_backups, not
config) in one flat object rather than two separate fields.

Alternative considered: two separate delta fields (config_deltas vs
backup_deltas) instead of one flat object — more rigid/self-documenting,
costs an extra field on every addon that uses either.

Not recommended: leave as-is (notes-only) — status quo, blocks the
analysis this issue exists to enable.

Checklist

I have searched for existing issues or discussions on this topic
This is a question or discussion, not a bug or feature request

### What's the question or topic? How should add-ons that grant MORE of a resource already tracked elsewhere (RAM, storage, instance slots, backup capacity) be captured, so an offering's effective total (base + purchased add-ons) is computable downstream instead of buried in free-text notes? ### Context / background Example: BisectHosting's "BisectOne+" is a single $4.99/mo add-on that grants +2 instance slots, +40GB storage, +2 backup slots, +40GB backup storage, +4 daily backup slots, plus some non-quantitative perks. Today this can only be recorded as one addon with the itemization in `notes` — there's no structured way to sum "config.storage_gb + whatever add-ons add" per offering. Deeper issue found while investigating: "instance slots" (relevant to multi-instance-panel providers like BisectHosting) isn't in the schema AT ALL yet — not in config, not as a feature — independent of the add-on question. ### Options or approaches considered Recommended: two connected schema additions — 1. Add `instance_slots` to the offering `config` vocabulary (baseline count, addon-independent). 2. Add a `resource_deltas` object to `addon`: a flat, closed-vocabulary map of resource -> increase amount, e.g. { "instance_slots": 2, "storage_gb": 40, "backup_slots": 2, "backup_storage_gb": 40 }. Keys span both the config vocabulary and backup-specific keys (conceptually mapping to feature_backups, not config) in one flat object rather than two separate fields. Alternative considered: two separate delta fields (config_deltas vs backup_deltas) instead of one flat object — more rigid/self-documenting, costs an extra field on every addon that uses either. Not recommended: leave as-is (notes-only) — status quo, blocks the analysis this issue exists to enable. ### Checklist - [x] I have searched for existing issues or discussions on this topic - [x] This is a question or discussion, not a bug or feature request

Xeplosion closed this issue

2026-08-27 20:19:35 +00:00

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

XeplosionGames/minecraft-provider-analysis#14

No description provided.

Rows
Columns