Poll: Would you like to see injection included in Simba?

Page 5 of 5 FirstFirst ... 345
Results 101 to 117 of 117

Thread: Injection

  1. #101
    Join Date
    Mar 2013
    Posts
    67
    Mentioned
    0 Post(s)
    Quoted
    41 Post(s)

    Default

    What makes simba attractive to me that it is NOT an injection bot. Injection bots always get caught, or the scripter/bot makers steals account info. I have even heard of the bots being made to automatically dump their gathered resources/bank in to the script writers account (via a bot of is own).

    Seriously, dont make Simba in to rsbot 2.0: extra shitty edition

  2. #102
    Join Date
    Mar 2012
    Location
    127.0.0.1
    Posts
    3,383
    Mentioned
    95 Post(s)
    Quoted
    717 Post(s)

    Default

    Quote Originally Posted by luxrath View Post
    What makes simba attractive to me that it is NOT an injection bot. Injection bots always get caught, or the scripter/bot makers steals account info. I have even heard of the bots being made to automatically dump their gathered resources/bank in to the script writers account (via a bot of is own).

    Seriously, dont make Simba in to rsbot 2.0: extra shitty edition
    It's not Injection.
    it's a reflection compliment. Only going to use for walking and such, get those nice 1,000 hour proggys like Ashaman

  3. #103
    Join Date
    Aug 2007
    Location
    Colorado
    Posts
    7,421
    Mentioned
    268 Post(s)
    Quoted
    1442 Post(s)

    Default

    Quote Originally Posted by NKN View Post
    It's not Injection.
    it's a reflection compliment. Only going to use for walking and such, get those nice 1,000 hour proggys like Ashaman
    Aye indeed. Should we follow through on the reflection it will be quite limited, only for what's necessary. As NKN said the main goal is for accurate walking, but we'll probably use it to determine aspects of our in-game player, like health & compass angle / pitch.

    Obviously using reflection is optional.

    Current projects:
    [ AeroGuardians (GotR minigame), Motherlode Miner, Blast furnace ]

    "I won't fall in your gravity. Open your eyes,
    you're the Earth and I'm the sky..."


  4. #104
    Join Date
    Jan 2012
    Posts
    1,104
    Mentioned
    18 Post(s)
    Quoted
    211 Post(s)

    Default

    Quote Originally Posted by luxrath View Post
    What makes simba attractive to me that it is NOT an injection bot. Injection bots always get caught, or the scripter/bot makers steals account info. I have even heard of the bots being made to automatically dump their gathered resources/bank in to the script writers account (via a bot of is own).

    Seriously, dont make Simba in to rsbot 2.0: extra shitty edition
    A color simba script could do this too. The difference between Simba and other bots is - open source. You can have a look at the code before running it.

  5. #105
    Join Date
    Sep 2012
    Location
    Here.
    Posts
    2,007
    Mentioned
    88 Post(s)
    Quoted
    1014 Post(s)

    Default

    Quote Originally Posted by luxrath View Post
    What makes simba attractive to me that it is NOT an injection bot. Injection bots always get caught, or the scripter/bot makers steals account info. I have even heard of the bots being made to automatically dump their gathered resources/bank in to the script writers account (via a bot of is own).

    Seriously, dont make Simba in to rsbot 2.0: extra shitty edition
    Shatter is right, there is no reason a current simba script can't do all this to you as well. The huge difference is how we're open-source and because of that, you can read the code and figure out if that's about to happen to you.

  6. #106
    Join Date
    Mar 2013
    Posts
    67
    Mentioned
    0 Post(s)
    Quoted
    41 Post(s)

    Default

    Quote Originally Posted by Kevin View Post
    Shatter is right, there is no reason a current simba script can't do all this to you as well. The huge difference is how we're open-source and because of that, you can read the code and figure out if that's about to happen to you.
    True true, and most leachers (or at least me and my friends do) skim through and search for telltale signs of malicious code (one from another site even had a "opentrade" procedure at the top, not even trying :v), and watch the script operate for 10-15 minutes attended before letting it go unattended.

    A big difference that you cant really deny between color and injection is that injection bots have an absolutely atrocious ban rate. And if you do reflection, as previously stated, Jagex will change the hooks in no time.

    I still maintain that color is the way forward, and development should focus on refining colorbotting and making it more reliable. That and antiban.

  7. #107
    Join Date
    Sep 2012
    Location
    Here.
    Posts
    2,007
    Mentioned
    88 Post(s)
    Quoted
    1014 Post(s)

    Default

    Quote Originally Posted by luxrath View Post
    A big difference that you cant really deny between color and injection is that injection bots have an absolutely atrocious ban rate. And if you do reflection, as previously stated, Jagex will change the hooks in no time.

    I still maintain that color is the way forward, and development should focus on refining colorbotting and making it more reliable. That and antiban.
    I agree that other botting techniques tend to have higher ban rates... However, that's true for several reasons not entirely dependent on the botting technique.
    1)Simba isn't as popular. You don't start your fight against bots by picking on the little guys, you knock out the big targets first and move your way down.
    2)We have better antiban. By a longshot. It's crazy and there's no reason these other bots don't have it, but they don't. They rarely even have failsafes. I've watched Powerbot's "amazing" USlayer script and it's terrible. Seriously, there are almost no failsafes, it makes weird inhuman decisions all the time, it gets stuck in infinite loops, and it has no sense of breaks or messing around like real people do. And that's supposed to be one of their better scripts. I can barely believe their ban rates aren't even higher! (This is probably the biggest reason for our safety).
    3)Injection does some weird things occasionally that just don't quite happen the same as what a real player even is capable of doing - but that doesn't affect reflection or color bots.

    Jagex can easily change the hooks to stop reflection techniques. But we can also have automatic hook updaters and we won't even have to worry about Jagex trying to stop us with that.

    All that said... We are a color community/bot. We will focus on color techniques, refining and reliability. It's where we will go simply because of who we are. But even with all that in mind, the 07 client is atrocious. Color does not and can not do nearly the same same things as far as walking is concerned. Any other aspect and I think color can handle it, but walking puts us at such a tremendous disadvantage, I support reflection for it. Noone is proposing an entire switch over to reflection, we just want reflection to cover the things color simply isn't quite capable of and even then leave it up to the individual developers for what they wish to do.

  8. #108
    Join Date
    Apr 2013
    Posts
    395
    Mentioned
    1 Post(s)
    Quoted
    177 Post(s)

    Default

    Quote Originally Posted by Kevin View Post
    I agree that other botting techniques tend to have higher ban rates... However, that's true for several reasons not entirely dependent on the botting technique.
    1)Simba isn't as popular. You don't start your fight against bots by picking on the little guys, you knock out the big targets first and move your way down.
    2)We have better antiban. By a longshot. It's crazy and there's no reason these other bots don't have it, but they don't. They rarely even have failsafes. I've watched Powerbot's "amazing" USlayer script and it's terrible. Seriously, there are almost no failsafes, it makes weird inhuman decisions all the time, it gets stuck in infinite loops, and it has no sense of breaks or messing around like real people do. And that's supposed to be one of their better scripts. I can barely believe their ban rates aren't even higher! (This is probably the biggest reason for our safety).
    3)Injection does some weird things occasionally that just don't quite happen the same as what a real player even is capable of doing - but that doesn't affect reflection or color bots.

    Jagex can easily change the hooks to stop reflection techniques. But we can also have automatic hook updaters and we won't even have to worry about Jagex trying to stop us with that.

    All that said... We are a color community/bot. We will focus on color techniques, refining and reliability. It's where we will go simply because of who we are. But even with all that in mind, the 07 client is atrocious. Color does not and can not do nearly the same same things as far as walking is concerned. Any other aspect and I think color can handle it, but walking puts us at such a tremendous disadvantage, I support reflection for it. Noone is proposing an entire switch over to reflection, we just want reflection to cover the things color simply isn't quite capable of and even then leave it up to the individual developers for what they wish to do.
    This is exactly what I want.

    If you start trying to script for 07 scape, you will be die-ing for Reflection to walk for you.

    Flight and the others that are implementing the Reflection on Smart should give us an update from time to time. I am very excited and have very high expectations of this being a success, came back to the thread to see if there's an update every day lol.

  9. #109
    Join Date
    Aug 2007
    Location
    Colorado
    Posts
    7,421
    Mentioned
    268 Post(s)
    Quoted
    1442 Post(s)

    Default

    For the sake of not quoting large blocks of text I'll just say this: luxrath, you make great points and I'm fully in agreement with you for keeping a strong sense of security not matter what you're using, even Simba/SMART/SRL/scripts. I have absolute faith in all of the above but even then I encourage all users to look into these things, at least to get a fair understanding of them enough to know that they're safe.

    And Kevin you explained it just right, nicely put mate.

    It's not so much the client/bot that will get you banned, it's the scripts themselves, as Kevin pointed out. We're superior to the others because we've been doing this before they even knew RS existed. For years and years SRL has changed parallel with RS, we know what is safe and what's not, we can mimic an average player down to the finest details that you simply will never find in any other bot. We're smart about how stay under the radar and this is reflected in our includes and scripts. So it's not the bot that makes you detectable, it's how you use it.

    @Haxz : We're at a stand-still at the moment as SMART, from what I can tell, does not yet have reflection fully implanted. I can't go much further myself so I'm waiting to see where Ben goes with this, if he continues or not. There's also always Brandon's work on his custom SMART that we could always work with. But while it's out of my control to move forward with reflection I'll still continue to work more with our available color-based walking methods, like SPS. At this point we can only advance in progress, we can never lose knowledge we have now so might as well try to make what we have better; keep building.

    Current projects:
    [ AeroGuardians (GotR minigame), Motherlode Miner, Blast furnace ]

    "I won't fall in your gravity. Open your eyes,
    you're the Earth and I'm the sky..."


  10. #110
    Join Date
    Sep 2010
    Posts
    5,762
    Mentioned
    136 Post(s)
    Quoted
    2739 Post(s)

    Default

    Quote Originally Posted by Flight View Post
    For the sake of not quoting large blocks of text I'll just say this: luxrath, you make great points and I'm fully in agreement with you for keeping a strong sense of security not matter what you're using, even Simba/SMART/SRL/scripts. I have absolute faith in all of the above but even then I encourage all users to look into these things, at least to get a fair understanding of them enough to know that they're safe.

    And Kevin you explained it just right, nicely put mate.

    It's not so much the client/bot that will get you banned, it's the scripts themselves, as Kevin pointed out. We're superior to the others because we've been doing this before they even knew RS existed. For years and years SRL has changed parallel with RS, we know what is safe and what's not, we can mimic an average player down to the finest details that you simply will never find in any other bot. We're smart about how stay under the radar and this is reflected in our includes and scripts. So it's not the bot that makes you detectable, it's how you use it.

    @Haxz : We're at a stand-still at the moment as SMART, from what I can tell, does not yet have reflection fully implanted. I can't go much further myself so I'm waiting to see where Ben goes with this, if he continues or not. There's also always Brandon's work on his custom SMART that we could always work with. But while it's out of my control to move forward with reflection I'll still continue to work more with our available color-based walking methods, like SPS. At this point we can only advance in progress, we can never lose knowledge we have now so might as well try to make what we have better; keep building.
    Quote Originally Posted by flight
    this is reflected in our includes and scripts.
    I sure how it's reflected wink wink

  11. #111
    Join Date
    Apr 2013
    Posts
    395
    Mentioned
    1 Post(s)
    Quoted
    177 Post(s)

    Default

    Quote Originally Posted by Flight View Post
    For the sake of not quoting large blocks of text I'll just say this: luxrath, you make great points and I'm fully in agreement with you for keeping a strong sense of security not matter what you're using, even Simba/SMART/SRL/scripts. I have absolute faith in all of the above but even then I encourage all users to look into these things, at least to get a fair understanding of them enough to know that they're safe.

    And Kevin you explained it just right, nicely put mate.

    It's not so much the client/bot that will get you banned, it's the scripts themselves, as Kevin pointed out. We're superior to the others because we've been doing this before they even knew RS existed. For years and years SRL has changed parallel with RS, we know what is safe and what's not, we can mimic an average player down to the finest details that you simply will never find in any other bot. We're smart about how stay under the radar and this is reflected in our includes and scripts. So it's not the bot that makes you detectable, it's how you use it.

    @Haxz : We're at a stand-still at the moment as SMART, from what I can tell, does not yet have reflection fully implanted. I can't go much further myself so I'm waiting to see where Ben goes with this, if he continues or not. There's also always Brandon's work on his custom SMART that we could always work with. But while it's out of my control to move forward with reflection I'll still continue to work more with our available color-based walking methods, like SPS. At this point we can only advance in progress, we can never lose knowledge we have now so might as well try to make what we have better; keep building.
    Sad to hear. Hope Ben will come back soon. Every single one of my script idea failed due to walking

  12. #112
    Join Date
    Nov 2011
    Posts
    1,589
    Mentioned
    9 Post(s)
    Quoted
    17 Post(s)

    Default

    Hey long time since I've been here
    Reflection is a useful thing, back when TRiBot for 07 was just starting out all it had was Colour and tiles walking it made scripts relatively easier to code. So for simba Rs07 I think it'll be a good improvement and give great reliability.
    If your not a fan just don't use scripts that have it. (Although I can see most of them will turn to it.)

    Mat



    ^^

  13. #113
    Join Date
    Nov 2011
    Location
    United States
    Posts
    815
    Mentioned
    6 Post(s)
    Quoted
    284 Post(s)

    Default

    Ive never had trouble walking before, Only reason I would use reflection is for looting items that are in the same color background as the item.

  14. #114
    Join Date
    Sep 2010
    Posts
    5,762
    Mentioned
    136 Post(s)
    Quoted
    2739 Post(s)

    Default

    Quote Originally Posted by Itankbots View Post
    Ive never had trouble walking before, Only reason I would use reflection is for looting items that are in the same color background as the item.
    You have never had trouble walking in osr...? (1-3 clicks doesn't count)

  15. #115
    Join Date
    Feb 2006
    Location
    Berkeley, CA
    Posts
    1,837
    Mentioned
    52 Post(s)
    Quoted
    60 Post(s)

    Default

    Quote Originally Posted by Flight View Post
    I'm just trying to understand it and get anything to work. :/ I'll worry about that later.

    On a related note, I had to add return types to the reflection-related functions in SmartRemote.H. @BenLand100: Is there a reason why none of these functions returned anything? I changed them up to this, can you tell me if these are correct? (I edited these in the style of the reflection functions in the old SMART)

    Code:
    (char*)"exp_getFieldObject", (char*)"function SmartGetFieldObject(objref: integer; path: string): integer;",
        (char*)"exp_isPathValid", (char*)"function SmartIsPathValid(objref: integer; path: string): boolean;",
        (char*)"exp_getFieldBoolean", (char*)"function SmartGetFieldBoolean(objref: integer; path: string): boolean;",
        (char*)"exp_getFieldLongH", (char*)"function SmartGetFieldLongH(objref: integer; path: string): integer;",
        (char*)"exp_getFieldLongL", (char*)"function SmartGetFieldLongL(objref: integer; path: string): integer;",
        (char*)"exp_getFieldInt", (char*)"function SmartGetFieldInt(objref: integer; path: string): integer;",
        (char*)"exp_getFieldShort", (char*)"function SmartGetFieldShort(objref: integer; path: string): integer;",
        (char*)"exp_getFieldFloat", (char*)"function SmartGetFieldFloat(objref: integer; path: string): extended;",
        (char*)"exp_getFieldDouble", (char*)"function SmartGetFieldDouble(objref: integer; path: string): extended;",
        (char*)"exp_getFieldByte", (char*)"function SmartGetFieldByte(objref: integer; path: string): string;",
    I believe I was either wrong with those or wrong actually using the function as I get an error "Error: Could not call proc at line...". I tried these 3, perhaps you could point out where I'm going wrong at:
    Simba Code:
    SmartGetFieldInt(-1, 'hw.client');
    SmartGetFieldInt(0, 'hw.client');
    SmartGetFieldInt(1, 'hw.client');

    This is using your SMART 8.1 with the reflection backbone you added about a month ago, loaded in Oldschool RS. I believe that hook is correct but even if not it would be unrelated to my error.


    Edit:
    Ok now I have all of the hooks for the current OSR client revision. I did a lot of digging through some other client that hosted the most recent hooks on their site; they sure went through a lot of trouble to keep these hidden...
    You're right about the function arguments and Brandon was right about adding them to the exports. What happened was I got bored on a 5 hour flight to California and did some dev work on adding reflection back in, but then the flight was basically over and I never had a large chunk of time to devote to it again. Really, I think the hard parts are "done" but the kinks need to be worked out. The access violation you got was probably related to me fucking up how I passed arguments over the shared memory or something along those lines. I may, at some point, have a chance too look at it again, but I wouldn't hold your breath. If you can fix the reflection problems and submit a pull request, I'll probably accept it, unless the code is just terrible. I don't see how it could be though, since I basically did the framing and just the details need to be worked out.

    E: The process goes like this
    1) Simba invokes the native exp_* method in the plugin
    2) Arguments get coppied into the shared memory
    3) The ID of the function is sent over a socket to the SMART process (callClient invoked)
    4) The SMART process copies the arguments out of the shared memory
    5) The function with the given ID is invoked in the SMART process
    6) The actual work is done (I *believe* this part is fine, should be the same as older versions)
    7) SMART process function returns, result coppied into shared memory (usually on top of the old arguments)
    8) Function ID is sent back over socket to Simba process (callClient returns)
    9) Native exp_* method copies the result out of the shared memory and returns to Simba

    Needless to say, there are a million things that could go wrong. I would initially suspect problems related to shared memory / function ID mismatches. On top of that, I didn't check *any* of the code I comitted to github yet because it's not at a testable stage, really.

    p.s. if you need to bug me for details, it's easy enough to catch me on IRC

  16. #116
    Join Date
    Feb 2011
    Location
    The Future.
    Posts
    5,600
    Mentioned
    396 Post(s)
    Quoted
    1598 Post(s)

    Default

    :O Ben you're alive! Yeah I'll upload to git or send a pull or something in a sec (in reply to that other thread I got tagged in).




    @Flight; No those exports aren't correct. I know Ben said that and he's right but to be exact, there is a size difference and it matters "somewhat". For example, if I exported a GLHook proc as extended instead of single, it would crash the program or return weird results and at times it'd return nothing (Happened already )..

    The reason is because of the difference in size/bytes..

    Ex:

    C++ Float = PS Single.
    C++ Double = PS Double. 8bytes.
    C++ string/char* = PS string/PChar.
    C++ does not have extended type which in pascal is 10 bytes..

    char is not exported as string.. Those are different.

    A string is a POINTER to an array of chars. A char in C++ is a char in Pascal script. Both as 1 byte in size and have the same range.


    You can see the difference:

    PS: http://www.den4b.com/wiki/ReNamer:Pascal_Script:Types
    CPP: http://msdn.microsoft.com/en-us/libr...(v=vs.80).aspx

    My Cpp Table (half-way on the page): http://brandon-t.github.io/ArtOfCPlusPlus/Cpp02.html


    All in all:


    C++ Code:
    extern "C" void* exp_getFieldObject(void* obj, char* path);
    extern "C" bool exp_isPathValid(void* obj, char* path);
    extern "C" bool exp_getFieldBoolean(void* obj, char* path);
    extern "C" unsigned int exp_getFieldLongH(void* obj, char* path);
    extern "C" unsigned int exp_getFieldLongL(void* obj, char* path);
    extern "C" int exp_getFieldInt(void* obj, char* path);
    extern "C" int exp_getFieldShort(void* obj, char* path);
    extern "C" double exp_getFieldFloat(void* obj, char* path);
    extern "C" double exp_getFieldDouble(void* obj, char* path);
    extern "C" char exp_getFieldByte(void* obj, char* path);

    (char*)"exp_getFieldObject", (char*)"function SmartGetFieldObject(objref: integer; path: string): Integer;",
    (char*)"exp_isPathValid", (char*)"function SmartIsPathValid(objref: integer; path: string): boolean;",
    (char*)"exp_getFieldBoolean", (char*)"function SmartGetFieldBoolean(objref: integer; path: string): boolean;",
    (char*)"exp_getFieldLongH", (char*)"function SmartGetFieldLongH(objref: integer; path: string): Cardinal;",
    (char*)"exp_getFieldLongL", (char*)"function SmartGetFieldLongL(objref: integer; path: string): Cardinal;",
    (char*)"exp_getFieldInt", (char*)"function SmartGetFieldInt(objref: integer; path: string): Integer;",
    (char*)"exp_getFieldShort", (char*)"function SmartGetFieldShort(objref: integer; path: string): Integer;",
    (char*)"exp_getFieldFloat", (char*)"function SmartGetFieldFloat(objref: integer; path: string): Double;",
    (char*)"exp_getFieldDouble", (char*)"function SmartGetFieldDouble(objref: integer; path: string): Double;",
    (char*)"exp_getFieldByte", (char*)"function SmartGetFieldByte(objref: integer; path: string): char;"

    C++ Code:
    EXPORTS
        GetPluginABIVersion
        GetFunctionCount
        GetFunctionInfo
        exp_clickMouse
        exp_clickMousePlus
        exp_getDebugArray
        exp_getImageArray
        exp_getMousePos
        exp_getRefresh
        exp_holdKey
        exp_holdMouse
        exp_holdMousePlus
        exp_isActive
        exp_isBlocking
        exp_isKeyDown
        exp_moveMouse
        exp_releaseKey
        exp_releaseMouse
        exp_releaseMousePlus
        exp_isMouseButtonHeld
        exp_sendKeys
        exp_setDebug
        exp_setTransparentColor
        exp_setGraphics
        exp_setRefresh
        exp_windMouse
        exp_setEnabled
        exp_pairClient
        exp_killClient
        exp_getCurrent
        exp_spawnClient
        exp_getClients
        exp_clientID
        exp_getFieldObject
        exp_isPathValid
        exp_getFieldBoolean
        exp_getFieldLongH
        exp_getFieldLongL
        exp_getFieldInt
        exp_getFieldShort
        exp_getFieldFloat
        exp_getFieldDouble
        exp_getFieldByte
        EIOS_RequestTarget=EIOS_RequestTarget@4
        EIOS_ReleaseTarget=EIOS_ReleaseTarget@4
        EIOS_GetTargetDimensions=EIOS_GetTargetDimensions@12
        EIOS_GetImageBuffer=EIOS_GetImageBuffer@4
        EIOS_UpdateImageBuffer=EIOS_UpdateImageBuffer@4
        EIOS_GetMousePosition=EIOS_GetMousePosition@12
        EIOS_MoveMouse=EIOS_MoveMouse@12
        EIOS_HoldMouse=EIOS_HoldMouse@16
        EIOS_ReleaseMouse=EIOS_ReleaseMouse@16
        EIOS_IsMouseHeld=EIOS_IsMouseHeld@8
        EIOS_SendString=EIOS_SendString@16
        EIOS_HoldKey=EIOS_HoldKey@8
        EIOS_ReleaseKey=EIOS_ReleaseKey@8
        EIOS_IsKeyHeld=EIOS_IsKeyHeld@8


    Works for me :l
    Last edited by Brandon; 06-06-2013 at 03:34 AM.
    I am Ggzz..
    Hackintosher

  17. #117
    Join Date
    Aug 2007
    Location
    Colorado
    Posts
    7,421
    Mentioned
    268 Post(s)
    Quoted
    1442 Post(s)

    Default

    Thank you for the advice Brandon, that makes sense and it's nice to know that it was a mistake I made. I'll add them to your client and see how far I can get this afternoon.

    Current projects:
    [ AeroGuardians (GotR minigame), Motherlode Miner, Blast furnace ]

    "I won't fall in your gravity. Open your eyes,
    you're the Earth and I'm the sky..."


Page 5 of 5 FirstFirst ... 345

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •