Technology

Technology adds generic placeable computers, seated laptops, addon modules, business kiosks, player mail, persistent online orders, ticket payment, stolen-card intrusion, dirty-funds withdrawal, and a handheld police MDT.

Required plugin order

Paper loads Core, Economy, Justice, Property, Lock, Vehicles, and WorldGuard before Technology. Oraxen and GSit are optional. Technology disables itself if any required service API is absent instead of starting in a partially connected state.

Technology items are registered through Core under the technology: namespace. Oraxen item IDs are tried first and every recipe has a vanilla fallback. Computer items contain only their generic item type; placed location, installed modules, kiosk binding, orders, mail, incidents, and access tokens live in the database.

Player workflows

• Place and right-click a computer to use it. Anyone who can physically reach it can use it.
• Sneak-right-click with a module to install it. Sneak-right-click empty-handed to remove modules. Both require WorldGuard build permission.
• Install a kiosk module and use /technology kiosk <business-account> while looking at the computer to restrict its store to that business. Use clear to return it to a normal computer.
• Use /technology business pool add <account> <world:property> to add a property to a business inventory pool. Online listings coexist with Economy chest shops, and orders remain open when stock is unavailable.
• Register a delivery chest with /technology deliverybox. Assigned delivery drivers receive a one-hour Lock USE bypass across the destination property only.
• Right-click a registered vehicle with an MDT to issue the configured parking ticket. The returned evidence link is one-use and valid for one hour.

Panel boundary

The Minecraft side is ready, but the mcskylines.net/panel website is intentionally a separate build. Technology creates cryptographically random, short-lived tokens, stores only their SHA-256 hashes, and exposes TechnologyApi.redeem as a single-use atomic redemption contract for the future trusted panel gateway. Evidence metadata is kept lightweight in-game; the panel will handle photo files and YouTube links.

Configuration and persistence

All player-facing text is MiniMessage in messages.yml. Gameplay values and Oraxen/fallback recipes are in config.yml. SQLite is the default; MySQL is supported. SQLite is backed up on startup with configurable retention. Database work is asynchronous, GUI holders are plugin-owned, and all top-inventory clicks and drags are cancelled before actions are consumed.

Computers and module lifecycle

Place a genuine desktop or laptop item, then right-click the placed computer to open its interface. Access is physical: anyone who can reach the machine can use its available applications. Use WorldGuard, Property, and Lock to control the location rather than assuming the computer itself has user accounts.

Sneak-right-click with a genuine module to install it. Sneak-right-click empty-handed to remove an installed module. Both changes require WorldGuard build permission at the computer. The item stores only its generic type; the placed machine, module slots, kiosk binding, and application data are authoritative in Technology's database.

Business kiosk and ordering workflow

1. Create or select the Economy business account that will own the store.
2. Add one or more world:property entries to its inventory pool with /technology business pool add.
3. Place a computer, install the kiosk module, target it, and bind it with /technology kiosk <business-account>.
4. Stock the configured business properties. Online listings coexist with physical Economy chest shops; one system does not replace the other.
5. Register a destination chest with /technology deliverybox before relying on delivery fulfillment.

Orders persist even when stock is currently unavailable. Delivery assignment gives the driver a one-hour, property-scoped Lock USE bypass for the destination, not ownership or management permission. Clearing a kiosk returns that computer to general use without deleting unrelated business records.

Mail and persistent orders

Mail and order records are stored server-side and survive restart. GUI ownership prevents clicks and drags from moving decorative application items. Database work is asynchronous, so a closing inventory or player logout cannot be treated as proof that an operation committed; use the resulting message/state on reopen.

Police MDT and ticket evidence

Hold the genuine handheld MDT and right-click a registered vehicle to issue the configured parking ticket. Justice and Vehicles supply the vehicle/citation behavior. The evidence link/token is single-use and expires after one hour. It carries lightweight metadata only; the future trusted web panel is responsible for media such as photos or YouTube links.

Stolen-card intrusion and dirty funds

Technology uses Economy's signed card serial state for intrusion attempts. A copied physical card does not create additional attempts because the opportunity is consumed server-side. Dirty-funds withdrawal and related incidents remain database/audit operations tied to the configured modules and integrated accounts; never use item names as proof of a valid card or device.

Panel boundary

The Minecraft plugin generates cryptographically random short-lived access tokens and stores only SHA-256 hashes. Redemption is single-use and atomic through TechnologyApi. The public website currently documents the system; it is not yet the trusted gateway that redeems those tokens. Do not paste tokens into chat, logs, documentation, or manual database tools.

Technology testing checklist

1. Start once with every required service present, then intentionally remove one on staging and confirm Technology disables instead of partially loading.
2. Place desktop and laptop items, test access, module install/removal, build denial, break/restart persistence, and invalid lookalike items.
3. Bind and clear a kiosk, add/remove business inventory properties, create an in-stock order and an out-of-stock persistent order.
4. Register a delivery box, assign a driver, and verify the Lock bypass is USE-only, property-scoped, and expires after one hour.
5. Issue a parking ticket with an MDT and test valid, reused, and expired evidence links.
6. Test one stolen-card attempt using duplicated copies of the same serial and confirm only one server-side opportunity exists.
7. Restart with open mail/orders/incidents and verify persistent recovery.
8. Exercise token redemption only through a trusted integration and confirm a second redemption fails.

Current boundaries

Technology requires the listed suite service APIs and intentionally refuses partial operation. Computer reachability is the access model; there is no separate in-computer login system. The website panel integration is a future trusted component, not an in-game token redemption screen today.