This is a discussion on OldSchoolKO - ERAGON Reborns! JUNE THE 5TH (official) - Miami 13:00 hours within the Private Servers forums, part of the Knight Online (ko4life.com) category; Originally Posted by tobol
how much is class change scroll?
well acme kicks me from pus everytime. Any solution?
Acme kicks me before entering the game. I hate their security updates so much, there are still koxpers running around ingame and legit players cannot login because some false positive or acme just failing to update no matter what.
Same thing as with the previous OSKO launch, they updated acme and after that I couldnt login for 2 weeks..
I get this line briefly on my firefox and get forwarded to acmecore forums:
well their support sucks, unless you wont find the way to fix that you wont be able to play I guess
still waiting destruction and talia stuffs. since 10 days its bugged. zzzzzzzzzzzzzzzzzz
Bump! Server still kicking hard. Increased PK quite a bit after players got their gear & masters up. Now the server need's to spice things up like adding drops on duke/bach/bishop. That's quite easy thing to do and increases activity on bowl even more!
For new players: Exping to 61 is easy even without premium, You can farm up raptor/shards and chitin set in few days. Masters require quite a bit of farm or mental durability on camping bowl with 20 enemy sins
Keep it up Prof!
There's something inherently broken with damage and range overall. A raptor +6 sword dancing fuck should not be able to spam 700 each hit... same goes to a shard+6 sin and their 1100 damage spikes (Wasn't like this on prev. Osko servers where'd I'd get SD'd max 600 and spiked 800-900, I refuse to believe that Pathos Gloves are the sole culprit either).
Am I the only one who gets deceived by the visual range between me and my enemies in game? Enemies are way closer than they appear, always. I get duffed from miles away too, it's like my position took too long to update in the client.
Other than that, server's looking good yes.
you better ban those koxp mages on dms
But as I said before, it's really easy to screw it up especially since the intended behaviour differed a little between versions officially. It wasn't until 1.9xx when mgame allowed for the client to say where it actually is at the time of the movement update, instead of its intended destination, which helps a lot (especially for speed hacking/collision detection!).
OSKO are using 1.8xx AFAIK, which sounds to me like they're storing the destination position server-side as if the client was at the destination already (i.e. client says I'm going to x,y, server says okay -- you're there), and relaying the client packet which the clients still handle as if they're still moving from their last known position to the destination position). So effectively they're a lot closer than they appear, but you don't see them there yet (either that or it's the inverse, confusing).
Otherwise, if it's 1.9xx -- just means they're not making use of the other position (client's current position as of the movement update) in the client packet which solves all of this confusion. >_<
I don't know about the visual range, we haven't got any trouble with it so far. Sometimes we see players lagging so much so it looks like they are speedhacking