butterflydog5 0 Share Posted October 14, 2017 hello a week or two ago quickhop was disabled on all clients then recently starting working on OSBuddy. by quick hop i mean hop to same world (W318->W318) without having to re-enter info. i was really hoping that this could get fixed soon since it is fixed on OSBuddy. thanks Link to comment Share on other sites More sharing options...
Stan 7 Share Posted October 14, 2017 pls fix Link to comment Share on other sites More sharing options...
Manly 879 Share Posted October 14, 2017 nezz said most likely not gonna be fixed. Link to comment Share on other sites More sharing options...
Clock Work 31 Share Posted October 14, 2017 Ya the way they rewrote the code for it is pretty ugly. Link to comment Share on other sites More sharing options...
butterflydog5 0 Author Share Posted October 14, 2017 nezz said most likely not gonna be fixed. was there any reasoning for this? really doesn't make sense as to why he wouldn't, assuming this would is an easy fix. Link to comment Share on other sites More sharing options...
Manly 879 Share Posted October 14, 2017 was there any reasoning for this? really doesn't make sense as to why he wouldn't, assuming this would is an easy fix. You cant assume its an easy fix if you are not a dev or dont know anything about the client. Link to comment Share on other sites More sharing options...
Nuclear Nezz 2052 Share Posted October 14, 2017 It's not an easy fix lol They added some kind of verification on the server (assuming) It used to just be that you could disconnect the socket, force change the host/world, and let the game reconnect itself. That is no longer the case. I've played with it a bit, but since we're limited to reflection it's rather tedious to "force" anything. I mean it's very possible I just missed something, or just don't know how the socket related things work. It is one of the areas of the gamepack I haven't actually put much time into looking at. OSBuddy devs were able to literally just ask the Jagex Devs what they changed, and worked on a solution based around that. They also have the access to say "Hey, this is what we're going to try, will this get our users banned?" We do not. Assuming we do find a work around for it, we also have to thoroughly test it to make sure it doesn't get everybody using it banned. If you have suggestions, I'd be happy to hear them, though. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.