Bambu Studio can make an assembly guide. Here’s why your multipart print still needs a real manual.

Bambu’s own wiki is clear about the goal: multipart prints fail when creators do not leave instructions, so Studio helps you rebuild the assembly sequence from STEP/STP or from existing MakerWorld 3MFs. It can suggest steps, camera angles, explode frames, snap-fit labels, and text callouts, then export PDF, Markdown, or MP4.

Treat that as a win. For decorative or snap-fit models with no bag of fasteners, a Studio guide plus a MakerWorld listing may be enough.

The gap shows up on functional machines: the slicer knows printed bodies; it does not own your hardware list, your reprint notes, or a public URL that stays current when geometry moves.

Which vitamins are in your hand on this step — M3×12 SHCS, a Dash 016 o-ring, a 4.57×0.36×15.88 spring?

How many of each do you order once, rolled up into a shopping list?

What walls, infill, and material does this STL need so the next builder is not guessing from a Reddit comment?

When you revise a part next week, do people still open a stale PDF, or does the same URL show the new figure?

If those answers live outside the export — in a spreadsheet, a Discord pin, or your head — builders will miss them. That is the instruction layer Slicebuild is built for.

Keep the same discipline Prusa-style kit manuals get right, without pretending a 40-page PDF is the product:

One action per step. “Assemble the plunger” is a chapter. “Drive the M3×30 through Plunger Head B into the rod” is a step.

Hardware on the step that uses it. Quantities should roll into a bill of materials on the public page.

Print notes on the STL — walls, infill, material, orientation — not only in a forum thread.

A figure that can move. When a bracket revises, restage the step instead of reshooting a photo set or regenerating a PDF nobody re-downloads.

Publish when the first real step can stand alone. Drafts stay private; the public page is what search engines and builders both read.

Printables and MakerWorld are strong at hosting files. Bambu Studio is getting strong at illustrating how printed parts click together. Neither replaces a revisioned project record: title, summary, printed parts, vitamins, and a step list that knows which screw belongs where.

That is why so many “complete” releases still stall on someone’s bench. The STLs downloaded fine. The missing M3 length, the wrong o-ring dash size, or the outdated plate note did not.

If you already have the files, the work left is the instruction layer — not another zip named final_final_v3.

Sillybutts’ Wildstyle on Slicebuild is the kind of project a slicer guide alone under-serves. Steps call out Dash-series o-rings with metric sizes, compression springs with OD × wire × free length, and specific SHCS lengths on the step that uses them. The figure is a restageable 3D view. The public page rolls the hardware into one list.

You can still design in CAD and still publish STLs wherever your audience already is. The Slicebuild URL is the manual people follow when they are holding a bag of fasteners.

Create a free account, start a project, and drop the STLs. Write one action per step. Attach the hardware that step uses — screws, inserts, bearings, o-rings, springs — with exact sizes so the bill of materials writes itself. Capture a 3D figure for the step. Publish when the first step is real.

Builders open the public page and start the guide without an account. When a part revises, you restage in Studio; the same URL updates instead of shipping a new PDF.

The longer walkthrough is on How it works. The short version: if Bambu gave you the explode, Slicebuild is where the vitamins and the living manual live.