Apaec

Sure - trial started! -Apa Hmmmm, that is very strange indeed. Perhaps an issue with a paint stat then. I'll investigate this. For now, run without the paint, and hopefully I can recreate this issue now. -Apa

All trials activated! Thanks for stopping by. -Apa

Hey, Thanks for letting me know, someone else mentioned a framerate issue too. I'm not entirely sure what is causing this and I haven't been able to recreate this on my end - just to double check, is there anything logged in the console logger? One other thing, does this also happen for you in Stealth injection? Or is it only on mirror mode? -Apa

Sure - trial activated -Apa

Sure - trial started! Have you considered training at sand crabs instead? They're better exp/h and I have a script for them too : https://osbot.org/forum/topic/98799-apa-sand-crabs/ -Apa

Hmm, this is odd. Perhaps a zoom issue? Could you please check if your camera zoom is on the default option? The reason I think this might be the case is because it seems the OSBot API is having difficulty rotating the camera to place the next obstacle in your screen viewport. -Apa

Sure - trial started -Apa

Hey, To make pineapple pizza you have to top pineapple rings onto an already cooked pizza, rather than cooking an 'uncooked pineapple pizza' on a range - this script is a cooker script rather than a cooking script and therefore doesn't these kinds of cooking methods. You can still use the script to turn your uncooked pizzas into plain pizzas though! -Apa

Sure - trial started -Apa

Hey, Unfortunately not. This is something I would like to add in the future. -Apa

Sure - trial started Apa

Sure - trial started -Apa

Hey, Sorry that I didn't get to you in time. I hope the script lives up to expectations! -Apa

Unfortunately not, this script is a `cooker` only! Writing one yourself is a good plan, though I believe there are also a few specific wine making (or even more general `cooking` scripts) on the SDN. Cheers, Apa

Sure - trial started -Apa

Both trials activated thanks for stopping by -Apa

Sure- trial started Apa

Sure -trial started Apa

No worries at all, i've just set you up with a fresh 24h trial Apa

Hey Cheers for taking the feedback on board. Nice one on point 3. As I mentioned before, a nice way to test that you don't have any holes in the journey (and hence places the script could get stuck) is to start the script at various points in-game and seeing if the script can get into the normal flow. As for point 5, yep - that's more or less what I mean. Right now, you are creating your dungeons path each time you enter the method, which is unnecessary as this path is constant. Instead, you could do something like this: List<Position> TELESPOT_TO_DUNGEON = Arrays.asList(new Position(3086, 3488, 0), new Position(3093, 3479, 0), new Position(3094, 3470, 0)); Also, you can add more positions to your path (I like to add every other tile to my paths and I have a script to record such data). As the walkPath method will select the next suitable position from your path (typically, I believe, the furthest point in the path reachable on the minimap), you don't have to worry about the script walking in small increments. As for point 6, local variables e.g. your `telespot_neardungeon` should be camelCase, i.e. `telespotNearDungeon`. That's the only inconsistency with the java conventions that I can see GL! -Apa

Sure thing, trial started! -Apa

Ah, apologies for the delayed reply re. the timings issue. I am currently working on levelling up my test account to access the course, and meanwhile am trying to think of a nice way to incorporate general timing tweaks into the script such that a major overhaul of how obstacles are handled is not needed. Sure, trial started! -Apa

In general, it's best to avoid botting where possible. Alching is something you can do fairly reliably with just an autoclicker, hence my recommendation. (To the best of my knowledge, autoclicking generally results in at most a temporary 'macro minor' ban, whereas botting can result in the permanent 'macro major'). However, this script is quicker to set up, more convenient (you can use your computer at the same time), works with automated breaks, permits the use of different inventory slots for alching (and allows spell filters to be active, etc), and tracks your progress. It's up to you which tool you use; and be sure to keep the risks you are taking in mind at all times!

Hey, This is looking nice! I'm not exactly sure if your conditions cover every case, because I don't know the context of the script. However this is something that you should have a feeling of and something I am sure you can test. A few things to note: All walking events could fail at any point throughout the walk (though this is unlikely). You therefore have to support this, so make sure this is the case. A good way to test this is to start the script at various stages in the journey and see if the script successfully completes the journey (relying on the webwalker as little as possible). getWalking().webWalk() and getWalking().walkPath are both blocking operations; there is no need for a conditional sleep after them. What happens if none of the conditions are met? Checking a Y coordinate like that is a little strange; I would keep things to area checks to make your code more readable! You should pull constants (such as the path) outside of the function. You can also instantiate the ArrayList from an array of positions. Try and stuck to java naming conventions where possible (though this doesn't matter so much, just a nit really). I wouldn't worry about walkPath not being random enough, lots of factors will combine to mean this isn't a problem (e.g. camera angle, network latency fluctuations, clickbox randomisation, etc) Nice one -Apa

Sure - trial activated Apa