Wespner Game Panel for Visual Studio Code
Sign in with your Wespner Game Panel account, watch and drive your game servers' consoles, edit server files and startup
settings, and manage backups, databases, schedules and players directly in VS Code. Available in the same thirteen
languages as the panel, following VS Code's display language.
Install
In VS Code, open the Extensions view, search for Wespner Game Panel and click Install, or open the
extension's page in the
Visual Studio Marketplace. It needs
VS Code 1.95 or newer, and VS Code keeps it up to date.
For an editor that does not use the Visual Studio Marketplace, download the extension in the Wespner Game Panel:
open Account → Connected apps and click Download the extension in the Visual Studio Code card. Then
choose Extensions view → ⋯ → Install from VSIX… and pick the downloaded file. When a new version comes out,
download it from the same page again and install it the same way.
Sign in
Open the Wespner view in the Activity Bar and click Sign in. Your browser opens the panel's login and consent
page; after Approve access you are redirected back into VS Code. The redirect uses your editor's own URI scheme
(vscode://, vscode-insiders://, cursor://, …), and the panel accepts those schemes for its OAuth clients (by
default the ones of VS Code, VS Code Insiders, VSCodium, Cursor and Windsurf). Until you approve, a notification waits
for the browser. Cancel it to stop the sign-in, which otherwise gives up after five minutes.
The first sign-in brings two questions from VS Code itself:
- "Do you want Code to open the external website?" before your browser opens the panel. Choose Open, or
Configure Trusted Domains to trust the panel's address for good. If you cancel it, the sign-in stops with
"Sign-in failed: Sign-in needs the panel's page in your browser. Allow VS Code to open it, then try again."
- "Allow 'Wespner Game Panel' extension to open this URI?" when the browser hands the sign-in back to VS Code.
Tick Do not ask me again for this extension and choose Open, so later sign-ins come straight back.
The extension never sees your password — it holds an OAuth token stored in VS Code's secret storage, refreshed
automatically, and listed in the panel under Account → Connected apps with your editor's name, where you can
disconnect it at any time. Sign out from the view's title bar revokes it too.
What you can do
- Servers — every server you own or are a subuser of, with its live state (running, offline, starting, stopping,
installing, installation failed, suspended, transferring, restoring a backup, node under maintenance). The power
state is checked every 20 seconds or so while the view is visible and follows an open console at once. Refresh
Servers in the view's title bar reloads the list and checks every state again at once; the last known states
stay while it loads. Start, stop, restart and kill from the context menu (kill asks first), send a single console
command, or open the server in the panel. A running server also shows how many players are on it ("Running · 3 / 20
players", and "Players: 3 of 20" on hover), for every game the panel counts, checked every 30 seconds while the view
is visible.
- Backups — expand a server for its Backups section, the panel's Backups page in the tree: every backup with
its size and age, a spinner while it is being created, and how many of the backups your plan allows are in use
("2 of 5"). Hover a backup for its times, size, checksum and ignored files. Create Backup… on the section asks
for an optional name, the files and folders to leave out and, if you may unlock it again, whether to lock it. On a
backup, Download… saves it where you choose, with progress and Cancel; Restore… brings the server's files
back to that backup, optionally deleting all files first; Lock protects it from deletion; Unlock… and
Delete… ask first. A backup being created and a restore you started refresh themselves while you watch, and a
notification says when a backup is ready or failed and when a restore has finished. What you see and may do
follows your panel permissions.
- Databases — expand a server for its Databases section, the panel's Databases page in the tree: every
database with its endpoint (
host:port) and its storage use, and how many of the databases your plan allows are in
use ("1 of 2"). A database turns yellow, then red, as it nears its storage limit, and shows a lock once it is full.
Hover a database for its endpoint, user, allowed connection sources and storage. Create Database… on the
section asks for a name and for where connections may come from (leave it empty to allow any address). The name
may use the letters A–Z without accents, digits, _ and -, at least 3 characters; the panel puts s<id>_ in
front of it (the prompt shows yours), and the two together may have at most 48 characters. On a database,
Copy… puts its endpoint, user, password, JDBC string or mysql command on the clipboard; Rotate Password…
gives it a new password after warning that applications using the old one stop connecting; Delete… first shows
what happens to its backups (they are kept under Backups of deleted databases while they fit within that group's
limit, and the dialog names any older unlocked backups deleted to make room, or says why the database cannot be
deleted right now), then removes it once you type its full name, s<id>_ included. A new or rotated password is
offered once, in the notification's Copy Password, and Copy… fetches it from the panel only when you pick it:
the extension never stores a password. Expand a database for its backups, newest first. Back Up… on the database
asks for an optional name and, if you may unlock it again, whether to lock the backup. On a backup, Download…
saves it as a .sql.gz file, with progress and Cancel; Restore… overwrites the database with it, and Wipe the
database and restore empties the database first (otherwise the tables the backup does not contain are kept);
Lock, Unlock… and Delete… work as for file backups. A backup being made and a restore you started refresh
themselves while you watch, and a notification says when a backup is ready or failed, with the reason, and whether a
restore worked; a backup whose last restore failed says so, with the reason on hover. The last row of the section,
Backups of deleted databases ("3 of 15": the backups it holds of its limit), keeps the backups of deleted
databases, one row per deleted database, and is shown while it holds a backup. Restore as New Database… on such a
backup asks for the new database's name and allowed connection sources, both filled in from the deleted database, and
restores the backup into a new database, which takes a slot of your plan's database limit; Download…, Lock,
Unlock… and Delete… work as on other backups. When they no longer fit within the limit after another database
is deleted, the oldest unlocked ones are deleted. What you see and may do follows your panel permissions.
- Schedules — expand a server for its Schedules section, the panel's Schedules page in the tree: every
schedule with its cron expression (minute, hour, day of month, month and day of week, for example
0 4 * * *)
and, while it is active, when it runs next ("next: in 3 hours"). A clock marks an active schedule, a grey sign an
inactive one, and a spinner one that is running. Hover a schedule for its next and last run, whether it runs only
while the server is running, and its number of steps. The cron expression and the times are on the panel's clock,
not yours: the tooltip names its UTC offset ("Times are in the panel's time zone (UTC+02:00)."), which follows
summer time. Create Schedule… on the section asks for a name; when it runs, every 5 minutes, every hour, every
day at midnight or at 04:00, every Monday at midnight, or Custom… for your own five fields, checked as you type;
whether it runs only while the server is running; and whether it is active. On a schedule, Run Now runs it at
once (when it has steps and is not running already), Edit… changes its name, its time or whether it runs only
while the server is running, Activate and Deactivate switch it on and off, and Delete… removes it with
its steps. Expand a schedule for its steps, in their order ("2. Power action: Restart the server"), each with the
seconds it waits after the step before it ("+30 s") and whether the steps after it still run when it fails.
New Step… on a schedule adds a console command, a power action, a backup (with the files and folders to leave
out, separated by commas) or a backup of one or all databases, then asks how long to wait after the step before it
(0 to 900 seconds, not asked for the first step unless it already waits) and whether the steps after it still run when
it fails. On a step, Edit… asks the same questions, filled in, and Move Up, Move Down and Delete… do
what they say. New Step… is offered until a schedule has 10 steps. A schedule that is running refreshes itself
while you watch; if one keeps showing "Running…" (see Troubleshooting), Deactivate it and Activate it again
(an inactive one: Activate, then Deactivate). What you see and may do follows your panel permissions: New
Step… offers only the actions you may use, no backup steps when your plan includes no backups, and no database backup
step when the panel has database backups switched off.
- Players — expand a Minecraft server for its Players section, the panel's Players page in the tree. The section
row reads how many play ("3 / 20 players"), "Offline" while the game is not running, or "Proxy server". Its groups are
Online (who plays now, with a green icon), Operators, Whitelist (whether it is on, and how many it holds:
"on · 2") and Bans (the banned players with their reason, then the banned IP addresses: "1 player, 2 IPs"). Each
player's row names what its group does not say ("online", "operator", "whitelisted", "banned"). A game that counts
more players than it names (some name only a few of them, and a server can hide them all) ends Online with how many it
does not name ("2 not named by the game"). Hover a player for their UUID and their ban (the reason, who banned them
and when) and, a moment later, their game mode, world, position, XP level, time played, deaths, player kills and time
since their last death. While the game is not running, Online says so, and the other groups, read from the server's
files, still show. The section refreshes itself every 15 seconds while it is open, every 30 seconds while the panel
cannot read one of its lists. Right-click a player for Kick…, Ban… and Ban IP… (each asks for a reason of
3 to 255 characters; Kick… and Ban IP… only while the player is online), Unban, Make Operator… (after the
panel's warning), Remove Operator, Add to Whitelist, Remove from Whitelist, Copy Name and Copy
UUID. The + on Operators, Whitelist and Bans (Add Operator…, Add to Whitelist…, Ban Player…) asks
for a Java player name (letters, digits and
_, up to 16) or a UUID with its dashes, looks the player up with the
panel, then goes on as on a player row. On Bans, Ban IP Address… bans an IPv4 or IPv6 address, with an optional
reason, and Unban IP on a banned address lifts the ban; on Whitelist, Enable Whitelist and Disable
Whitelist switch it on and off. Find Player… (the magnifier on the section) lists up to 50 of the players the
panel knows, the last seen first ("Last seen 5 minutes ago"), and anyone else as you type; a name, or a UUID with its
dashes, that never joined can be looked up from the last item (Look up "Steve"…), so you can whitelist or ban a player
before they first join. Pick a player for Show Details or for the actions their row would offer. Every request
names a player by their UUID whenever the panel knows it, never by what you typed. On a proxy server the section shows
only the panel's notice (see Troubleshooting), and refreshes only when you refresh it. What you see and may do follows
your panel permissions.
- Startup — expand a server for its Startup section, the panel's Startup page in the tree: the startup
command with its variables filled in (Copy puts it on the clipboard), the Docker image (Change Docker
Image… picks another of the egg's images) and the egg's variables (click one, or Edit…: a pick of the
allowed values, Yes / No, or a box that checks the egg's rules before the panel does and shows the panel's answer in
place). A change takes effect the next time the server starts. What you see and may change follows your panel
permissions, a read-only variable carries a lock, and when a server is installing, suspended, transferring,
restoring a backup or on a node under maintenance, or its installation failed, the section says so instead.
Refresh on the section loads it again (on such a server it first checks whether the server is back), and
Collapse All in the view's title bar folds every server.
- Console — Open Console shows a live terminal per server: output as it happens, a command line with history
(↑ / ↓), power buttons and CPU / memory / disk / uptime. Uses the same websocket as the panel; what you may do
follows your panel permissions.
Console tabs come back after a window reload and connect again by themselves; in a window that starts signed out a
tab says "Sign in to Wespner Game Panel to continue." and connects once you sign in. The power buttons and the
command line are named for screen readers.
- Files — Open Server Files adds the server as a workspace folder (
wespner://<server id>/). With a folder
already open you choose between this window, which becomes a multi-root workspace and reloads, and a new window.
Browse, open, edit, save, create, rename and delete with VS Code's own Explorer and editor. Files above 4 MiB are
transferred through the server's node directly, so large configs and logs open and save too (the node's upload
limit, 100 MB by default, applies on save). The 4 MiB threshold is only an optimisation: when the panel still
refuses a file as too large, the extension falls back to the node automatically.
Right-click files or folders and choose Compress… to pack them into a .tar.gz on the server; right-click an
archive for Extract Here (overwrites files of the same name, after asking) or Extract to Folder (a new
folder named after the archive). Both run on the server, so nothing is downloaded.
Settings
Both are user settings: they apply to every window, not per workspace.
| Setting |
Default |
Meaning |
wespner.panelUrl |
https://game.wespner.eu |
The panel to sign in to. After a change VS Code asks you to reload the window. Each panel keeps its own sign-in. |
wespner.files.panelTransferLimitBytes |
4194304 |
Files above this size bypass the panel and go through the node. Matches the panel's own limit for editing files (4 MiB). |
Remote development
In a remote window (Remote SSH, WSL, Dev Containers) the extension runs on the remote side, next to your workspace, so
that machine must be able to reach the panel and your servers' nodes. The browser still opens on your own computer:
the redirect comes back through VS Code's URI handler on your local machine and is forwarded to the remote extension
host. VS Code for the Web (vscode.dev) cannot run the extension.
A backup you download in a remote window is handed to your browser, so it lands on your own computer, not on the
remote machine. VS Code may ask before it opens the link: allow it, or the download does not start.
Note: sign-in in remote windows has not been tested yet. If it does not complete there, open a
support ticket with the log from the output channel (see below).
Troubleshooting
- "Sign in to see your servers." after changing
wespner.panelUrl. Each panel has its own sign-in. Reload the
window when VS Code offers it, then sign in to the new panel.
- "The panel could not be reached." This computer got no answer from the panel at all. Check your internet
connection, a VPN or proxy, and the address in
wespner.panelUrl. The log (see below) names the reason, for example
a name that does not resolve or a refused connection.
- "Use only the letters A to Z without accents, digits, underscores and dashes." when you create a database. Use the
letters A–Z without accents, digits,
_ and -, at least 3 characters: a database with any other character in its
name could not be backed up, so the extension does not create it. The panel puts s<id>_ in front of the name (the
prompt shows yours, for example s12_), and the two together may have at most 48 characters, so the longest name you
may type is 48 minus the length of that prefix.
- "The cron data provided does not evaluate to a valid expression." when you create a schedule or change when it
runs. The expression has five fields, but the panel cannot read one of its values, for example a minute above 59,
an hour above 23, a day of the month of 0 or above 31, a month of 0 or above 12, a day of the week above 7, a step
of
*/0 or a name it does not know. The panel words this message itself, in English. Correct the value and try
again: in Edit… → When the box keeps what you typed. An expression the panel could never read, such as four
fields, ? in both day fields or L in the hour, is refused in the box before anything is sent, with the reason
in your language.
- A schedule keeps showing "Running…" long after its steps should have finished. The panel can lose track of a run,
for example when a step is deleted while its schedule runs, and then leaves that schedule alone. Right-click it,
choose Deactivate, then Activate (an inactive one: Activate, then Deactivate): the run counts as
ended, and an active schedule runs at its next time again. While it shows "Running…", Run Now is not offered.
- "The server must be online and the player connected for this action." when you kick a player or ban their IP
address. The player left in the seconds since the Players section last read who is online (the panel checks that every
10 seconds or so). The panel words this message itself, in English. The section refreshes at once, without that
player, and nothing is done to anyone else. If the player is back, try again.
- The Players section shows only "This is a proxy server — player management runs on the backend servers behind it."
The server is a proxy, such as Velocity or BungeeCord: players join through it, but their operators, whitelist and
bans are kept on the servers behind it, so manage them in those servers' Players sections. A proxy offers no player
action and no Find Player…. If the server is not a proxy, a
velocity.toml or a config.yml in its root folder makes
the panel take it for one: open a support ticket.
- "Player not found." when you add a player by name or look one up in Find Player…. On a server in online mode
the panel checks the name with Mojang, and a name that no Minecraft account has is not found. Check the spelling, or
enter the player's UUID, with its dashes, instead. A Bedrock player who joins through Geyser has a name the box does
not take (it starts with a prefix such as
.): find them in the Online group or with Find Player… once they have
joined.
- "This server is in offline mode: any name is accepted." in the box where you type a player's name. The server does
not check names with Mojang (
online-mode=false in server.properties), so the panel takes any name and gives it the
UUID the game would: a typo makes a new player, so check the spelling. A name with a space or console syntax, such as
@a, is still refused in the box.
- Every action asks you to sign in although the view shows you signed in. Use Sign out in the view's title
bar, then Sign in again. Signing in from the error message reuses the stored token, signing out drops it, so
the next sign-in gets a new one.
- "The panel is rate limiting requests. Try again in … s." The panel limits how many requests an account may make
per minute. Wait the time shown, then try again. The servers view paces its own checks to stay under that limit,
and a server whose check fails keeps its last known state.
- The panel says two-factor authentication is required. Click Open Panel, set up two-factor authentication
on your account, then try again.
- Logs: View → Output, then pick Wespner Game Panel in the list. It shows the panel in use and what failed,
with the reason and a timestamp: the checks in the background (server states, the server list), the actions you
ran and the sign-in. Attach it when you open a support ticket.
Licence
This extension is proprietary software for customers of the Wespner Game Panel; see the LICENSE file shipped with the extension. The open-source components bundled into it (xterm.js, its fit addon and ws) are listed with their MIT notices in the THIRD_PARTY_NOTICES.md file next to it.
| |