Connecticut Changes?

[hribek]

Alex, that thread is almost 18 months old, and the proposal is specific to jumphole moving. I could say that posting there would be gravedigging, so I think it is better if we continue the discussion here - and it can be more general.

(Would supreme search function users please abstain from interfering and use PMs instead?)

Now, on topic:

The suggestion presented here still has the following drawbacks:

• Easy transfer of mounted weapons and equipment to anywhere. Think codename guns.
  
• Connecticut will still use up RP server resources, if there is a large battle somewhere (in Conn or not) the result is performance loss for all players on the server.
  
• The beaming timer is suboptimal if you just want to run some quick test of your setup or so.
  
• An extra FL Hook command needs to be implemented and debugged for it.
  

My post doesn't end here because I'm not and don't want to be part of the "search function masters". I'm going to come up with an alternative which can possibly fix the above, with a bonus.

Here's how:

• A PvP server could be set up by means of an additional server install on the machine that's running the dev test server normally (and was used for events in the past).
  
• Players who connect would have the .setcash .beam and .setrep commands available for own ships only, allowing a very quick setup for any PvP / balance / mod testing. It would even be faster than flying to Connecticut.
  
• No mod changes have to be made for this.
  
• When 4.86 beta is out, or even after regular release, this will allow easier testing of features like turret split. No doubt swapping turrets around takes extra time & credits - it could be much more streamlined.
  
• Less lag for good PvP experience, no performance loss for RP server during non-RP PvP fights or vice versa. Extra server slots during peak times.