Jump to content

FrostBug

Scripter III
  • Posts

    3967
  • Joined

  • Last visited

  • Days Won

    5
  • Feedback

    100%

Everything posted by FrostBug

  1. You should be able to use it just fine; tho it might not be organized optimally (Will be in an "Empty" defined slot, I reckon)
  2. Here you go There's a little guide in the first post
  3. Typecasting the selected item should work fine
  4. You never set the JFrame to be visible Also, EXIT_ON_CLOSE is probably not the default action you want, since this will close the entire osbot client as well
  5. Sorry about your loss Works with image tags on the forums as well , dynamically updating when it loads, so the image always displays the latest data
  6. Well, you can easily debug it. int totalListeners = bot.getMouseListeners().size(); If this is constantly increasing, then you have a memory leak
  7. Well, onPaint is called 60 times per second (or 30, I don't remember). The bot holds a collection of MouseListeners. Each time you register a listener, it's added to this collection. Registering 60 new mouse listeners per second is not only a fairly critical memory leak; but will increase your CPU usage over time, since every single mouse event has to be processed by the constantly growing number of listeners ;o. I'm fairly surprised if you've been able to run it for ~30 minutes without seeing poor performance
  8. Hmm, that's quite unfortunate. Looking thru the related code and your log, I can't really piece together a logical explanation :| Could it be that the world was under DDoS attack? In the first place I find it odd that your client could disconnect, even with the falling rocks in the tunnels, as well as the anti-stuck events. Sorry for your loss; I'll keep snooping around to see if I can pinpoint the cause
  9. You wat? Just making sure here; but you should under no circumstance register the event listener in onPaint :E
  10. Drop by the chatbox if you want help
  11. Your ammo wasn't equipped when you hit "Refresh equipment" during script setup. Make sure they are next time Killcount is configurable. Yes, It'll go to the bank and log out if you run out of iban charges
  12. I'm afraid having the ring as part of your gear setup isn't supported at the moment. Started
  13. Started I typically set trial length based on join date. 24 hours is the max length
  14. The pin random is handled by the client; the only advice I can give is to ensure the pin you've set in your profile is correct. As for clan wars; try to disable roof rendering in your game settings
  15. The exception is telling you that the message of the widget is empty ("" in other words). So you probably have the incorrect widget; or the number was never in the message field of the widget in the first place. Try using the widget value debugger to find the correct widget/field.
  16. Widgets#get(int, int, int) will return null if the widget is not found. So when you call getMessage on a null reference, you get an NPE
  17. I don't think so. Just check your nulls properly and you'll be fine :E
  18. Java is pretty similar to C# actually, so you shouldn't have much trouble 1. To detect user input, you will need to implement the onMessage method in your class that extends Script. Method overriding works the same in Java as it does in C#. The onMessage method will be called whenever a new message (be it a game message or a player message) appears in your chatbox. 2. To parse the inputted string, you could simply break the message into parts. Given your example "!58x2", you could first check if the message starts with "!" ( stringMsg.startsWith("!") ) Then you could proceed to split the remainder of the string on the "x" delimiter, and read each value. To generate a random number, you can use the built in osbot method MethodProvider.random(minValue, maxValue) 3. To let your character write stuff in the chat, you can use the OSBot keyboard API. example: getKeyboard().typeString("You rolled a " + num); Note that the getKeyboard method is located in the MethodProvider class, so it may only be used from the Script class, since Script inherits from MethodProvider
  19. The NPE is probably thrown in your getState method when the widget is unavailable.
  20. Version 1.4.3 - Updated trident attack styles to work with defensive casting again (After yesterdays update)
  21. Probably neither. Judging by the error, it looks like one or more of your equipment configurations are unset or contain errors. Please try going thru your equipment configuration for every brother + tunnel creeps, and try again
  22. Wut... did you set up a packet filter just for that ?
×
×
  • Create New...