-
Notifications
You must be signed in to change notification settings - Fork 67
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Debug functions #1
Comments
Any update about this? trying to make a new gui, but cant find anyway to attach to the paint to the botpanel. same for the paint for on scripts |
I'm pretty sure the debug is attached here, but it has been a bit so I forget as to why they're non-functional. I believe it is due to the bot not actually performing the rendering, but I'm certain if that is the case it is FAIRLY easy to work around. Edit: This is simply where the debugs are loaded on, but that doesnt exactly help you. To clarify, the bot is currently rendering using however RuneLite is doing it. This is because I simply didnt take the time to hook (for lack of a better word) into that and create a fluid way for the API to interact with it. It should be possible to do so, and I will take a go at it tomorrow. |
Okay, so while testing this I came across a far more debilitating issue that prevents me from testing further. Scripts currently don't seem to do anything. This includes painting. |
How did ya draw text to it? |
You're getting scripts made in the testsScript to work and interact with npcs? |
yeay can load script from the testScript folder also .jar and .classes are working for me. interact works, beside that it click to walls ect because the the turnto and onscreen dont work as you know. but having no problems with loading scripts. |
Alright, weirdly enough. Scripts seem to be working, but I have to start the script to login, and then stop it and restart for it to actually execute. That said, I tested whether the script could interact with the panels and client and that seemed to work so after I figure out why the script behaves like that I'll try to make a cleaner solution for drawing on the client. |
good to hear its working for you, would love to see a solution for drawing the debug options. |
Nice work, cant wait for it so i can at least see my mouse position. and if the debugger works it will make it more easy to rewrite the api, have the feeling the is much changed in the past months |
Not completely finished, as I believe some debug functions are still a little broken. Several are working though. Additionally,
You in theory should be able to draw on the screen with a script doing that. |
You are really doing a great job, will try get used to github. so i can make changes also and send pull. |
Thanks! Take your time getting used to it and feel free to make changes and pull requests whenever. I've fixed all the TextEvent debug functions. The PaintEvent ones rely on Calculations which appear to be wrong. Hopefully I'll have that fixed soon as well. |
All debugs work excluding models, webs, and calc test. Mouse can still not be enabled or disable and any debug utilizing models will be broken for now. |
Closed due to changes in GUI, since most were fixed and the GUI is being moved away from this isn't needed anymore. |
Merge pull request #134 from myzsqn/master
The bot debug classes all fail to work correctly. Likely requiring the client panel and such to be drawn and assigned appropriately.
The text was updated successfully, but these errors were encountered: