haha, was thinking the exact same thing.Originally Posted by swoozie
This is a discussion on KO-Tastic! within the Private Servers forums, part of the Knight Online (ko4life.com) category; Originally Posted by swoozie
another SRB ?
haha, was thinking the exact same thing....
Page: 65
LinkBack URL
About LinkBacks
haha, was thinking the exact same thing.
Gadget : (19 July 2011 - 01:53 AM) Still here, still working on it. As already mentioned in numerous topics: We WILL update you at least one hour prior to putting the server back up. Go out, do something else, waiting and spamming the forums doesn't help anyone.
josh stop licking twostars's balls/pussy..
i dont even know if twostars is a male or female xd
he is male....
The kind of attack you're trying was used back in Win98 times. Back then, it was effective due to OS flaws. Now it's just useless, and I didn't even have to do anything against it to make it that way. I'm repeating again - it wasn't you. I know who it was, and really... I know DDoS' are going to happen. It was only brief, the point of it (despite being overkill) was to knock the game server offline and cause it to stop accepting connections, which I'll explain below (again... I just CTRL+W'd by accident).
The problem wasn't the DDoS, that's fine - it only takes one to take it down. The problem is mgame's retarded socket system (which leads me to wonder more and more why I even thought it wise to help out a server using mgame's code).maybe twostars tought he can stop small ddos from bringing down his server....all i know is that he change some of the code or whatever...to handle a higher load as usually.
problem is, that twostars didnt host a server yet with such a high volume of people playing...live experience is harder to handle with than just doing coding and thinking its gonna work out the way you wrote the code
to put it in a nutshell, he is a good coder but lacks live server experience
edit: i know he put a lot server online, but i guess none of them were as populated to ddos them that hard?!
Their system breaks and stops accepting new connections when it's (briefly) flooded with new connections. What seems to be happening, however, is this code seems to be being completely broken out of, and short of replicating it myself, it's trial and error working out what exactly's doing it. This is why I asked the one person I know to have fixed it for any advice; osmanx.
Unfortunately, it's been a while and he no longer has the fix on-hand, but because he has people experiencing that issue too lately, he said he'd do up a new fix "tomorrow", so... despite not being able to give me much advice, I figured there was probably no point in me looking into it any further, and just focused on the new issues (and decreasing the chances of floods being more effective).
That said, we decided to put the server up (after I finished working on the above) and (sadly) just hope nobody abused that particular exploit on us until I was able to apply the fix, but that was obviously a little too hopeful as the person who's doing it is very persistent.
I'll have another look at the issue, and have left a message to osmanx just in case.
One way or another, the issue is being resolved very soon - that particular issue is the only one that is still plaguing us. Everything else we've been able to deal with as they happen - we haven't actually experienced anything new since the DDoS attack we experienced earlier, it just keeps coming back to this one issue.
If I don't manage to solve it before osmanx does (and he will, because he's done it before, and hence knows how exactly it's causing it to break :P), there's always him. So there's a server to look forward to one way or another, I just hope for my own sake that I solve it first. :P
On another note, woke up today to find my PC had restarted (no idea if osmanx IM'd me) after a power surge, and... my video card seems to be dead (agh).
Definitely a fun week.
Despite what people may think however, we have absolutely no plans to give up as other servers have done in the past.
What do you mean by "very soon" , your words bamboozle me.
It seems that your time concept is very wrong and is relative to the time on some planet far far away.
"Very soon" as in no longer than 48 hours at absolute most.
LOL i thought ur very soon meant like 4 hrs xD
No, that's my "shortly." You'll have to write up a translation for these... for later.
Oh , wow... good luck losing the rest of the community.
alright. monopoly/aion for the next 48 hrs boyz lets go.
Thanks. Sadly, can't be helped. The good news, however, is that it's just this one issue remaining (still).
I'm thinking within 24 hours is more reasonable, but giving an absolute maximum of 48 hours... just in case.
Just come back to WOW bro
HAHAHAHAHHHAHAHAHAHHAHAHHAHAHAHAHAHAHAHAHAHAHJust come back to WOW bro
AHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAH
bb
Out of all honesty you just killed the population. Even though it might be a few days that ALOT of the players have wasted no-lifing both in game and waiting for it, me being one of them... I strongly suggest restarting the whole thing... and that is wiping the server and making another official day WITH 100% CERTAINTY that this bug that you say will be the last one that is actually preventing us from playing, and with it the fix that you are suppose to get soon it should work fine.
Posting Permissions
Bookmarks