Depot service lines

What the shelves hold and what leaves the floor

Hybird Game Limited licenses sprite sheets, tile packs and sound kits from the Stanley Street depot at Rm C 7/F World Trust Tower, 50 Stanley St, Central, Hong Kong - 999077, Hong Kong (HK). Six service lines cover a run from the first brief to the sealed release archive. Every line has its own intake rules, its own checks and its own written output, and every line is booked through the same inbox at general@meiyuelmaterials.buzz or by phone on +14355588049.

Sprite Sheet Bays

A sprite sheet bay takes a character, effect or prop set and slices it into an atlas that the target engine can import without manual repair. The bay works from a rig profile supplied by the client, which declares frame size, pivot placement, padding and the palette depth the project already uses. Sheets are delivered as packed atlases with a companion data file naming each animation, its frame count and its loop flag. Where a project has unusual requirements, such as directional eight way sheets or large boss frames that must share one texture page, the bay documents the compromise rather than hiding it.

The bay also handles re-slicing for platform ports. When a title moves from one engine to another, the art usually survives intact but the packing does not, and the bay can rebuild the atlas against the new frame rules while keeping every animation name stable. Client teams receive the finished sheet, the data file and a short note listing any frame that required redrawing to satisfy padding rules. Nothing leaves the bay without passing an import test on the target engine version recorded in the brief.

Tile Pack Runs

A tile pack run assembles terrain sets that close at the seam width declared in the brief. Floors, walls, slopes, edges and decorative overlays are produced as one coordinated pack so that the palette never drifts between variants. Packs ship with autotile masks for the common engines, which means the level designer can paint a corridor and get corners automatically rather than placing each edge by hand. Each run also includes a small demonstration map that proves the set works as a whole.

Runs are scoped by count rather than by hours, so a client knows up front how many tiles will arrive and what categories they cover. Where a project needs a new biome beyond the original scope, the depot quotes a second run rather than stretching the first one thin. Tile packs from the Stanley Street depot are licensed for the terms recorded in the accompanying license note, and the pack file always carries the same internal naming pattern so that assets from different runs can coexist in one project folder without collisions.

Sound Kit Desks

A sound kit desk curates audio into a single consistent set. Every clip is trimmed to remove silence at the head and tail, normalised to the loudness target named in the brief, and looped with a verified sample accurate loop point where a loop is required. The kit arrives with a cue sheet listing each file, its duration, its loop status and the intended gameplay moment, which saves the audio programmer from guessing which click belongs to which menu.

The desk does not compose original music, and it says so plainly. It works with existing recordings, whether supplied by the client or drawn from a cleared set of source recordings, and its value is in consistency and documentation rather than authorship. Kits are tested in the target engine so that compression artefacts and loop gaps are caught at the depot rather than in the first playtest. Format options include the common compressed and uncompressed containers, and the desk will state which format best suits the platform in the brief.

License Renewal Windows

A license renewal window is a scheduled review of an existing grant before it lapses. The depot keeps a record of every license it has issued, and when a window opens the client receives a written summary of the current terms, the renewal terms and any change in permitted use. Renewals are handled in writing so that the record stays complete, and the updated terms are attached to the client account rather than sent as a loose message.

Windows are opened early enough that a production schedule is never interrupted by paperwork. A typical window opens several weeks before expiry, which gives the client time to confirm scope, adjust territory or add a platform. If a client chooses not to renew, the depot records that decision and states clearly what the client may and may not continue to do with the existing assets. That clarity is part of the service, because an expired grant that nobody noticed is far more expensive than an honest renewal conversation held in good time.

Compatibility Reviews

A compatibility review loads a finished batch into the engine version named in the brief and reports what actually happens. The reviewer checks import faults, texture page overflow, memory spikes during scene load, frame rule breaks and any mismatch between the data file and the delivered sheet. Findings are returned as a short written report with the severity of each issue and a proposed fix, and the fixes are applied at the depot where they fall within scope.

Reviews are the step that stops a batch from embarrassing a client in front of a publisher. They are also the step most often skipped by teams under time pressure, which is why the depot treats a review as a mandatory part of a run rather than an optional extra. The report is written for a producer as much as for an engineer, so it states what the issue means in production terms alongside the technical detail. A batch that passes review is signed off with the engine version and build number recorded in the client file.

Bundle Release Sittings

A bundle release sitting assembles the final package. The manifest lists every file with its checksum, the credits file names every contributor, and the license record states the grant, the term, the territory and the permitted uses in plain language that a publisher can read without a lawyer present. The sitting closes only when the archive verifies clean against the manifest, which means no file is missing and no file has changed since it was listed.

Sittings are scheduled near the end of a run and they usually take less than a day, but they matter more than their length suggests. A bundle that ships without a coherent record creates a quiet liability that surfaces months later during due diligence or a platform review. The depot therefore treats the sitting as a formal step with a named closer, a verification pass and a written hand over note. Clients leave with the archive, the manifest, the credits file and the license record together in one place.

How a service run is scheduled

Brief by email. Send the project name, target engine, content needs and the date the assets must be in the build to general@meiyuelmaterials.buzz.
Scope and window. The depot replies with a written scope, the bay assigned to the run and a delivery window measured in working days.
Production. Sheets, packs and kits are produced against the rig profile or tile width declared in the brief, with progress notes at each stage boundary.
Review. The batch is loaded into the target engine and a short report records every finding and the fix applied.
Release sitting. The archive is assembled with manifest, credits and license record, then verified clean before hand over.
Account record. The run is logged against the client account so that renewal windows can open on time without anyone relying on memory.

Book a bay or ask a scope question through the contact page