Rank-based usage limits
All products remain version 1.0.0. Limits apply to creating content, not opening menus or browsing.
| Product | Permission | Counted allowance | Default without numeric permission |
|---|---|---|---|
| StrawOrder | strawio.order.limit.<number> |
Active orders, including funding and open orders with uncollected deliveries | order.max-active-orders (26) |
| StrawAuction | strawio.auction.limit.<number> |
Open, reserved and externally settling listings | auction.default-listing-limit (25) |
| StrawBounty | strawio.bounty.limit.<number> |
Bounty additions per UTC calendar day, including pending/uncertain payments | limits.daily-additions (-1 = unlimited) |
| StrawHomes | strawio.homes.limit.<number> |
Saved homes | limits.default (2) |
No matching entries.
Numeric nodes are dynamic: any integer from 0 to 2147483647 works without listing it in config. They are not granted by default. The highest granted numeric value wins, replacing the configured fallback even when lower. A false permission grants no allowance. 0 prevents new creations; it does not remove existing data. Keep ordinary feature permissions such as strawio.order.create enabled as well.
strawio.<product>.unlimited bypasses the allowance, except Homes where all grants are capped at 19. Order/Bounty default false; Auction/Homes retain their existing operator bypass. Test ranks on a non-OP account without wildcard permissions. A numeric wildcard is not a number; use the explicit unlimited node.
Examples with LuckPerms (substitute your own group names):
/lp group default permission set strawio.order.limit.2 true
/lp group vip permission set strawio.order.limit.10 true
/lp group default permission set strawio.auction.limit.3 true
/lp group vip permission set strawio.auction.limit.15 true
/lp group default permission set strawio.bounty.limit.2 true
/lp group vip permission set strawio.bounty.limit.10 true
/lp group vip permission set strawio.homes.limit.5 true
Bounty counts additions, including top-ups to the same target. Definitively declined payments release their allowance; pending/uncertain ones keep it. A new UTC day starts a fresh allowance without deleting records. Successful payments and retries retain their existing journal identity. No timezone or daily-reset timer is required; keep network clocks synchronized.
Order and Auction reuse their existing database admission locks. Bounty checks the shared payment journal under the same transaction lock and adds an account/date index. Shared storage counts usage across servers; synchronize permission groups across those servers too and update every participating server to this build (older builds cannot enforce the new limits). Permissions are captured on the player/entity thread before asynchronous database work. Auction captures its allowance when the draft is created, so an already open draft retains that allowance for its short confirmation window.
Changing rank affects new operations. Downgrading does not delete homes, orders or auctions already owned. Replacing an existing home remains allowed. Homes now uses explicit numeric overrides instead of always taking the maximum of the fallback and a permission. Its older permission-tiers list remains accepted for config compatibility; numeric permissions do not need to be listed there.
Install the updated JARs and restart, or use the supported product reload for configuration changes. Existing configs need no rewrite; missing new defaults are loaded internally. Configure Bounty's default by adding:
limits:
# -1 = unlimited; 0 = no new additions. Resets at midnight UTC.
daily-additions: -1
Other products retain their existing feature permissions; no arbitrary quotas were added to chat, teleports, viewing menus or claiming already earned rewards.