SWIFTPOINT//HUB
Support

Profile Builder · Quickstart — your first profile in ~5 minutes

A working z3 profile from zero to a downloaded .spcf file in five minutes — the fastest possible first run.

This walkthrough gets a working profile from zero to a downloaded .spcf file as fast as possible. If you want details on the individual parts, each step links to the matching guide.


1. Open the Builder

Go to Swiftpoint Hub → Profile Builder (or the /editor page).

You start with an empty "blank template". The editor automatically creates one group named New Profile and fills it with sane device defaults:

  • DPI 800 × 800
  • Polling rate 1000 Hz
  • Lift‑off 2 mm
  • Game device off (plain mouse mode)
  • LED off, OLED profile mode
  • Auto‑release enabled, Tilt auto‑zero enabled
You don't need to understand any of those yet

They're sensible defaults you can change later in the Settings view.


2. Pick a button to bind

Look at the Mouse view (the default tab). This is the button map of the Z3. Each card is a real physical input:

  • Wheel Pull / Push / Press
  • Left / Right / Middle button
  • Top Thumb / Bottom Thumb
  • Left / Right Fingertip
  • Left/Right Trigger Push / Pull
  • Rear Edge / Front Edge

Click a button — for example Left Button. The right‑hand panel opens and shows the Press stages for that button plus an Add a binding section.


3. Create your first binding

  1. Below the press‑stages card, choose a Trigger type from the dropdown (default Button press = the light press) and click Create binding.
  2. The binding appears on the right with an On activation list and an + Add action button.
  3. Click + Add action. Pick a Kind — for a first test choose Key press — select a key (e.g. V) and the action tap. Confirm with Add action.

The card on the Mouse view now shows the key next to the button, and the bindings list in the Bindings tab shows the full text, something like:

Left Button → Press Key V [tap]

That's a binding. Do the same for a couple more buttons (Right Button, Top Thumb, trigger Pull) to see how the map fills up.


4. Give the profile a name and save it

  1. In the header, click Save (labelled Save / publish profile for a new profile). A small Publish window opens.
  2. Fill in Title (required, e.g. My CS2 Setup), an optional Game (e.g. CS2) and a short Description.
  3. Click Publish.

The profile is now live on the hub at its own URL. Need a local copy instead? Use Download in the header — it writes a .spcf file right away.


5. What just happened (the mental model)

  • Profile — the whole file, your title/game/description live on it.
  • Group — the single New Profile group inside it, holding all bindings. You can later add more groups and sub‑profiles for layers.
  • Mapping — one button + trigger + actions combo (your Left → V).

Everything from here on is just combinations of these three ideas:

Want to… Guide
Add a deep press that only fires halfway down deep-click.md
Make a gesture with the mouse tilt tilt-and-pivot.md
Make one binding live only while another is held nesting.md
Put something on the OLED screen oled-actions.md
Set DPI / polling / lift‑off settings-and-dpi.md
See every trigger & action available bindings.md
Understand the whole interface interface.md

Shortcuts you'll use constantly

Keys Action
Ctrl+S Save / publish
Ctrl+Z · Ctrl+Shift+Z / Ctrl+Y Undo · Redo
Ctrl+Shift+D Duplicate the selected binding
Delete / Backspace Remove the selected binding (outside text fields)
Ctrl+/ Show/hide the shortcut help overlay

FAQ — first minutes

"Do I need an account to build profiles?" No. Everything except publishing to the hub works offline. You can create, edit and Download .spcf files without logging in.

"Can I open a file I got from a friend?" Yes — drag & drop it onto the page, or use Open… in the header. It's parsed and fully editable. If something in the file is invalid, the Builder tells you why before it makes any changes.

"Can I load one of my hub profiles back for editing?" Yes. Type the profile #ID into the small # field in the header and hit Load, or open the page as /editor?id=<ID>.

"Undo only goes back so far — why?" The Builder keeps the last 50 document snapshots. Big edits (like many range‑plot drags) reuse one snapshot per drag.