Evolin | 70 Cap | G.O 10.05 | No P2W | First Jobsystem & Map | vSro Based | Long Term

[turkmineydah]

Weeeee

[trakyali06]

Am I the only one having problems?

[trakyali06]

See you evolin, it was nice meeting you.

[Aranruth1]

Lags and no speed for new players is a no go these days, we dont wanna waste 10 minutes to run to TG mountain, also pots and stuff so hard to get. This server wont last a week.

[InZiDeR]

Server issues happen, it's a part of the online world. But remember, the person behind this server is working hard to resolve them. Instead of spreading hate, let's give him the time and space he need to fix the problems.

I get it, it's frustrating when you can't access what you want, when you want. But let's channel that frustration into patience and understanding.

And remember, server owners are always cursed on G.O. It's just a phase that goes by.

[Omnyamura]

Well, those problems could happen in the 2010s... We re in 2024 and this server has more problems than solutions.

Have a great week end everyone, dont loose your time here.

Cheers

[InZiDeR]

Originally Posted by Omnyamura

Well, those problems could happen in the 2010s... We re in 2024 and this server has more problems than solutions.

Have a great week end everyone, dont loose your time here.

Cheers

Back in 2010, the VSRO files weren't even leaked...

Unlike other sporadic projects owners that emerge (wannabe 60 cap os servers), B0ykoe is a recognized figure in the community with a track record of positive feedback. Let's be patient and have faith that he'll resolve the issues

[b0ykoe]

Originally Posted by InZiDeR

Back in 2010, the VSRO files weren't even leaked...

Unlike other sporadic projects owners that emerge (wannabe 60 cap os servers), B0ykoe is a recognized figure in the community with a track record of positive feedback. Let's be patient and have faith that he'll resolve the issues

Made me smile after reading through this mess. I will obviously not hide what happened so here we go:

I'm deeply sorry about how the GO went. This was not expected and neither did reflect any of our tests. Production is simply something different, something by far more dynamic then testing.

To take out some rumors. No it was not a DDoS, no it was not any of our servers going down duo to performance issues, it wasn't the directly the filter falling onto its knees. It was the Database. Basically what happened is that a check in the filter did straight up miss the local cache and request the database. Every, single, damn time. Imagine every monster around you being one query. The database just gets hit over and over and over again and simply at one point timing out. This lead the filter to wait for results and at some point mass timeout.

- Website is running behind Cloudflare on a own VM with 8 dedicated cores and 16gb of ram (using less than 100mb).
- Filter is running on 16 dedicated cores and 16gb of ram (using 1.5gb while having the full db cached)
- Two gameservers and the database are running on their own dedicated server in a vm, duo to scaling - moving - backup reasons, with 16 dedicated cores and 32 gb ram

The databaseserver just stopped at 3.4gb ram usage and wouldn't move any further. This might be a soft cap where it starts to clean up old statistics. Right now its at 2.4gb and building up.

Can this happen again?
The short answer is yes. The long answer is that it is hard to answer. Was it the cache? Was it the database server? In the end we'll see

Noob gm, why no prevent?
While we could've gone with Maxiguard, VSROPlus or any other filter I wanted to use my own project. The reason is simple, its open source and free. I want other servers to be free in their choice and have a solid alternative. Therefore I was confident enough that our tests, with up to 1k chars, was enough. Reality hit, it wasn't enough of a test.

Compensation
I said I'll compensate, I'll compensate. Right now I've send every Account 150 silk and every character large mp / hp pots

Thank you for understanding and I'm sorry.
- Ahri

Ps: we jumped from 114 players to 90 in that time. We're back up to 108.

[BowHunter]

Originally Posted by b0ykoe

Made me smile after reading through this mess. I will obviously not hide what happened so here we go:

I'm deeply sorry about how the GO went. This was not expected and neither did reflect any of our tests. Production is simply something different, something by far more dynamic then testing.

To take out some rumors. No it was not a DDoS, no it was not any of our servers going down duo to performance issues, it wasn't the directly the filter falling onto its knees. It was the Database. Basically what happened is that a check in the filter did straight up miss the local cache and request the database. Every, single, damn time. Imagine every monster around you being one query. The database just gets hit over and over and over again and simply at one point timing out. This lead the filter to wait for results and at some point mass timeout.

- Website is running behind Cloudflare on a own VM with 8 dedicated cores and 16gb of ram (using less than 100mb).
- Filter is running on 16 dedicated cores and 16gb of ram (using 1.5gb while having the full db cached)
- Two gameservers and the database are running on their own dedicated server in a vm, duo to scaling - moving - backup reasons, with 16 dedicated cores and 32 gb ram

The databaseserver just stopped at 3.4gb ram usage and wouldn't move any further. This might be a soft cap where it starts to clean up old statistics. Right now its at 2.4gb and building up.

Can this happen again?
The short answer is yes. The long answer is that it is hard to answer. Was it the cache? Was it the database server? In the end we'll see

Noob gm, why no prevent?
While we could've gone with Maxiguard, VSROPlus or any other filter I wanted to use my own project. The reason is simple, its open source and free. I want other servers to be free in their choice and have a solid alternative. Therefore I was confident enough that our tests, with up to 1k chars, was enough. Reality hit, it wasn't enough of a test.

Compensation
I said I'll compensate, I'll compensate. Right now I've send every Account 150 silk and every character large mp / hp pots

Thank you for understanding and I'm sorry.
- Ahri

Ps: we jumped from 114 players to 90 in that time. We're back up to 108.

Thanks for the compensation and the effort!
I'm in and happy to play. :-)

By the way - sbot crack works just fine. People are always complaining.. that's just how it goes.

Anyways see you ingame!

[SubZero**]

Wishing you nothing but the best, my friend!

[mertacgz]

perfect swwww

[Darknessmist]

A unique server, a minor setback in the g.o but everything is smooth now and we are really enjoying it!

[b0ykoe]

Another day, another update. Plans for today:

- fix the problem with the cracked bot (done)
- set up another vm for a raw mssql server
- migrate to that new vm

The downtime is expected to be 30 minutes and will be announced 1 hour in advance. There will be no update, so you can just set up your bot and go out.

Cracked bots have been an issue that has been messy. On the one hand, I don't want to support them. There are great alternatives like rsBot, paid sBot and phBot. On the other hand, many players use them.
Even though I would be happy if they supported the developers. Unfortunately, there was also a lot of antipathy towards rsBot. Simply because it seems to be a bit slower. It's sad to hear that he didn't get the chance he deserved, even if he attacks monsters 0.1 seconds slower.

Anyway, I've added `?fixbots` as an in-game command. Here is a quick video. You will permanently lose the 5 pet pages and the 4th inventory page.

[vemtoo]

Originally Posted by Unguided

You will need to buy an official bot to play here no cracked bots work here. Almost no players because of it. Dont join. Tragedy, not a server.

It's all fixed even cracked bots working too, you guys need to give admins some time to fix issues, you're making decisions too fast.

[staska393]

is it down??