PhasmaStrap v2.19.3

Party

• You keep following your party after the first game. Asking first when you are already in a game meant every game after the first one, because somebody who had just been sent to the party's game still counted as busy and got a notification to click instead of being moved. Being in the game the party is in now counts as following, so only somebody off playing their own thing is asked
• Following a launch worked only while the background party process was running. Turning that off left the party unable to move you even with PhasmaStrap open. Any part of PhasmaStrap that is watching your party can move you now, and you are still only sent once

Note: this build is unsigned (this fork does not have access to the SignPath code-signing service the upstream Bloxstrap project uses), so Windows SmartScreen will likely flag it on first run. Click "More info" then "Run anyway" to proceed.

Requires the .NET 6 Desktop Runtime. If you don't already have it, install it before running PhasmaStrap.exe or clicking Play in the browser - if it's missing, launching straight from a browser link can fail silently instead of showing the usual "install the .NET Desktop Runtime?" prompt you'd get from double-clicking the exe directly.

PhasmaStrap v2.19.2

Games PhasmaStrap did not start

• A game started from the Roblox app or a browser link is now picked up, so activity, the overlay, Discord presence and your party still see what you are playing
• There is a toggle for it on the Integrations page, under activity tracking
• FastFlags and mods are not applied to a session PhasmaStrap did not launch, because Roblox only reads those when it starts. If a game has its own flag profile you get the usual offer to restart into the same server with it

Party

• Signing in updates the party page straight away instead of leaving the signed out card up until you navigate away
• Your party sees the name of the game you are in. It used to show "Place 123456" for the whole session, because where you are was recorded at the moment you joined, before the name had been fetched
• Following your party out of a game no longer opens the in game menu and no longer reports a crash afterwards. Asking the Roblox window to close is what opened that menu, and the kill that followed left no clean shutdown for the crash analyser to find

Crashes

• When Roblox refuses to let a program load into the game, the crash report now names it. That line is in Roblox's own log and needs no crash dump, which is why crashes caused by an overlay used to come back as "neither Roblox nor Windows wrote down why"
• Overlays from NVIDIA, AMD, Intel, Xbox Game Bar, Discord, Steam, OBS, MSI Afterburner and ReShade are recognised by name, and the report says plainly when the cause is not PhasmaStrap

Fixes

• Opening the editor from a screenshot notification and then closing it took the whole watcher down with it, which is what stopped the screenshot button, the tray icon and the overlay working until the next launch
• The watcher no longer throws while shutting down, from releasing a lock on a different thread than took it

Note: this build is unsigned (this fork does not have access to the SignPath code-signing service the upstream Bloxstrap project uses), so Windows SmartScreen will likely flag it on first run. Click "More info" then "Run anyway" to proceed.

Requires the .NET 6 Desktop Runtime. If you don't already have it, install it before running PhasmaStrap.exe or clicking Play in the browser - if it's missing, launching straight from a browser link can fail silently instead of showing the usual "install the .NET Desktop Runtime?" prompt you'd get from double-clicking the exe directly.

PhasmaStrap v2.19.1

Cursor fixes

• Your cursor picture is scaled to the size a cursor actually is. Roblox draws the texture at whatever size the file is, so a normal sized picture came out enormous. Pictures are now fitted to the size Roblox ships, keeping their proportions, and anything already smaller is left alone
• The cursor you chose is remembered when you close and reopen PhasmaStrap. It used to show nothing chosen on every start, even though Roblox still had your cursor
• The remove button works. It only appeared when PhasmaStrap thought a cursor was set, which after the bug above was never, so an applied cursor could not be taken off

Note: this build is unsigned (this fork does not have access to the SignPath code-signing service the upstream Bloxstrap project uses), so Windows SmartScreen will likely flag it on first run. Click "More info" then "Run anyway" to proceed.

Requires the .NET 6 Desktop Runtime. If you don't already have it, install it before running PhasmaStrap.exe or clicking Play in the browser - if it's missing, launching straight from a browser link can fail silently instead of showing the usual "install the .NET Desktop Runtime?" prompt you'd get from double-clicking the exe directly.

PhasmaStrap v2.19.0

Parties

• Invite people into a party and follow your leader into whatever they launch
• Join by six character code, or invite straight from your friends list
• See what every member is in, and whether they are in the same server as you
• Follow automatically, or get asked first when you are already in a game
• Runs in the background, so an invite still reaches you when PhasmaStrap is closed

Gallery

• Share screenshots from the Capture page
• Everything shared is looked at before it appears
• You are told when something you shared is approved, or taken down
• Crosshairs get a real preview instead of a broken image

Cursors

• Any picture becomes your cursor, whatever it is named
• PNG, JPG, BMP, GIF, TIFF and ICO all work, and anything that is not a PNG is converted to one
• Cursor packs still apply in one click

Developer tools

• The page is finished: FastFlag diff against Roblox defaults, live A/B toggle, proxy traffic log, log viewer, crash report bundler and the Studio plugin installer

Fixes

• Joining a friend checks where they actually are first, instead of sending you to a server they already left
• Background processes are named in Task Manager, and stay out of Alt+Tab and the taskbar
• PhasmaStrap no longer claims it is already running when Roblox is closed
• The driver frame rate limit is on the Rendering page again, and two pages no longer fight over it
• The frame rate limit hotkeys are gone
• Every link points at the renamed repository

Note: this build is unsigned (this fork does not have access to the SignPath code-signing service the upstream Bloxstrap project uses), so Windows SmartScreen will likely flag it on first run. Click "More info" then "Run anyway" to proceed.

Requires the .NET 6 Desktop Runtime. If you don't already have it, install it before running PhasmaStrap.exe or clicking Play in the browser - if it's missing, launching straight from a browser link can fail silently instead of showing the usual "install the .NET Desktop Runtime?" prompt you'd get from double-clicking the exe directly.

PhasmaStrap v2.18.0

• The settings window has been redesigned. Eight pages in the sidebar instead of a long list, with an "ON THIS PAGE" rail inside the bigger ones so settings are easier to find.
• Every notification can be turned off on its own, not just server join and leave. Each type now has its own colour and icon so you can tell what fired at a glance, and the Notifications page shows the full list.
• New server region notification: tells you which datacenter you landed in after joining, with the ping when it is known.
• Notification popups can be placed anywhere, with a corner, offsets and a width you choose. Several arriving at once now stack into one popup with a count and a Clear all.
• Cursor mods accept PNG, JPG, BMP, GIF, TIFF and ICO. Anything that is not already a PNG is converted, and a multi size ICO uses its largest frame.
• Fixed: the frame rate limit hotkeys did nothing. They used a driver setting id that does not exist, so every press was silently refused.
• Fixed: your accent colour was ignored by the section rail, the notification popups and a dozen other places, which stayed the default blue.
• Fixed: PhasmaStrap could stay running after Roblox was closed abruptly, which also left later sessions without a tray icon or overlay.

Note: this build is unsigned (this fork does not have access to the SignPath code-signing service the upstream Bloxstrap project uses), so Windows SmartScreen will likely flag it on first run. Click "More info" then "Run anyway" to proceed.

Requires the .NET 6 Desktop Runtime. If you don't already have it, install it before running PhasmaStrap.exe or clicking Play in the browser - if it's missing, launching straight from a browser link can fail silently instead of showing the usual "install the .NET Desktop Runtime?" prompt you'd get from double-clicking the exe directly.

PhasmaStrap v2.17.9

• Get help on Discord: the support links now point to the PhasmaStrap Discord server instead of GitHub issues.
• PhasmaStrap counts how often features are used (a clip saved, a preset shared or imported, low-end mode turned on) so the project knows what people actually use. Counts only, never what was in them, and all of it stops when you turn off "Enable sending of analytics".

Note: this build is unsigned (this fork does not have access to the SignPath code-signing service the upstream Bloxstrap project uses), so Windows SmartScreen will likely flag it on first run. Click "More info" then "Run anyway" to proceed.

Requires the .NET 6 Desktop Runtime. If you don't already have it, install it before running PhasmaStrap.exe or clicking Play in the browser - if it's missing, launching straight from a browser link can fail silently instead of showing the usual "install the .NET Desktop Runtime?" prompt you'd get from double-clicking the exe directly.

PhasmaStrap v2.17.8

• Statistics and crash reports now go to PhasmaStrap's own server instead of the upstream Bloxstrap project's. They are still anonymous, still off when you turn off "Enable sending of analytics", and the privacy page at phasmastrap.com/privacy says exactly what is sent.

Note: this build is unsigned (this fork does not have access to the SignPath code-signing service the upstream Bloxstrap project uses), so Windows SmartScreen will likely flag it on first run. Click "More info" then "Run anyway" to proceed.

Requires the .NET 6 Desktop Runtime. If you don't already have it, install it before running PhasmaStrap.exe or clicking Play in the browser - if it's missing, launching straight from a browser link can fail silently instead of showing the usual "install the .NET Desktop Runtime?" prompt you'd get from double-clicking the exe directly.

PhasmaStrap v2.17.7

• Updates and the News page now come from PhasmaStrap's own server (api.phasmastrap.com) instead of GitHub's, which only allows 60 requests an hour per IP address - with a few people on one network, update checks used to quietly fail. If the server is down, PhasmaStrap asks GitHub like before. Downloads still come from GitHub.

Note: this build is unsigned (this fork does not have access to the SignPath code-signing service the upstream Bloxstrap project uses), so Windows SmartScreen will likely flag it on first run. Click "More info" then "Run anyway" to proceed.

Requires the .NET 6 Desktop Runtime. If you don't already have it, install it before running PhasmaStrap.exe or clicking Play in the browser - if it's missing, launching straight from a browser link can fail silently instead of showing the usual "install the .NET Desktop Runtime?" prompt you'd get from double-clicking the exe directly.

PhasmaStrap v2.17.6

• Choose what double-clicking the tray icon does while Roblox is running (PhasmaStrap › Startup & updates): open settings (the default), bring Roblox to the front, open the tray menu, take a screenshot, save an instant replay, show server details, copy the invite link or clean RAM.

Note: this build is unsigned (this fork does not have access to the SignPath code-signing service the upstream Bloxstrap project uses), so Windows SmartScreen will likely flag it on first run. Click "More info" then "Run anyway" to proceed.

Requires the .NET 6 Desktop Runtime. If you don't already have it, install it before running PhasmaStrap.exe or clicking Play in the browser - if it's missing, launching straight from a browser link can fail silently instead of showing the usual "install the .NET Desktop Runtime?" prompt you'd get from double-clicking the exe directly.

PhasmaStrap v2.17.5

• Fixed: logs could miss their last lines when PhasmaStrap closed right after something happened (like an update), which made problems hard to track down.

Note: this build is unsigned (this fork does not have access to the SignPath code-signing service the upstream Bloxstrap project uses), so Windows SmartScreen will likely flag it on first run. Click "More info" then "Run anyway" to proceed.

Requires the .NET 6 Desktop Runtime. If you don't already have it, install it before running PhasmaStrap.exe or clicking Play in the browser - if it's missing, launching straight from a browser link can fail silently instead of showing the usual "install the .NET Desktop Runtime?" prompt you'd get from double-clicking the exe directly.