SolarStrike Software

Line 444 of rom/functions.lua has this: __WPL:setWaypointIndex(__WPL:getNearestWaypoint(player.X, player.Z)); Change to: local wpi = __WPL:getNearestWaypoint(player.X, player.Z); if( wpi == 1 ) then wpi = #__WPL.Waypoints else wpi = wpi - 1; end; __WPL:setWaypointIndex(wpi); That should get you mov...

Of the 4 times I tried it, it only worked 2 times. The 2 times it didn't work it still just stood there.

I've noticed a situation where the bot can get stuck and not be able to continue. It's when you start a fight with a mob and it moves into a position where you are unable to attack it. In this situation the mob will continuously attack you. After awhile the bot notices that it has stopped damaging t...

I've noticed, in some situations, that waypoints get skipped when they shouldn't. I've now done a few tests to see under what conditions this happens. I've found 2. 1st. When you use loadpaths you get a message saying something like "Point #3 is closer than Point #1 so we will start with point ...

svn update is for updating the bot not micromacro. Where did you get your version of micromacro? Is it version 1.0 or newer? If you suspect your micromacro installation try re-downloading from here. http://www.solarstrike.net/downloads.php If it's not micromacro you probably need to provide more inf...

Administrator wrote:

rock5 wrote:If "this makes sense" why didn't you implement it?

I made the change after the last commit, and don't think that small of a chance is worthy of a commit by itself. It'll be in the next revision.

OK. No probs.

So I would change it like this? Sorry its just im not that experience at using this yet. <!-- # 17 --><waypoint x="-15995" z="-834"> if( player.Fights-player.free_counter1 > 380 ) then player.free_counter1 = 0; player.Fights = 0; player:rest(1); loadPaths("37repair.xml"...

getpos.lua doesn't spam. Actually, it uses the same, continuously-updating line the whole time. Ah, that's what \r does. Yeah, that looks much better. Yeah, this makes sense. Actually, it looks like you just left the default start and stop/pause keys (F5/F6). You should set them to 0 to disable the...

Even though getpos.lua is not working I can see from the script that I like mine better. Even though they should do about the same thing, I made a couple of changes, I think that make it better. 1. Mine only displays the co-ordinates if they change, not just spam the same co-ordinates over and over ...

You forget the 'then'.

Doh!

You're probably right. How long has that been there?

Anyway I just tried it and got an error

Hi guys, I just created a simple script to show your current position as you move. Useful when testing your newly created waypoint files. Just run it in another window. When you come to a point in your waypoint file you want to change, just pause your waypoint script, move to the correct position, r...

You should be changing settings.profile.skills.MAGE_LIGHTNING, not the database. If I display settings.profile.skills.MAGE_LIGHTNING it says it's nil. On further investigations it looks as though the skills are stored by number. eg; settings.profile.skills[5] for me is MAGE_LIGHTNING. So to change ...

Just tested it. It works fine. Thank you.

Doesn't seem to work.

Changed database.skills.MAGE_LIGHTNING.MinRange to 0 in the onLoad section of my profile but Lightning doesn't caste when up close.

Any ideas?

I've been trying to figure out how to do this with no success. I'd like to change the minrange value of MAGE_LIGHTING from within my profile. Is there a command to do this or a variable I can change? The reason: Usually the value of 75 is good because Lightning is only really useful to keep mobs fro...

So I take it you'll change it in the next update?

I noticed I've been encountering more and more NPCs with " in their names such as "Anemone" Tadesha. When running createpath.lua and pressing keypad 4 or 5 it creates waypoint entries that wont work. For instance; player:target_NPC(""Anemone" Tadesha"); player:merc...

I am sorry, i forgot to mention that i have completed everything as the tutorial says and i have the code in my waypoint file also. This is my current waypoint file and it should work but after testing it for a few hours my weapon was at 40/111 durability and the bot never started the repair macro ...

Could somebody tell me how the bot calculates the durability and what does 0.9 represent ? 0.9 represents the percentage of the max durability of an item. So if an item has a max durability of 125 and the current durability is 100 then dura will equal 100/125 = 0.8 Also what does this line do ? if(...