Describe the solution you'd like
Ability to launch bots from command line

Additional context
This would enable faster launching and more efficient automation.

Is your feature request related to a problem? Please describe.
Currently scripts are a pain to create and test without using --bot-runelite as the program argument and testing in the RuneLiteTestFeatures class.
#25 is an obvious sign of this.

Describe the solution you'd like
A more streamlined method to create scripts for the bot. Probably a wiki page explaining the process to create scripts in this new manner for clarity.

Describe alternatives you've considered
It could probably be done with two projects being opened and having the script creation project be a dependency, but in intelliJ and interacting with RuneLite it could prove problematic to implement in a manner that is intuitive.

BEFORE REPORTING
Ensure RuneLite is up to date in IDE and you are using the latest version of the master branch

Describe the bug
When opening multiple bot instances will render one of them black and unable to be interacted with.

To Reproduce
Steps to reproduce the behavior:

1. Open bot application
2. Click File and then new bot
3. Click the new bot instance

Expected behavior
It should load normally and be visible like the previous bot instance

Screenshots

Desktop (please complete the following information):

• OS: [e.g. iOS]

When thread sleeps are left low in the api they can cause inconsistencies if lag occurs or they simply try acting before a transition has occurred.

Currently each individual client is not masked at all, so the end result would look like us running fifty clients on one computer. If possible we need to develop a method to mask IP addresses. In the past I've managed to add run parameters to the shortcuts and programs to manipulate them into connecting to a proxy server. I'll look into incorporating a past solution similar to this or coding up a method to allow the connection between each client and Jagex' servers to be route-able through a proxy service.

The bot debug classes all fail to work correctly. Likely requiring the client panel and such to be drawn and assigned appropriately.

In methods.menu getMenuX is reflectively gotten, alternatively we'd like to get this value via calculations to remove our need for reflection. As for getMenuY it just needs some refinement as it works fairly well.

Is your feature request related to a problem? Please describe.
The GUI is currently missing icons and it makes the entire application look really bad.
Describe the solution you'd like
Adding icons to match each gui function.

Based off the readme:
--bot-runelite or --runelite should be commands used in Program arguments however both provide me with error:

"Exception in thread "main" joptsimple.UnrecognizedOptionException: runelite is not a recognized option"

It should be noted when using default commands like: --debug --developer-mode and removing the bot-runelite/runlite commands it launches without any issues.

I am adding these arguments to the RuneLite.main() file in the client folder, I have also tried the RuneLite.main() in the rsb ->botLauncher folder with the same results.

Any ideas what I'm doing wrong?

Allow the camera to turn and contort using the mouse or keyboard (allow the decision to be saved as a setting in the login files) This will prevent our bots from having similar move patterns.

https://i.gyazo.com/ee7aaf8ae1165ab21d51a49152b617e2.mp4

If I switch the script to the test script

https://i.gyazo.com/d92f15046cbea11fed113e1ab3dbe0be.mp4

It's something to do with the canvas class; if I find a fix I will post here

**Unofficial Fix - Works for me

Replace your BotHooks#draw method with mine**

@Override
public void draw(MainBufferProvider mainBufferProvider, Graphics graphics, int x, int y) {
    try {


        //Preferably initialize the value of bot with the current bot on screen
       // IE Application.getBot or similar manner.



        if (graphics == null) {
            return;
        }
        // We only want do do this once because this would MASSIVELY affect performance.


        /*
        if (SUPERCLASS_MAP.get(SUPERCLASS_MAP.keySet().iterator().next()) == null) {

            for (Method method : this.getClass().getSuperclass().getDeclaredMethods()) {
                Iterator itr = SUPERCLASS_MAP.keySet().iterator();
                while (itr.hasNext()) {
                    String name = (String) itr.next();
                    if (method.getName().equals(name)) {
                        method.setAccessible(true);
                        SUPERCLASS_MAP.replace(name, null, method);
                    }
                }
            }
            for (Field field : this.getClass().getSuperclass().getDeclaredFields()) {
                Iterator itr = SUPERCLASS_MAP.keySet().iterator();
                while (itr.hasNext()) {
                    String name = (String) itr.next();
                    if (field.getName().equals(name)) {
                        field.setAccessible(true);
                        SUPERCLASS_MAP.replace(name, null, field);
                    }
                }
            }
        }*/

        //We then simply invoke the method as needed here. It should perform similar to how it does in RuneLite
        //final Graphics2D graphics2d = (Graphics2D) ((Method) SUPERCLASS_MAP.get(GETGRAPHICS)).invoke(this,
         //       mainBufferProvider);

        Image image = mainBufferProvider.getImage();
        // finalImage is backed by the client buffer which will change soon. make a copy
        // so that callbacks can safely use it later from threads.
        drawManager.processDrawComplete(() -> copy(image));

        final Graphics2D g2d = (Graphics2D) bot.getCanvas().getGraphics(bot, mainBufferProvider);

        // Draw the image onto the game canvas
        //graphics.drawImage(image, 0, 0, bot.getCanvas());

        g2d.drawImage(image, 0, 0, bot.getCanvas());


    } catch (Exception e) {
        e.printStackTrace();
        //log.warn("Bot hooks failed to paint properly");
    }
}

GrandExchange items can be collected from the bank and just simply has not been implemented yet.

BEFORE REPORTING
Ensure RuneLite is up to date in IDE and you are using the latest version of the master branch

Describe the bug
Currently, the method for getting the selected item in the inventory doesn't appear to return anything besides null.

To Reproduce
Steps to reproduce the behavior:

1. Simply try using the method and watch the return

Expected behavior
It should properly be going through the image and checking the pixels to validate if the item is selected or not.

BEFORE REPORTING
Ensure RuneLite is up to date in IDE and you are using the latest version of the master branch

Describe the bug
Login bot isn't able to log in after the bot is logged out.

To Reproduce

Expected behavior
Should be able to detect the screen it is at and then log back into the game.

Code contains remnants of the massively overhauled code base used to create this. Most of it has been changed and should be updated to reflect said change.
Such changes would include updating comments, class descriptors, variable names, and removing remnant features that are no longer applicable or prepping them for a conversion.

BEFORE REPORTING
Ensure RuneLite is up to date in IDE and you are using the latest version of the master branch

Describe the bug
Because the LoginBot behaves in a dumb manner with literal waits it fails to load properly sometimes.

To Reproduce
Steps to reproduce the behavior:

1. Run bot
2. Run any script with an account set up

Expected behavior
It should log in perfectly every time.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: [e.g. iOS]

Additional context
Preferably checking what screen we are on constantly and performing actions based on the screen similar to what we are currently doing.
Because this is a fairly vital component of testing it should be fixed relatively soon.

#2 #8 Menu bugs are causing the inconsistencies and possible incorrect calculations. Currently if an item like say "chicken meat" is on the entry list and one is searching for entries containing examine and chicken. Instead of the chicken being examined 100% of the time, some results will be for the chicken meat.

BEFORE REPORTING
Ensure RuneLite is up to date in IDE and you are using the latest version of the master branch

Describe the bug
Supposedly interaction with non-game objects (ground, wall, ect) might not be handled correctly or that the way we go about retrieving objects could be invalid due to an assertion in OSRS client.

To Reproduce
Steps to reproduce the behavior:

1. Attempt to access an object with any standard method
   (getNearest(StringName) or getAllAt(RSTile) ect)
2. It should return a null or assert error.

Expected behavior
For the object array to return properly without fail.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: Windows 10

Additional context
Found by @vuurman100

Lacks any actual means of trading, simply a means to initiate the trade.

Needs a method to verify what is being traded to it.
Doesn't need a means to trade items (inventory and doAction("Offer") ect, but should contain methods to interact with the trade items to remove them or update offers perhaps?

Not currently a priority as trading players isn't really needed at the moment.

If the user clicks it disrupts the mouse position as the user click isn't sent to the virtual mouse and can cause bugs when checking for entries that should be directly under the virtual mouse but aren't there leaving a null menuentry object instead.

At a later time, it'd be even more optimal to emulate RuneLite's gui to look even less suspicious.

BEFORE REPORTING
Ensure RuneLite is up to date in IDE and you are using the latest version of the master branch

Describe the bug
Currently in resizable the math doesn't apply for it. The larger the viewport means the more entries can be listed.

I am trying to implent my own gui.

but i am really struggle how the botpanel/bothome are working with the client panel.
Could you help me with make it work? i know i could easy copy/paste most but try to learn something also.

Is there anyway to come in private contact with you? if you are willing to help.

Right now the labels only are applicable to bugs, but enhancements and such should also be applicable with the labels.

Currently the API is outdated and incompatible with RuneLite at the current moment.

Do you have any plans on updating?

Describe the bug
Currently IDs for interfaces may be incorrect, and thus most features may be unusable

To Reproduce
Steps to reproduce the behavior:
Try any script, in --bot-runelite or --bot it should fail

Expected behavior
Literally the expected behavior of the bot

Desktop (please complete the following information):

• Windows 10

Additional context
Ideally updating the IDs would be beneficial and additionally creating a wiki page entry detailing how to do so would benefit anyone wishing to add features.

Propose your question
Scripts under testScript folder not showing up in script selector, am i doing something wrong?

will try to see if i can make a nice gui if i have time

BEFORE REPORTING
Ensure RuneLite is up to date in IDE and you are using the latest version of the master branch

Describe the bug
When setAngle is interrupted it stays in the while loop indefinitely as it is never notified that it isn't turning anymore.

To Reproduce
Steps to reproduce the behavior:

1. Run a script that utilizes the setAngle method
2. Proceed to supply user input to stop it from moving
3. Watch as the bot proceeds to sit indefinitely in an inescapable while loop
4. See error

Expected behavior
Adjusts to handle this interruption

Desktop (please complete the following information):

• OS: Windows 10

Currently, the API uses a poor GUI to display the client and such.
This has introduced a number of issues that could simply be done away with if re-written as well as provide far more functionality.

This will likely take a bit of time (a week or more), but I'll be pushing changes to the wip branch while that takes place.

BEFORE REPORTING
Ensure RuneLite is up to date in IDE and you are using the latest version of the master branch

Describe the bug
Scripts currently aren't executing any code written in them or the getBot function is returning null values.

To Reproduce
Steps to reproduce the behavior:

1. Create any script with code to be executed.
2. Watch it fail to do anything.

Expected behavior
It should execute the code. Additionally, at the moment I am uncertain if the issue lies in the scripts themselves or elsewhere

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: [e.g. iOS]

Additional context
Found while attempting to fix #1
Scripts appear to not be able to interact with any given object after getBot() which results in virtually everything written in them failing to run.

https://github.com/open-osrs/runelite

has more of a open API and you can access the mixins

BEFORE REPORTING
Ensure RuneLite is up to date in IDE and you are using the latest version of the master branch

Describe the bug
The walking module is mostly dysfunctional. For most purposes, it will not run.
This is because the prediction tree and every method involved with it are very much broken since they use collision flags which RuneLite prevents us from using to prevent abuse.

To Reproduce
Steps to reproduce the behavior:
Use any method in the module.

Expected behavior
The module should function.

Additional context
I've already re-created a collision map and I'll begin working on making a maze solver (effectively what a pather is)

Need to create a way for the bots to transfer gold/resources to a mule account for it to store wealth.

Menu entries might be incorrect or not corresponding to the appropriate NPC and can cause inconsistencies and misclicking. #2 might also be related to this behavior.

BEFORE REPORTING
Ensure RuneLite is up to date in IDE and you are using the latest version of the master branch

Describe the bug
GService is blank on creation. This leaves a very ambiguous situation for any script user.
Additionally without the pre-created folders a user won't know where to put scripts.
To Reproduce
Steps to reproduce the behavior:

1. Start the bot
2. Check home_dir\G Service\

Expected behavior
It should auto-generate folders named Scripts, Settings, Logs, Cache
and inside Scripts it should auto-generate folders Precompiled and Source

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: [e.g. iOS]

BEFORE REPORTING
Ensure RuneLite is up to date in IDE and you are using the latest version of the master branch

Describe the bug
It appears as if RuneLite (and likely OSRS) has removed the clan chat tab and other in-game occurrences of clan stuff. So it is very likely the API won't compile currently as we use references to the RuneLite usages.

Expected behavior
The API compiles and executes properly. All references that are invalid need to be removed.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: [e.g. iOS]

Additional context
Add any other context about the problem here.

BEFORE REPORTING
Ensure RuneLite is up to date in IDE and you are using the latest version of the master branch

Describe the bug
Models that contain two renderables will currently never interact with the second renderable
IE WallObjects

Expected behavior
They should be added to the model in some manner so we can interact with that renderable.

Additional context
First noticed here, and fixed most of the model issues. This one won't stop the api from functioning. #48
#52 fixed the api so at least one renderable for any object was used. This prevented nulls. That said we should create a separate object model class for objects with two renderables or something and see if the getModel can incorporate both renderables.

BEFORE REPORTING
Ensure RuneLite is up to date in IDE and you are using the latest version of the master branch

Describe the bug
Currently the turnTo method can turn you to an entity, but leave it just far enough out of vision to not consistently be able to click the model despite it technically being within vision.

To Reproduce
Steps to reproduce the behavior:
For example

1. Go to Grand Exchange
2. Position yourself like in the image
3. Ensure the script is attempting to interact with the Grand Exchange Clerk
4. Watch the API struggle to click on them.

Expected behavior
It should preferably turn to the entity to have more of them in the screen.

Screenshots

Desktop (please complete the following information):

• OS: Windows 10

Additional context
Somewhat related to #17 and #6

Is your feature request related to a problem? Please describe.
Currently, the mouse movements are rudimentary. They lack any real depth in functionality and are probably a big cause of bans.

Describe the solution you'd like
The addition of a humanized mouse movement would be imperative. Ideally, a library likely exists that has utilized a neural net
to analyze data and generate humanized mouse movements. I'd like this to be added.

Describe alternatives you've considered
Obviously, removing the mouse, in general, could work. Perhaps simulating a touch screen. I'd like to add this too.

BEFORE REPORTING
Ensure RuneLite is up to date in IDE and you are using the latest version of the master branch

Describe the bug
Throughout use, the ignored exceptions may result in a freeze or crash

To Reproduce
Hard to reproduce

Expected behavior
No random freezing

Desktop (please complete the following information):
Windows 10

Is your feature request related to a problem? Please describe.
While a mobile bot is out of the question at the moment, simulating touch screens is not.

Describe the solution you'd like
Determine if it is possible to send touch screen like behavior to the game.

When attempting to click on small models it's not uncommon for the bot api to mis-click the model in question

NPC.turnTo() and likely methods.camera.turnTo() are broken and result in an infinite loop causing complete lack of functionality.

Currently we can confirm if something is on screen, but not if we have line of sight of it. We need to likely rework some interactions or add in a check to verify that the object we are attempting to see and interact with is visible to the player. (To prevent clicking through walls or similar consistently)

Is your feature request related to a problem? Please describe.
Currently the ground item will throw an error likely if it can't render the default value being passed.
Was 52, but I'm trying to figure out the render distance

Describe the solution you'd like
A constant or variable that changes based on the client render distance. That way we know how many tiles away we ever render at one time.

Additional context
Add any other context or screenshots about the feature request here.

Set up a network drive between the computers you run the bot off of and store the login state so the computers can run synchronously without overlapping.

The account manager doesn't save passwords without making a second account and then hitting done.

Propose your question
Orientation is listed in numerous places and some are conflicting information.
I doubt the API implementation is wrong, but clarification would be useful.

I'm going under the impression that the one listing 0 as north is possibly outdated/incorrect. A quick search clarifies the wall one (albeit mildly weird).

The manner in which the bot api gets a point of a model lacks any actual randomization as it'll return on the first match it finds. While this is probably to avoid going through the entire array it means that we're going to consistently hit those early values and never hit the later ones.
Additionally the function returns a value even if there is no point on the screen.