Everything posted by Token
- Stealth Builder
-
Accounts Section
- Number 1 doger
- Stealth Builder
Yes but I don't know when it goes up- Error with Sockets
A server by definition should have high uptime, not even the runescape game meets a minimum of 99% uptime requirement. Consider writing an actual server application.- Error with Sockets
You are not allowed to host a server in the client, and that doesn't make sense anyway so you don't need it- Stealth Builder
Erm sure but it's not really a trial since the stable version is not on the SDN until release No- Abort offer if it has ... status
I don't see why it's impossible to replace, the id is just one of the many properties a RS2Widget object has. Take a look through all methods, there's at least 10 different ways of identifying a widget and id is only 1 of them (easiest and worst at the same time) https://osbot.org/api/org/osbot/rs07/api/ui/RS2Widget.html eg: filter by actions, filter by position, filter by message, filter by color BUT NOT filter by id. The simple reason behind this is the properties I mentioned are all exposed to the human player, while abstract numbers such as ids and indexes are not visible to normal players, and jagex can change them whenever they want without affecting the legit players. They do this about once a month for the tutorial island widgets just to break all scripts coded by people who use these properties. As for the sleeps, if I ask you why 300 and not 301, and you can't give a serious answer to this, then it is an obviously flawed logic. A better approach would be waiting until something happens aka conditional sleep.- Abort offer if it has ... status
That's 1 of the 2 which makes your code unstable- Abort offer if it has ... status
If you are looking for improvements I guess you could start by removing any constant number that you can't justify ("magic numbers" in programming), I see at least 4 of them in the 2nd method, and another 2 which will make your code unstable- Naming classes
Second one won't even compile, but source code != memory usage- Stealth Builder
Lol Still waiting on approval- Ban timers
They are manually unbanned just the way they were manually banned- How did you learn to put all your knowledge together?
Create something, anything, even if it takes only 1000 lines of code it's better than reading some book (or going to school)- The result of 17 years of engineering at its finest.
Is it edible- Stealth Builder
- Stealth Builder
It's just pending approval for now, no point giving trials on a version that is not stable...- Stealth Builder
Not giving trials until the script is actually released as I don't see the point anymore, I needed testers not goldfarmers- Stealth Builder
- Stealth Builder
- Stealth Builder
Alright thanks I'll check them out These aren't really trials because the script is in beta phase (not stable) and I'm only looking for bug reports right now- Stealth Builder
Try again, I believe the server was offline- Stealth Builder
- interact() weird behavior
I'm not exactly sure what "this" refers to in your first snippet so I can't help you with that but when you call interact() on anything, an InteractionEvent instance is created with a default threshold of 5 attempts so it may execute the same action up to 5 times and it's equivalent to InteractionEvent e = new InteractionEvent(someEntity, someAction); e.setCameraDistance(14); e.setHover(false); e.setMaximumAttempts(5); e.setOperateCamera(true); script.execute(e); In java we use the equals() method to compare 2 non-primitives like String instances so your condition should be @Override public boolean condition() throws InterruptedException { return script.inventory.getItemInSlot(27).getName().equals("Jug of water"); } But you should take into consideration this will throw a NullPointerException if there is no item in that slot, eg when you don't have 28 jugs left and you only go to fountain with 20, so maybe this may work better @Override public boolean condition() { return !script.inventory.contains("Jug"); } Also void using any animations as they are not continuous and therefore not reliable (there is a short transition time between animations when the method returns false)- Clients crashing / memory leak
Java allocates a lot of memory on unix systems, so easiest fix is switching to windows if the .118 client didn't fix your memory issues - Number 1 doger