[RFE] Load Scenarios on a Dedicated Server #6262
Labels
New Feature
Used with the RFE tag to indicate a new feature
(RFE) Enhancement
Requests for Enhancement, new features or implementations
Scenario
Prerequisites and Pre-Issue Checklist
I'm reporting the RFE to the correct repository:
MegaMek
MegaMekLab
MekHQ
Does this conform with our Content Policy linked above?
I've searched the GitHub tracker and haven't found a similar feature request listed
RFE Details *
This is a new feature
Brief Description *
A way to either load custom scenarios onto a dedicated server (maybe from the lobby) and have players connect to it, or a way to automate the described process I used to simulate this without opening an independent MegaMek client window for each player in the game.
MegaMekLab Suite Version *
0.49.19.1
Attach Files
Problem: No obvious way to load a created scenario to a dedicated server. (There are other limitations with created scenarios not relevant to this workaround) This poses a challenge when running a GM'd roleplay-centric campaign and using a personal dedicated server. I wanted to be able to load directly into combat without everybody having to choose units, set correct starting positions, etc., as well as have all the GM-controlled assets be ready to go.
Steps to Bypass Process: I took a multi-step approach. I connected to the dedicated server as the GM and pre-set up all of the GM's options, starting positions, camo, etc. Once done, I connected extra client windows to the server as each player and did the same. I used "I'm Done" to start the match, with the players set to deploy at the start of round 1 to allow me to place all GM units. Once done, I disconnected the extra clients, and had the players later connect to the server, allowing them to load straight in as their chosen BattleMechs for their characters and place them according to the rules of engagement. This also bypassed having to have the players set up their SPA's, Edge, etc., correctly.
Final Checklist
The text was updated successfully, but these errors were encountered: