I have just created my first script! I am making this post primarily to have other scripters give me feedback on my code in general. Specifically, I am looking for comments about my ABC2 implementation as well as my TRiBot API usage, and whether I could be doing things better with regards to either. But any advice is welcome.
One thing in particular I am not quite proud of is how I determined what is "open ground". I have looked at other firemaker scripts that I could find and they seemed to be doing it in much the same way. I tried to come up with a more elegant, robust, and all together decent solution but after a while I just wanted to get a working script and start getting feedback.
For those of you who aren't scripters and would just like to try the firemaker in order to help me bug test, YOU HAVE BEEN WARNED, it has NOT been tested very thoroughly nor am I at all an experienced scripter and as such, I can not speak as to how well I have implemented anti ban techniques.
That being said, if anyone would like to test my script and find bugs or behavior that should be changed, you are more than welcome to. Please include the client log along with your bug report, as I have made the script quite verbose intentionally, at least for now.
Firemaker.java See Firemaker2.java below for most recent version
EDIT: I have taken the advice of some of the comments below, namely @warfront1 advice regarding making the script more state oriented. Below is a pastebin link for my second iteration of my firemaker script.
My name is Ulsting, I just recently graduated with a BS in Computer Science. I am new to TRiBot and scripting in general but I am looking to learn the API and produce a few free public scripts on the TRiBot website so that I can apply to be a Premium Scripter.
If you have any ideas for scripts that you would like to see created, and are okay with them being public and free via the TRiBot platform, then please post those ideas below.
I will be choosing at least three of the proposed scripts to create. I will choose them based on these factors:
Scripts that would require me to learn things I am not already familiar with in the TRiBot API I know this is pretty ambiguous to anyone that isn't me but if your script does something or requires a certain approach that is not mainstream I think exploring and developing that would be worth my time Scripts that will be able to showcase my all around competency as a scripter when applying for the position of Premium Scripter Things like implementing ABC Anything that requires more complex logic or executing a strict yet random set of events Scripts that are sufficiently complicated yet do not greatly exceed the average complexity found in other free scripts Any scripts that I feel are too complicated for the free script platform or that I am just not ready to create yet I will definitely consider making when/if I am a Premium Scripter either as public or private scripts.
Thank you for your suggestions! =)
This release will:
Fix Settings UI placement bug
Fix game object location bug
Fix small layout bug making the client shift up and down
Fix client crashing bug where loading the client with a small display area will cause the client to crash
Fix annoying Linux bug relating to painting events and peers
Fix settings saving bug where settings are saved to disk more often than they should
Fix RSInterface#isBeingDrawn bug affecting a limited amount of people
Drop Java 1.7 bytecode version for 1.8
Important: Since the downloadable RS client uses Java 7, it will no longer be compatible with Looking Glass. To make up for this, we will add support for using other clients such as RuneLite (at a later date).
This change was necessary to allow us to use Java 8 syntax. It also paves the way for Java 9/10/11 support.
Try our development release by checking "Development Release" on the TRiBot Loader. Note that these new features are currently in beta.
This release features:
Re-sizable mode support for both LG and the regular client
Slightly improved login bot
Removed final access modifiers from API classes
Added RSServer hook wrapper to get the client's cached list of server/world info
[NEW] Bug fix for intelligent banking
[NEW] Improvement to the stability of LG over time
[NEW] Vastly improved the reliability and speed of Screen#getColorAt on both LG and the regular client
[NEW] Fix LG login problems
[NEW] Fixed re-sizable mode container bug
[NEW] Fixed re-sizable mode mouse bug
[NEW] Use of public constants in the Banking API
[NEW] Use of other various constants such as Projection#NULL_PT and Screen#EMPTY_COLOR
More features to come very soon!
Please test it and let us know here if there are any new bugs introduced in this release.
Recently Browsing 0 members
No registered users viewing this page.