Jump to content

Our Goals For This Week


Maxi

Recommended Posts

  • Developer

Well, we might as well just put it our here. We have a massive goal set once again for this week. We've done that in the past and managed to more or less meet our goals within time. We will try to do the same thing this week, however this time it feels as if it's even more and the impact of these updates will make us the best bot out there if we manage to pull it off in time. So let's get to the list:

Client related goals:

    [*]Find the source of invalid logins / unable to login / unable to connect to Runescape. This bug happens only to a select group of users, however we want OSBot to be public to everyone

    [*]Find the left sources of any freezing issues. I have not encountered it myself, but will try to reproduce the bug and profile it to find its origin. It's most likely a crash of the RS client itself caused by injected callbacks.

    [*]Fix up the skill hooks

    [*]Fix up the facing uid hook so we can return the proper facing entity

    [*]Add facing coordinates, x and y

    [*]Add the character chat messages, both force chat (used for randoms and such) and regular chat (used to write an AI to talk with other players in RS in the future)

    [*]Add the ability to provide the walking method with a collection of Position objects to create custom selfmade paths and lower overhead

    [*]Add a proper enum for hitsplats

    [*]Add a canReach method not only for entity, which we already have, but also for arbitrary Position objects

    [*]Find and fix the origin of non running onLoop() methods. This has occurred to me in the past, however not after last update, so we'll once again have to reproduce and find the cause.

Non client related goals:

    [*]Finish up the SDN portal where script developers can login to maintain, update and submit their scripts. Set up the logic on the client and server to handle access to certain scripts (like premium scripts), automatic updates on random event handlers and a secure mechanism of providing the OSBot client with premium scripts that will prevent leaking to protect the creators of the scripts

    [*]Randoms, like we said, we aim to have most if not all randoms with their first version updated through the SDN once it's setup

After writing this list I realized we should stop writing more and put the effort into real code!

Yours sincerely,

OSBot.org

  • Like 4
Link to comment
Share on other sites

 

Well, we might as well just put it our here. We have a massive goal set once again for this week. We've done that in the past and managed to more or less meet our goals within time. We will try to do the same thing this week, however this time it feels as if it's even more and the impact of these updates will make us the best bot out there if we manage to pull it off in time. So let's get to the list:

Client related goals:

[*]Find the source of invalid logins / unable to login / unable to connect to Runescape. This bug happens only to a select group of users, however we want OSBot to be public to everyone

[*]Find the left sources of any freezing issues. I have not encountered it myself, but will try to reproduce the bug and profile it to find its origin. It's most likely a crash of the RS client itself caused by injected callbacks.

[*]Fix up the skill hooks

[*]Fix up the facing uid hook so we can return the proper facing entity

[*]Add facing coordinates, x and y

[*]Add the character chat messages, both force chat (used for randoms and such) and regular chat (used to write an AI to talk with other players in RS in the future)

[*]Add the ability to provide the walking method with a collection of Position objects to create custom selfmade paths and lower overhead

[*]Add a proper enum for hitsplats

[*]Add a canReach method not only for entity, which we already have, but also for arbitrary Position objects

[*]Find and fix the origin of non running onLoop() methods. This has occurred to me in the past, however not after last update, so we'll once again have to reproduce and find the cause.

Non client related goals:

[*]Finish up the SDN portal where script developers can login to maintain, update and submit their scripts. Set up the logic on the client and server to handle access to certain scripts (like premium scripts), automatic updates on random event handlers and a secure mechanism of providing the OSBot client with premium scripts that will prevent leaking to protect the creators of the scripts

[*]Randoms, like we said, we aim to have most if not all randoms with their first version updated through the SDN once it's setup

After writing this list I realized we should stop writing more and put the effort into real code!

Yours sincerely,

OSBot.org

 

Try using my fight-cave script, or any other fight-cave script to find the client-freeze issue as it seems like the issue occurs more there.

Edited by XenoTools
Link to comment
Share on other sites

What are the account requirements to go there and use it? My account is very low level so I assume I won't last long. If so, I'll have to borrow an account to profile.

It is fine if you are a low level. You will still be subject to any freezing issues, because the script re-enters the cave regardless of how many times you die. It's pretty much the only combat bot with 'death walking' so you should be set with your low level.

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...