Appreciate the thoughtful post. To do what you're asking for properly, the system would have to be backed by official dedicated servers. As you can imagine, it isn't cheap to rent solid, DDoS-protected servers all over the world, which makes it economically infeasible for us to do (we're talking thousands of $ per month).
Unless someone with deep pockets would be up for sponsoring this, our only option would be a peer-to-peer system, which leaves a lot to be desired...
Fixed.
Took care of it.
Fixed.
Bug in the forum software. The issue has been fixed and will be included in an update tomorrow.
The ban has been lifted.
The ban has been lifted.
Astrocule Is mostly correct. As much as I'd love to have a sleek dashboard with tons of metrics to be able to easily investigate things like this, that's simply not the reality.
I just pulled some stats (using raw database queries...), if all players who got banned in the last 30 days (131 players) were banned falsely, that'd work out to a ~0.07% false positive ratio. This seems to be slightly lower than average too, when comparing over a longer period of time.
Based on these numbers alone, I still wouldn't rule out the possibility of false positives, but it's going to be very hard for us to determine what the cause might be, given our limited data.
Your username has been restored.
The game died due to lack of player interest, nobody is going to put in the effort to revive this game, especially not us.
The ban has been lifted.
prophetarmed said in Quantom of Solace Wine Incompatibility:
Eldor Thank you so much!
It now gets much further than it did before but I am getting
"Error during initialization:
Failed to bind socket, error 10013." on startup.
I've tried various Wine versions and cleared the wine prefix but no luck - do you recognise this error?
Try running with sudo/root.
Thanks for reminding me! A new update that should fix Wine compatibility is now out, you can download it from https://cdn.plutonium.pw/quantum/plutonium-quantum.exe
EagleWatch said in Find a solution for the problem faced by Iraqi players:
it is your job to keep it up and find solution for people who cannot use it
No, it is not. If you can't cope with that reality, go ahead and leave.
A solution for this would be an alternative (non-Cloudflare) ingress path for backend traffic, which would have to routed through separate infrastructure. This would likely cost us at least an additional ~$10/month for something that wouldn't immediately die from even a small DDoS attack. Development time would have to be spent to implement this fallback method as well. Are you willing to pool together, say $100 to cover this?
It's likely that they didn't explicitly block us, but rather another site that happened to be assigned the same IP as us by Cloudflare (which we use to protect ourselves against DDoS attacks, among other things). Unfortunately there's nothing we can do on our end with our limited budget to immediately fix this, but you (and others having the same issue) can try to complain to them like Xerxes suggested in hopes that they will lift (or fix) the block if they can.
After further consideration, we've decided to temporarily ban the "Z-TAVERN" servers for a duration of 2 weeks effective immediately. We do not appreciate people monetizing ours (and others) efforts and goodwill like this. No further "rent seeking" or similar behavior will be tolerated, do better or face the consequences. Recouping server expenses is one thing, trying to turn it into a "business" is not.
Eizekiels You've caused trouble before, consider this your final warning.
We don't have very strict rules on what people can and can't do within their own communities, and this drama seems to be largely concentrated outside our core community. With that said, we don't want assholes that ruin the fun for others around either, so we'll take a closer look at this.
What you could do meanwhile, is to chargeback or open disputes for the payments you've sent them (provided it wasn't too long ago), if they indeed have defrauded you.
IUseArchBtw-1 You're in luck, we managed to fix it and will ship this together with some other features in the near future. Login seemed "broken" (failed to open a web browser, could be related to my install or how Wine handles protocols), but works using the manual steps outlined in the announcement post. Thanks for reporting 
Hey, thanks for the detailed post! At first glance it doesn't seem to be related to Themida, I can reproduce the crash you're seeing on a debug build with wine 9.3. Will see if we can fix this with reasonable effort, but Linux support (especially for games) is usually only supported on a "if it works it works"-basis, so no promises.