Every version
What changed
Phasma updates itself, so you are normally on the newest one already. This is what was different about each.
3.6.30
NewestFixed
- Changing a hotkey did nothing. Every hotkey can be changed again.
Buy Phasma to download it. Only the newest version can be downloaded.
3.6.29
Fixed
- Phasma Free kept asking to update, even right after updating.
3.6.28
Added
- RDPs work as a set: open them all at once on Farming, RDPs, and each account you launch goes into the first free one.
- Main account option, so your own account always opens on your desktop and never in an RDP.
- Choose whether an RDP that closes by itself opens again or stays closed until you open it.
Fixed
- Phasma Pro was flagged by several antivirus programs.
3.6.27
Fixed
- Minimizing an RDP session minimizes the game inside it again, and it comes back without going black.
- Rejoining in an RDP session closed the game and never opened it again.
3.6.26
Fixed
- RDP sessions no longer go black on restore: the game inside stays visible and is never minimized with the window.
3.6.25
Fixed
- An RDP session's Remote Desktop window could come back black and stuck after being minimized.
3.6.24
Fixed
- CPU temperature could show an impossible number on some PCs. It now only shows once it's confirmed real.
3.6.23
Added
- CPU and GPU temperature on the PC page in the remote.
- In an RDP session, choose which accounts only hide their game when minimizing, and which never minimize at all.
Changed
- Tapping in the remote moves the cursor there first instead of jumping straight to it.
- RDP sessions use less data.
Fixed
- Accounts sometimes showed empty right after opening the app.
- A sequence with more than one window could get stuck on the first one.
- Unminimizing a game in an RDP session now brings it back fullscreen instead of windowed.
- Windows could flip back and forth between virtual desktops on their own.
- Memory trim happens the moment it's needed instead of a short delay later.
3.6.22
3.6.21
Added
- Number boxes take any number you type.
- Share outputs and sequences with a short code. Basic can make 3 a day. Pro has no limit and can share playbooks too.
- The overlay can show the key that turns an output on.
- New RDP farm system for Pro. Each account runs in its own Remote Desktop, so you can farm with many Roblox at once.
- Choose what opens Roblox: normal Roblox or a bootstrapper you have installed.
Changed
- Big performance boost: smoother pages, less CPU use and fewer freezes.
- Rejoining many accounts at once is steadier.
Fixed
- A crash when marking all as read or clearing a lot of notifications.
- Quitting during a sequence no longer crashes.
3.6.20
Added
- Sign out sessions, on the Accounts page and in an account's Windows session section, signs every session out.
Changed
- A session window or Roblox you close yourself stays closed.
3.6.19
Fixed
- Windows no longer asks to verify the publisher every time a session window opens. Press Repair on an account once.
3.6.18
Added
- Run every account in its own Windows session, so the one copy limit no longer applies. There is a step by step guide under Help.
- Set the frame rate cap, graphics level and priority for each account.
- Farming lists the games running in sessions.
- Tile, Minimize all and Restore all work on session windows too. Tile can use a separate Windows desktop and can be set to clients, sessions or both.
- Keep active lets you pick the key, how many presses, how long to hold and the gap, and choose clients, sessions or both.
Changed
- Accounts refresh who is online every 5 seconds while the page is open.
- Removed "Skip the client I'm playing on" from Keep active.
Fixed
- A Roblox you open yourself is no longer limited by an account's frame rate and graphics level.
- An account that is not running no longer shows as playing.
3.6.17
Added
- Phasma Free, a free edition with the basics: make outputs and click, with a little humanizing. Nothing to sign in to.
Changed
- Smaller, tidier builds.
3.6.16
Changed
- Under the hood improvements to performance and reliability.
3.6.15
Fixed
- Phasma stops rewriting a Windows scheduled job over and over while you farm. It was doing it every time anything was saved, which on a busy farm is every few seconds, and each one started three programs. That is where the handles and the memory were going.
- A cascade actually cascades. With a lot of clients it was spreading them across the whole screen and squashing them, because it stepped once per client and shrank them to make the whole run fit. They are one size now, a title bar apart, and the pile starts again at the top rather than walking off the edge.
- Opening a client no longer drags every minimised client back onto the screen. Arranging has to do something with a minimised window, and when you press Tile yourself bringing it back is right. When it happens on its own it is not, and it was happening every time anything rejoined.
- Clients are arranged again after maintenance, if you have tiling set to do that. It brings every client to the front and restores the minimised ones, so it was the thing most likely to have scattered them, and the only one that never triggered a tidy up. Clients that were minimised stay minimised.
- The installer no longer asks for administrator. It never needed it, and it is sharper on a scaled screen.
3.6.14
Warning
- Roblox is banning accounts for running several clients at once. Multi-Instance is still there and still works, but it is your risk now.
- Multi-Instance starts off on a new install because of that. If you already had it on it stays on, and it is under Settings, Farming either way.
Fixed
- Sequences no longer fill up with steps you did not record. Recording was on Ctrl R, which is also reload in a browser, and Phasma watches for hotkeys everywhere rather than only in its own window.
- Recording is unbound now, and it is let go of once for anybody who still has it on Ctrl R. Give it a key of your own under Settings, Hotkeys.
- The recording hotkey stops whatever is being recorded, instead of starting a second recording on whichever sequence you have since selected.
- The bench stopped leaving a picture behind for every client that closes.
Added
- A hotkey for stopping a recording, which works whatever is selected. Unbound to begin with.
3.6.13
Fixed
- A client rejoining no longer closes your other clients.
3.6.12
Fixed
- Opening several Roblox clients works again.
- Closing Phasma no longer closes your clients.
- The remote opens accounts where you picked: a place, a private link, or somebody to follow. Pick which one under the box.
- A saved setup on the remote opens what it was saved for.
Added
- Multi-Instance can be turned off in Settings, Farming.
3.6.11
Fixed
- Opening several Roblox clients: the launch now does exactly what 3.6.2 did, which is the last version it worked in. 3.6.3 made three changes around it and all three are undone. If it still does not work, what is left is one change from that version and this narrows it to that.
3.6.10
Changed
- A launch writes down what it actually did: how many accounts were asked for, whether Roblox's single instance guard was really held at that moment, how many clients were already open, and whether each ask made the number go up. A launch Roblox quietly folds into a client already running looks exactly like one that never happened, and only the count tells them apart.
3.6.9
Fixed
- Opening several Roblox clients works again. It has been broken since 3.6.3 and the cause was a fix in that version: Phasma started holding the name Roblox checks for another copy from the moment it opened, rather than at the moment of launching. Held before any client is running, the first launch finds that name already taken and waits for a client that is not there, so nothing opens. It is taken at launch now, which is what 3.6.2 did and what worked. A rejoin is still covered, because a rejoin launches through the same place.
3.6.8
Added
- A switch for running several Roblox clients at once, under Settings, Farming. Phasma holds the name Roblox checks to decide whether another copy is already open, which is what stops a new client closing the ones you already have. It was always held and there was no way to say otherwise, so turning it off now actually turns it off, from the very next launch rather than after a restart.
3.6.7
Fixed
- Run and stop on the remote's sequences page work. The buttons had been there since the page was rebuilt with nothing listening for them, so pressing one did nothing at all and said nothing either. The same was true of everything on the PC page: freeing memory, running maintenance, hiding the clients and restarting Phasma. Switching a profile too.
- A fresh Phasma no longer fills itself with outputs you did not make, and deleting them no longer brings them back. Phasma carries an older Phasma's outputs and sequences across the first time it opens, which is right, but it worked out whether it had already done that by asking whether there were any outputs. Delete the ones it gave you and the answer became no, so it gave them to you again, and again, for as long as you kept deleting them.
- Anything the remote asks for that Phasma turns down now says so on the phone. The reason was only ever shown on the PC, which is the one place nobody is looking.
3.6.6
Fixed
- Restarting Phasma no longer closes the clients that were running. Phasma holds the name Roblox uses to decide whether another copy of the game is open, and it was taking ownership of that name as well as holding it. A name whose owner goes is handed to the next thing that asks for it, and a client handed it decides it is the only one and tells the rest to close.
- Farming carries on after a restart. Turning it on and opening Phasma again left it off, and quietly forgot the setting as well: the first thing the engine says after starting is that farming is off, because it has only just come up, and that was being written down as the thing to remember before anything read it.
- Phasma uses far less memory while farming a lot of clients. Checking whether a client has frozen took a picture of its window, copied the whole picture, shrank the copy to something small and threw both away, for every client, over and over. With twenty clients that is hundreds of megabytes asked for and handed back every round, and what the PC had set aside for Phasma climbed all day. The picture is now reused rather than made again.
- Reading a number off the screen no longer holds on to the last picture it read.
- A cloud backup that will not go says what went wrong instead of only that it did not go.
Changed
- Updates ask before they install. Phasma still looks for them on its own, but it shows you what changed and waits, rather than closing and coming back on its own. It can be put back the way it was under Settings, Advanced, Updates.
- The remote lets you call each PC whatever you like, and what you set on it now follows you to every device you sign in on rather than staying on the phone you set it on. Both are already live and need no update.
3.6.5
Added
- Cloud backup. A copy of everything, kept under your licence rather than on this PC: every setting, your theme and the ones saved beside it, every profile with its outputs and sequences. Accounts are in or out by choice each time, because a backup with accounts in it carries your Roblox sign ins. Several are kept, with what is in each one written beside it, and any of them can be put back. It will also do one a day on its own if you let it. A backup is locked on this PC before it leaves, so nobody at the other end can read one, and only your licence can open it again.
- An output can be exported on its own, from its row or beside Duplicate. Sequences could already do this.
Fixed
- The remote can do what its pages offer. Docking, undocking, full screen, minimise, opening accounts, the server browser and turning a sequence on or setting it to loop all answered "the remote cannot do that", because the list of what the remote may ask for was eight short. A refusal now says which thing it was.
- Signing accounts in through the browser never saved a single one. The part that does it had a database of its own that was never opened, and all it said was "DB write failed". Adding an account also asked Roblox at an address that answers a program with a web page rather than an answer.
- Signing in fills in and sends far faster. One browser is built for a whole run instead of one per account, which was most of what a long run spent its time on.
- Signing in happens out of sight. The window no longer appears and takes the keyboard for every account in the list, and comes over only when you are actually needed: a code, a puzzle, or nothing having happened for a while.
- The picture on the licence row is the right shape, instead of a square photograph sitting over a round one.
3.6.4
Fixed
- News said "Reading" and never said anything else, and the panel that tells you what changed after an update never appeared. Both were the same thing: the list of changes could not be read at all, and nothing said so.
- That panel also came up with its heading and nothing under it, because the part of it that holds the list was given no room to draw in.
Changed
- Only one Phasma at a time. Opening it again brings the one already running to the front instead of starting another. Several copies at once each took the keyboard, drove the same clients and saved over each other's settings, so whatever went wrong afterwards looked like a fault somewhere else.
3.6.3
Fixed
- A client being kicked took another one down with it. Roblox closes every other running client when a new one starts unless its single instance guard is held, and the guard was only taken when you changed the setting for it, never when Phasma opened. It is held from the start now, so a rejoin no longer closes the clients around it.
- Docking is remembered. A client that rejoins, crashes or restarts comes back on the stage instead of being left off it.
- Closing a client closes it, rather than putting Roblox's leave confirmation on screen and waiting for somebody who is not there.
- Opening the Sequences page could bring Phasma down. A recording left running writes two steps for every key pressed, so a sequence could reach thousands of steps and drawing them all was what stopped it responding. A recording now stops itself, and a sequence that is already too long offers to be cut back rather than being a page that cannot be opened.
- Restarting while farming no longer loses which window belongs to which account, or where each account was meant to rejoin.
- Clients that were minimized stay minimized after maintenance, even when one crashed or rejoined partway through.
- Farming stays on across a restart.
- Press down only holds the button down instead of pressing it again and again.
- Following a player from the Accounts page works. It never did, and a username is turned into an account rather than being sent as though it were a place.
- Finding a picture on screen is about thirty times faster when what it is looking for is not there, and no longer matches the wrong thing at a lower match percentage.
- The last seven days chart no longer spreads its bars across the panel with gaps between them, and hovering one says the date and the exact number.
- Keys are let go of properly when a licence check has not happened recently, instead of being left held down.
Added
- The remote has every page: clients you can put on or take off the stage and make full screen, sequences you can run and set to repeat, accounts you can search, filter and open by group, a browser for a place's servers, profiles, statistics, the PC's load, the whole list of problems, and who else has access.
- The remote shows every PC your key is signed in on, not just one of them.
- Picture quality and how many a second can be chosen on the remote. Both were fixed before.
- Read a number, a sequence step that takes a figure off the screen and stores it in a variable, so a sequence can stop at an amount.
- Power saving. Clients that have gone a while with nothing wrong are told to take less of the processor, and get it straight back the moment anything happens.
- Sign accounts in through the browser, in bulk, from a pasted list.
- Delete removes the selected outputs or sequences.
- News, which is what you are reading. It also shows itself once after an update.
- How long Phasma has been open, on the Statistics page.
- A picture on the licence row. Your Discord one is used if you have signed in on the website, and you can choose your own, including a gif.
- What a recording picks up can be chosen: keys, clicks, right and middle clicks, scrolling, and the pauses between things.
- Clicking can be started with no outputs, and sequences are held while it is off so one switch stops everything. Both can be changed in Settings.
Changed
- New outputs start on mouse button four.
- Minimizing no longer hides Phasma to the tray.
- Docked games hide with Phasma by default.
- Every kind of farming event can be turned on or off in notifications.
- Timing effort and input method say which value the engine is really using.
- Discord activity uses Phasma's own application, so it shows a name and an icon.
3.6.2
Fixed
- Restart actually restarts.
- Press down only keeps the button held.
Sign in if you own Phasma, and every version becomes downloadable here.