#Modpack:Prominence II [RPG] What to add: Add th...
exotic geyser
karmic quest
!powershell
silent vesselBOT
An update to windows introduced a new security feature that prevents powershell files from running on your PC. This is great for your security, but not so great for our server start scripts, which require powershell to run them. Fortunately there is a quick fix for this!
Run powershell as administrator, then run Set-ExecutionPolicy RemoteSigned. Read the prompt and press accept. This will allow us to run scripts.
Next, navigate to your server directory using cd path/to/directory (for example: cd C:\Users\Username\Documents\Minecraft\Server)
You can now run the server by double-clicking the start.ps1 file, or typing .\start.ps1 into the command line while in the directory.
IF THE ABOVE DOES NOT WORK, TRY THIS
Run the command Unblock-File -Path .\start.ps1 in the same powershell window. This will allow the start script to not be blocked by windows, and run freely.
ripe void
I was able to run the powershell script. I had previously set the execution policy to allow any script to run (I do this as a write manual scripts quite often to run things) When I reviewed the error logs from trying to start the server, it just failed out and said it couldn't connect to the url.
shut lake
where did you download the serverpack from, the app or the website
btw this is the suggestions channel, not support
ripe void
Yeah I know. I was suggesting the server.jar just be added to the server pack* like several other modpacks do, thus minimizing weird interactions like this when Mojang does weird things with their servers. I already got it working using a downloaded jar from waybackmachine. I downloaded the serverpack from the cursed forge app.
shut lake
Curse does not allow jar files as part of serverpacks