https://github.com/mxve/plutonium-updater.rs/releases/latest/download/plutonium-updater-x86_64-unknown-linux-gnu.tar.gzhttps://github.com/mxve/plutonium-updater.rs/releases/latest/download/plutonium-updater-x86_64-pc-windows-msvc.ziphttps://github.com/mxve/plutonium-updater.rs/releases/latest/download/plutonium-updater-x86_64-apple-darwin.tar.gztar xfv plutonium-updater-x86_64-unknown-linux-gnu.tar.gzchmod +x plutonium-updater./plutonium-updater@echo off
set installDir=C:\your_pluto_directory
plutonium-updater.exe -d "%installDir%"
#!/bin/bash
INSTALLDIR=/home/pluto/pluto_dir
./plutonium-updater.exe -d "$INSTALLDIR"
./plutonium-updater.exe -f
or
./plutonium-updater.exe -fd "pluto directory"
-h, --help
-V, --version
-d, --directory <path>
-f, --force
-l, --launcher
-q, --quiet
-s, --silent
-c, --check
--no-color
--no-backup
--backup
--backup-list
--backup-restore <backup>
updatink yes
My preferred way is to have a separate plutonium directory (the one in %LocalAppData%\Plutonium, where you put your scripts) for every server.
@echo off
set plutonium=C:\path\to\plutonium.exe
set installDir=C:\unique\dir
"%plutonium%" -install-dir "%installDir%" -update-only
Update your start.bat
if you use the default start bat, there'll be a line like this
cd /D %LOCALAPPDATA%\Plutonium
change "%LOCALAPPDATA%\Plutonium" to the path you set for installDir
Put scripts on the new plutonium folder, or don't if you don't want any :^)
A different way is to modify your script(s) so they only load on servers with a specific port
https://forum.plutonium.pw/topic/17070/assign-a-script-to-another-server-how?_=1643248860552
You could use https://forum.plutonium.pw/topic/17548/linux-windows-server-updater to still keep getting updates.
It by default only checks file hashes when a new version has been released, and can also skips launcher files, although I'd recommend against skipping the launcher files.
You could do something like this, if you drop the latest .exe in to %localappdata%\Plutonium\bin
set plutopath=%localappdata%\Plutonium\
%plutopath%bin\plutonium-updater.exe -l -d %plutopath%
start "" "%plutopath%bin\plutonium-launcher-win32.exe"
-l makes the updater check the launcher files, but only if a new plutonium revision has been released, I'd recommend keeping it so the launcher doesn't break if theres an update for it.
Plutonium isn't about playing for free, it's about adding features and enhancements to old games
BO3 already has most, if not all, things plutonium would be adding
A Plutonium client for BO3 wouldn't make it suddenly get more players
@Dr-Stone762 said in T7.:
I think I would like to see bo1 or even aw more than bo3 because they are games that I have not played in 2 generations of consoles (ps3), I would like the plutonium team to support one of those 2, I personally loved it that plutonium gave me the opportunity to replay the great and nostalgic bo2
bo3 < bo1/aw
for nostalgia
BO1 (T5) has already been announced. Theres no ETA, but it is being worked on.
@IHateBlackOps4 said in [Web] Plutonium Server List:
I have some suggestions.
- H1 support when?
Currently not planned
- Any way you can have it select certain games to show up? e.g. show only IW5 and T5 servers and/or don't show Pluto Zombies servers?
You can make it show only a single game by using the links above the table:
https://i.mxve.de/v/qqrctshw.mp4
Filtering for multiple games isn't really something I want to do, because I feel like it would make things too cluttered or harder to use.
@EternalllZM In that case it's usually a firewall problem or some other kind of routing/connectivity thing.
The server successfully connects to the plutonium master & authorizes with the provided key.
The way the ingame server list works is basically:
For your server it seems to fail on step 2, the client can't reach the server.
Thats at least as far as I know.
You are using a somewhat "complicated" hosting setup, is the server running on a system with a different ipv4 than the one it's routed through to the public? Does the online server list return the correct IP? If not, you could try setting it using +set net_ip 0.0.0.0.
Also Plutonium servers only use UDP (Not really fun fun fact: xlabs servers use UDP and TCP), of course opening the TCP ports won't make it stop working but just so you know.
(plutonium.pw/api/servers and list.plutools.pw should list the same servers, as the latter uses the api)
You can check https://list.plutools.pw/, if you find it on there it successfully connects to plutonium.
This may also be a configuration issue, maybe a typo in the maprotation or similiar, make sure to check the servers output for errors.
https://list.plutools.pw/t5mp
Shows the real player count, in parentheses is the number of bots on the server
