Test Server Feedback

This was actually what started me thinking about the time multiplier. If not teams though, this implant idea is pretty interesting. Good job folks! 99% is never happening though :)

75% is also a fine number ^^

But yes, the last thing we need is another SC hotdrop preying on 1v1 tests.. but after all, the SC are not the problem, but the interdictors, who pin you down there in the first place and provide the warpin and cyno ^^

But i wont start this now, because it has been beaten to death by now.

Just see, if you can get lost a bit of the casual waiting time on jobs in reseach/industry, that would help alot, not to mention the fact that if you dont have a corp ready on TQ, you will wait another 7 days before you can set up your first POS, what will leave you with only 7 days for anything else, if we only have 2 weeks between each Mirror.

But i think we will get a solution here that fits everyone fine.

Upon the application of a new mirror, each account is given a single item (via redeem system) that when added into the build of a super capital reduces the manufacturing time by 60%. Seems reasonable as far as time and helps limit their mass production as well.

sit down together in a Captain's Quarters

I'd like to avoid a total segregation approach if possible. I have a dream that one day under the red sun of 6-CZ49 the sons of titan pilots and the sons of destroyer pilots will be able to sit down together in a Captain's Quarters of brotherhood.

Not going to work because somebody will assign fighters from the undock and come haze you inside the "cap free" combat area.
and if the rules kept craziness in check then we wouldnt see people getting supercap blobbed on the undock. Let's throw that out of the window. Clammoring for all deadspace officer gear was a disaster last time they did it too btw. How realistic is your "test" when you are slogging through godtanks on a rupture. Not very I'm guessing. Current system is fine.

1 if the rules say no fighters in the non supercap area then they could get banned for sending them to it

2 not my fault you are not reporting them for blobing on the undock as afaik that is infact a bannable offense (last i read the rules it said combat is to be in the combat areas and nowhere else)

3.let me get this straight you play eve and you brought a knife to a gun fight? well guess that rupture kill you huh maybe next time you will get a corp mate or w/e to join you on sisi so you dont have to worry about that sort of thing.

edit: its been a while since i been on sisi so i havent bothered to go read the rules so i could be wrong about point 2 but the point im making is still viable, if it's in the rules and you report when someone breaks said rules then ccp will handle them. IRL it's against the law for someone to ****...but if you arent going to report them to the police when they do it dont whine about it to me.

you should prob learn a thing or 2 about coding before opening your mouth as the entire server is most certainly not reprogrammed to implement my suggestion

Hey folks,

I understand that the mirroring cadence can be troubling to you, particularly relating to building things that take a long time. The short answer is that we mirror as and when we need it for testing purposes. In this instance we need a mirror to get relevant data onto the Sisi DB so that we can perform another upgrade test to ensure that our deployment next week will be smooth and on time.

Moving forward, we are actually trying to make mirrors on a regular cadence (though there will always be exceptions) but also to increase their frequency to as much as every 2 weeks. Obviously this has some problems and we would be very receptive to hearing them (more dedicated feedback threads will go up nearer the time, but I'm now subscribed to this thread so feel free to post here too), but it also addresses one of the most oft-asked things, which is the lack of frequency of mirrors. So, with that in mind, let's hear some ideas (like Orny's above) of how we could go about mitigating the issues that come with frequent mirrors. If at all possible, bear in mind that Sisi cannot be a special little flower and have massive code differences from TQ, or it invalidates itself as a test environment.