Jump to content

FrostBug

Scripter III
  • Posts

    3967
  • Joined

  • Last visited

  • Days Won

    5
  • Feedback

    100%

Everything posted by FrostBug

  1. Sure, I give trials. Let me know when you want one Thanks for reporting it! Do you know if it still works on .77? (Will determine whether the runescape update or the .79 experimental build is to blame)
  2. In other news; It seems there are still some mirror mode bugs that prevent the script from running properly. I will take a look at fixing mirror mode bugs in the coming weekend. So until then, please refrain from using mirror mode.
  3. try this Rectangle bounds = new Rectangle(Whatever bounds you want to crop to on the game screen); int dx1 = bounds.x; int dy1 = bounds.y; int dx2 = bounds.x + bounds.width; int dy2 = bounds.y + bounds.height; int sx2 = bounds.width; int sy2 = bounds.height; g.drawImage(image, dx1, dy1, dx2, dy2, 0, 0, sx2, sy2, null, null); You can calculate the bounding rectangle by having a pre-defined "full" (100%) rectangle, and transform its width according to your percentage variable.
  4. Dev build 2.3.79 is out now; I recommend you guys to try that
  5. Not too sure about the door thing. It would enforce a constant low camera angle, which probably will cause more misclicks on other doors/creeps There already is a Clan Wars route
  6. You've set up your ranged gear incorrectly. As the OP states, you need to be wearing the chosen ammo as you parse the worn equipment. Do that and it should be fine
  7. Seems like the latest Dev build is still 2.3.78; but as soon as it's out. Yes
  8. You should be able to get the button widget by the index of the attack style (eg. child Id 0 for accurate, child Id 3 for defensive), and then interact with the widget.
  9. Your death was most probably caused by the interaction bug. Which will have been fixed now, if it was caused by one of the things that were patched with script version 1.2.10. In addition, @Alek has confirmed that the interaction bug has been patched, and will be available in client release 2.3.79 (in case there are still remaining cases that I've missed)
  10. Alright so I did a 2 hour test just now; but while I couldn't reproduce the bugs you guys have reported; I did make some misc. fixes that could potentially have been to blame for those issues. Version 1.2.10 - Reverted the broken hook temp. solution - Added some more .77 interaction-bug workarounds related to ammo handling and ectophial usage __ As always, the changes have been committed, but needs to be reviewed by the SDN manager before the script version goes live on the SDN
  11. Mirror mode? Please use the bug report template. What position did it stop in, states, etc..
  12. Started a trial Strange, first time I've ever seen this. Did you use different settings than you normally do (kill order for example, or a different 'correct tomb last' setting?) Also, was it actually the correct tomb (for dharok)?
  13. Interpret it as you will. I haven't tried it on the new mirror release yet, but I don't see any reason it shouldn't work anymore. 24 hours
  14. I think mirror client is now at the point where I'll start running tests with this script. I will also start to look into bug reports from mirror client related bugs.
  15. Your memory appears to be completely maxed out (lower right corner). That'll freeze any script. Try allocating it more memory
  16. You can't sort a hashmap.. It's hashed.. A priority queue would be your best bet IMO, depending on the situation ofc. Make a wrapper class to hold your 2 ints, let the wrapper class implement the comparable interface (compare by key value), and they'll be automatically sorted as you insert them into the PQ
  17. Alright, here's what's gonna happen. All of you are gonna restart your scripts right now (hit the refresh scripts button to be sure) And then they're gonna run without any problems! If there are any problems after that, please fill in the bug report template located in the first post. Thanks
×
×
  • Create New...