Everything posted by FrostBug
-
Fruity Barrows (Frost Barrows)
Version 1.2.8 - Fixed a mort'ton teleport scroll bug - Added an extra camera check to staircase interaction - Attempted to fix an issue with picking the correct enemy from a pile of barrow brothers
-
Fruity Barrows (Frost Barrows)
You set the gear up properly in the setup user interface. As noted in the OP, all items used by the setup must be worn as you set it up. This includes ammo.
-
GUI not functioning but not giving errors in IDE.
You've defined 2 global variables in GUI: public JComboBox comboBox; public JComboBox comboBox_1; These are un-initialized, thus null. In the constructor, you create 2 new local variables with the same names, but you do not refer the global variables to them. JComboBox comboBox = new JComboBox(); JComboBox comboBox_1 = new JComboBox(); As a result of this, you're getting NPE's thrown in onStart, as you're accessing the uninitialized global variables. onStart however is catching these exceptions for you, so they are never visible to you (other than the message "Error in onStart") Solution: In the constructor; initialize the global variables rather than creating new local ones.
-
Interacting with widget menu?
options.interact() would probably work as well. I think it just clicks the first option if the vararg is empty
- chat down = heartbroken
- chat down = heartbroken
-
Fruity Barrows (Frost Barrows)
You can disable this on your ava device Rip. Guess that didn't work after all then Back to enforced auto-retaliate Please use spoiler tags for huge pastes in the future Thanks. I'm on it. Please use spoiler tags for huge pastes in the future
-
Fruity Barrows (Frost Barrows)
The targeting bug should be patched now with 1.2.7b
-
WTF?
If you get caught a second time, they'll add an additional 10 days, eh? So they're saying you can keep going.. huh..
-
Fruity Barrows (Frost Barrows)
Calm your tits, a simple "This is still an issue in 1.2.7a" would have sufficed. Will take a look when I have time, after work.
-
Fruity Barrows (Frost Barrows)
.. no, it was a bug introduced in 1.2.7 ____ Can anyone confirm if this is still an issue in 1.2.7a?
-
Bug
You need to disable resizable mode on your osrs account. Log into the game normally, go to your settings and set your screen mode to fixed.
-
Fruity Barrows (Frost Barrows)
Which script version was this? (Should be visible in the start of the log for that run). Pushed a small fix for this in 1.2.7a
-
Cat lost his eye - Tried to fix the situation..
lose*
-
Cat lost his eye - Tried to fix the situation..
Hate when I forget where I left my eye
-
When Czar shows you a sneak peak of one of his scripts
- The greatest battle of our time
Ended with victory for the b0g How did that make you feel, @Raflesia ?- every cc when a new update is about to come
Well, it's either Assnerd or Slvr. I'm guessing Slvr- Fruity Barrows (Frost Barrows)
sorry about your loss Glad you liked it; altho the only changes to interaction not listed in the patch notes were some extra checks on the chest interactions :P- Fruity Barrows (Frost Barrows)
Read the FAQ- Fruity Barrows (Frost Barrows)
I'll see if I can reproduce it. Going to be difficult without the exact positions or script states, though. EDIT: should be able to patch it by extending the route path a bit to the west Version 1.2.7 - Fixed an issue with ectophial area detection - Fixed an issue with using multiple mort'ton teleport scrolls - Added new API for detecting the correct brother in a pile of barrow brothers - Removed forced auto-retaliate - Added some extra checks against the option to use killcount gear for tunnel traversal - Fixed an issue with equipment detection after a disconnection - Fixed an issue with getting out of range during the myreque shortcut route- Fruity Barrows (Frost Barrows)
Wouldn't happen to be running in mirror mode, would you? If so, check out the FAQ- Nice main, old acc, log-in name is regular username
25m- none of scrips work.
The error you posted very clearly says that the script itself is outdated. It uses old API that is no longer supported, and thus throws that error. If every script you try to run gives that error, then every script you're trying to run is outdated. If these scripts are still on the SDN despite being outdated, it should be reported in the appropriate forum.- Specter
- The greatest battle of our time