Search results

It couldn't and cannot be up before the new launcher is done as the old one does not have the capability to deliver a beta version. Additionally, because of the way it was built it could not be extended to add the capacity. No one wanted to rebuild it, because it takes time away from other...

I mean its not that differnt from what is there now, so i dont know why people expect so much from it. But we will test it and i stand ready to eat my words.

Not exactly. Different people work on different things. It wouldnt have been right to hold up CTF when there were other things that differnt people needed to do to get Open Betas ready - namely launcher. Since you were not one of the two people who gave test feedback on internal beta launcher...

That is not true - and you know it.

As now then - no less than 4 weeks.

It will go to open beta when we are ready. There has never been a firm date and this kind of thing makes me wonder if it would be a better idea to go back to not talking about time scales at all. What needs to happen to get the open beta out is this: Finish new launcher Migrate all users to...

In the user info string it wont. It might be ppssible in other ways.

Space in the userinfo string is extremely limited and anything that uniquely identifies a player that is added by MB2 would be hidden as much as possible to prevent impersonation.

We wont be porting our code base to arm64.

1.03 sounds like Jedi Outcast not Jedi Academy.

Ok - I will rephrase that. We are not holding back some magic cure to the problem. We are not holding anything back which would be of any use to anyone else anywhere else

Both are true. We are not holding anything back and the protections in place for our infrastructure are uniquely tailored to our environment. Some of the utilities may or may not be used by other server hosts - and we have no way of knowing if what we have is any more effective than what anyone...

If we had anything that could help everyone we wouldn't keep it to ourselves. If this were a solvable problem in the generic sense then there would be as many blog posts and articles about it as there are about preventing SQL injection. Protections would be baked into operating systems and the...

I'm not sure what you want here. There are 60 servers give or take - some will be in a common host environment so lets say that is conservatively 40 different setups with differences ranging from different bandwidths, different network hardware, different operating systems, different levels of...

You believe very incorrectly. Security of hosts is the responsibility of the hosts. It's enough trouble being responsible for one set of infrastructure taking on responsibility for everyone else's is plain ridiculous. Every server host operates in a unique environment, what works well for one...

When you did this part - which browser did you use? Did it auto-upgrade to https? Can you try the same link Internet Explorer? Can you also please try the beta launcher?

Dont click repair - just restart the launcher. With logging enabled a log should get written to /MBII_Launcher/logs/

Can you please enable logging in launcher and, restart launcher and then send the latest log.

Proprietary is such a loaded and often misleading term. It is not proprietary - it is http and json. It is private as it is tied to our infrastructure and we don't want to have any sort of responsibility to not break it. Forums have some RSS capability if it could do what we do right now with...

The cross platform updater already has everything anyone would need as far as i know. It is entirely scriptable, so anyone could whack a UI ontop of it. There are no advantages to be had by open sourcing it - the amount of required to wrap a UI around it would be the same.