SolarStrike wiki - User contributions [en]

RoM Auto repair

2011-08-23T03:26:08Z

Wildfire: /* Use a Durability Based AutoRepair */

= Auto Repair at the merchant NPC =

For using the autorepair ingame, you need normaly to press the 'repair' button. You can install the ingame addon [http://rom.curse.com/downloads/rom-addons/details/streamline.aspx Streamline]. Streamline will automaticly repair if you open a dialog window with a merchant and it will automaticly deliver quests, if you open a dialog with a quest NPC.

You can also do that by using the function:

<source lang="lua">player:merchant( npc_name );</source>

It will try to target the nearest NPC's and find the NPC by name. After that, the bot will open the dialog window, autorepair and buy consumables depending from your profile options. It will also work while using multiple bots.

If you only want to target a NPC and do the further stuff by yourself you can use the function:

<source lang="lua">player:target_NPC( npc_name );</source>

Now you have to create a waypoint file, which leads your character to the repair NPC

e.g. '5-7_bugs_repair.xml'
<source lang="xml"><waypoints>

<waypoint x="-12282" z="11183"></waypoint>
<waypoint x="-12391" z="10982"></waypoint>
<waypoint x="-12529" z="10941"></waypoint>
<waypoint x="-808" z="-6067">
player:merchant("Tracy");
loadPaths("5-7_bugs_repair_back");
</waypoint>
</waypoints></source>
The bot will use the waypoint file '5-7_bugs_repair_back' to find back the way to the original boting place.

You now have to insert some code into your boting waypoint file (in this example into the file '5-7_bugs.xml'), to give the bot the information when to repair.

== Use a Durability Based AutoRepair ==

It could be based on the duration of your items:<source lang="xml"><waypoint x="13752" z="6726">
if( player.free_flag1 == true ) then
player.free_flag1 = false;
loadPaths("5-7_bugs_repair.xml");
end
</waypoint>
</source>

As you see, we don't check the duration directly in the waypoint file. Simply because the duration is dependent from your armor and by that, dependend from your character. Hence we check the duration in our characters profile and set just a flag, if we should go for repairing.

<source lang="xml"><onLeaveCombat>
local dura = inventory:getMainHandDurability();
printf("Durability:%s\n", dura);
if( dura < 90 ) then
player.free_flag1 = true;
end
</onLeaveCombat></source>

== Use a Fight Based AutoRepair ==

It could be fight based:<source lang="xml"> <waypoint x="-12364" z="10939">
if( player.Fights-player.free_counter1 > 300 ) then
player.free_counter1 = player.Fights;
load_paths("5-7_bugs_repair.xml");
end
</waypoint>
</source>

== Use a Time Based AutoRepair ==

Or time based:<source lang="xml"> <waypoint x="-12364" z="10939">
if(player.free_counter1 == 0) then player.free_counter1 = os.time(); end;
if( os.difftime(os.time(), player.free_counter1) > 3600 ) then
player.free_counter1 = os.time();
load_paths("5-7_bugs_repair.xml");
end
</waypoint>
</source>

== Use a Items Based AutoRepair ==

You also can check for an item amount like healing or mana potions. But I would recommend more to use a durability check and by that fill up enough of your potions <source lang="xml"> <waypoint x="-12364" z="10939">
if( 20 > inventory:itemTotalCount(<itemNameOrId>) ) then
load_paths("5-7_bugs_repair.xml");
end
</waypoint>
</source>
Replace <itemNameOrId> with the itemname or item-id of the potions you want to check. Be sure your cached inventory is up to date. See the [http://www.solarstrike.net/wiki/index.php5?title=RoM_Functions#Inventory_and_Item_Functions inventory functions section] for more informatione about that.

== Switch an item ==

Instead of repairing your items, you could also switch a item based on the durabilty:

<source lang="xml"><onLeaveCombat>
local dura = inventory:getMainHandDurability();
printf("Durability:%s\n", dura);
if( dura < 0.9 ) then
inventory:useItem(<itemNameOrId>);
end
</onLeaveCombat></source>
Replace '<itemNameOrId>' with the itemname or itemid of the item you want to equipt. You have to be sure that your [http://www.solarstrike.net/wiki/index.php5?title=RoM_Functions#Inventory_and_Item_Functions inventory is up to date], because the funtion 'inventory:useItem(itemNameOrId);' uses the cached inventory.

You also could combine some of that methods.

= Auto Sell at the merchant NPC =

==General Autosell Options==

There are some expert options for your profile if you want to automatically sell items to the merchant NPC.

<source lang="xml"><option name="INV_AUTOSELL_ENABLE" value="true" />
<option name="INV_AUTOSELL_FROMSLOT" value="61" />
<option name="INV_AUTOSELL_TOSLOT" value="120" />
<option name="INV_AUTOSELL_QUALITY" value="white,green" />
<option name="INV_AUTOSELL_IGNORE" value="Pfeil,Elementar, III" />
<option name="INV_AUTOSELL_TYPES" value="Weapons,Armor,Recipes,Others" />
<option name="INV_AUTOSELL_TYPES_NOSELL" value="Cloth,Cooking" />
</source>

{|
|- style="padding: 8px;" |
| style="width: 200px; border-bottom:1px dotted #000000;" | INV_AUTOSELL_ENABLE
| style="border-bottom:1px dotted #000000;" | Allows you to enable or disable the Auto Sell function. Valid values are true|false.
|-
| style="border-bottom:1px dotted #000000;" | INV_AUTOSELL_FROMSLOT
| style="border-bottom:1px dotted #000000;" | Starting bagslot for autosell. Bag 1 has slots 1-30, bag 2 has slots 31-60, ...
|-
| style="border-bottom:1px dotted #000000;" | INV_AUTOSELL_TOSLOT
| style="border-bottom:1px dotted #000000;" | Ending bagslot for autosell.
|-
| style="border-bottom:1px dotted #000000;" | INV_AUTOSELL_QUALITY
| style="border-bottom:1px dotted #000000;" | Enter the item qualities you want to sell. Recommended value is "white, green" ( white | green | blue | purple | orange | gold).
|-
| style="border-bottom:1px dotted #000000;" | INV_AUTOSELL_IGNORE
| style="border-bottom:1px dotted #000000;" | Enter items names (or parts of the names) or item-Ids (not parts of the tooltip text !), you don't want to sell. You can enter more than one item. Use commata as delimites.
|-
| style="border-bottom:1px dotted #000000;" | INV_AUTOSELL_TYPES
| style="border-bottom:1px dotted #000000;" | Enter the item types you want to sell. You can view a list of the item types in the cache file "cache/itemtypestable.lua" once it has been created. If no types are specified then it will default to selling all.
|-
| style="border-bottom:1px dotted #000000;" | INV_AUTOSELL_TYPES_NOSELL
| style="border-bottom:1px dotted #000000;" | Enter the item types you don't want to sell. This overrides the "INV_AUTOSELL_TYPES" option. So if you set INV_AUTOSELL_TYPES = "Armor" and INV_AUTOSELL_TYPES_NOSELL = "Cloth" then it will sell armor but not cloth armor.
|}

Use the normal 'player:merchant()' function in your waypoint file to autosale your items. The bagslot are starting from the top left with 1, 2, 3, ... in the first row, 6, 7, 8, ... in the second row, ...

==Check Durability and Stats while using Autosell==

You can also check the durability and/or stats of an item while selling it. We need to read the ingame tooltip to check the durability and the stats. That's at the moment not possible by only using the RoMScript() MACRO function. So we need a little ingame addon. That addon is named 'igf' (ingamefunctions). You found that addon in the bot folder 'rom/devtools/'.

'''Please copy the folder 'ingamefunctions' into your RoM installation into the folder '\Runes of Magic\Interface\AddOns' to install that addon. And restart the RoM games client.
'''

<source lang="xml"><option name="INV_AUTOSELL_NOSELL_DURA" value="110" />
<option name="INV_AUTOSELL_STATS_NOSELL" value=" X,XI" />
<option name="INV_AUTOSELL_STATS_SELL" value="IX" /></source>

{|
|- style="padding: 8px;" |
| style="width: 200px; border-bottom:1px dotted #000000;" | INV_AUTOSELL_NOSELL_DURA
| style="border-bottom:1px dotted #000000;" | Items with a durability eq or greater that value will not be sold.
|-
| style="border-bottom:1px dotted #000000;" | INV_AUTOSELL_STATS_NOSELL
| style="border-bottom:1px dotted #000000;" | Items with that text strings in the right tooltip side will not be sold. Caution: It's only a very easy check. So that text strings are checked against the whole right side tooltip text. E.g. if you want to save the stat 'defense', also items with 'magical defense' will not be sold. Not only items with the stat 'defense'. Sry for that. If you set the value 'X', all stats with 'X' wouldn't be sold: 'X', 'IX', 'XI'.
|-
| style="border-bottom:1px dotted #000000;" | INV_AUTOSELL_STATS_SELL
| style="border-bottom:1px dotted #000000;" | By using that items, you could overwrite the 'INV_AUTOSELL_STATS_NOSELL' value. e.g. if you set 'INV_AUTOSELL_STATS_NOSELL'="X" you would not sell 'IX' stats. But if you know set 'INV_AUTOSELL_STATS_SELL="IX" you would sell 'IX' stats and save all other stats with 'X'.
|}

==Debuging Option for Autosell==

You can use the option:
<option name="DEBUG_AUTOSELL" value="true" />
to get some debuging options while using autosell.

Snippets

2011-08-23T01:22:25Z

Wildfire: /* Expirience per Hour */

'''Note:'''

Code posted here is considered Public Domain unless otherwise noted. Be aware of this '''before''' posting your code! You may release your code here only under the following licenses: Public Domain, BSD, GPL, or LGPL.

== Random hash generator ==
'''random_hash(len)'''

'''random_hash()'''

'''Description: '''
Generates a random filled hash containing numbers and (capitol) letters. It will generate and return a hash that is 'len' characters long. If 'len' is not specified, then a 32 character hash will be assumed.

'''Purpose: '''
Random hashes are, often, used in place of passwords. It is considered more secure than storing a reversible hash simply because it cannot be reversed (as it contains no real information). For example, after a successful login, a server might generate a random hash for that specific user. The client (user) will now use the random hash for future authentication instead of the password.

'''License: ''' Public Domain

'''Author: ''' "Elverion"

<source lang="lua">
-- Generates a random hash with the specified length.
-- If length is less than or equal to zero, or unspecified, 32 bytes will be assumed.
function random_hash(len)
if( len == nil or len <= 0 ) then len = 32; end;
local holder = ""; -- a string for holding our hash temporarily

-- create an array of all acceptable characters that can be put in our hash.
local hash_chars = {"0", "1", "2", "3", "4", "5", "6", "7", "8", "9", "A", "B", "C", "D", "E",
"F", "G", "H", "I", "J", "K", "L", "M", "N", "O", "P", "Q", "R", "S", "T",
"U", "V", "W", "X", "Y", "Z"};

for i = 1, len do
local index = math.random(1, #hash_chars);
holder = holder .. hash_chars[index];
end

return holder;
end
</source>

== memory Write String ==
'''memoryWriteString(proc, address, msg)'''

'''Description: '''
Enters a string into memory.

'''Purpose: '''
So strings can be written. Be sure not to write a string that's greater than the strings allocated memory.

'''License: ''' Public Domain

'''Author: ''' "zerosignal"

<source lang="lua">
function memoryWriteString(proc, address, msg)
local l_msg_len = msg:len()
local l_char = nil;
for i=0, (l_msg_len-1) do
l_char = msg:byte(i)
--debug_message("char: " .. l_char);
memoryWriteByte(proc, address + i, l_char)
end
memoryWriteByte(proc, address + l_msg_len, 0)
end
</source>

== Experience per Hour ==

'''Description: '''
Estimates the total experience in a hour. Can be extended for Gold, Kills or anything else.

'''License: ''' Public Domain

'''Author: ''' "Elverion"

<source lang="lua">
local expGained = 0;
local startTime = os.time();
local lastAnnounce = os.time();

local lastTotalExp = 0;
while(true) do
local newTotalExp = memoryReadInt(proc, experienceaddr, experience_offset);
if( newTotalExp > lastTotalExp ) then
expGained = expGained + (newTotalExp - lastTotalExp);
end

-- has 10 seconds elapsed? update the exp/min
if( os.difftime(os.time(), lastAnnounce) > 10 ) then
local timeElapsed = os.difftime(os.time(), startTime);
local expPerMin = 0;
if( timeElapsed == 0 ) then timeElapsed = 1; end; -- prevent division by zero

expPerMin = expGained/(timeElapsed/60.0);
lastAnnounce = os.time();
printf("Exp/min: %0.1f\n" expPerMin);
end

end
</source>

RoM Getting started

2011-08-23T01:17:23Z

Wildfire: /* Run */

'''Requirements:'''

MicroMacro 1.0, which you can get [http://www.solarstrike.net/phpBB3/viewtopic.php?f=6&t=177 here]

You will need rom scripts and put them in micromacro/scripts folder. here is how you get them:

http://rom-bot.googlecode.com/svn/trunk/

== Configure RoM in game ==
In Runes of Magic, hit the 'Escape' button and click 'Interface Options', and be sure to turn on 'Self Cast', 'Click To Move', and 'Auto Loot'.

== Configure the macro ==
'''Important:''' As of revision 524, this step is no longer necessary. The bot can now create it's own macro in the first free available macro or find a previously setup macro. It will no longer accidentally over-write user macros either. It will also setup the actionbar key, using the user specified macro hotkey if available or the first empty key.

----

Create ingame a empty macro at macro slot 1. You do that by:

Press ESC (System-Menu) -> Macros). Then click at the macro slot 1 at the very up left.

[[Image:macroslot.jpg]]

Press the button 'New' -> 'Save'.

Now move (via Drag&Drop) that empty macro to your action bar button with the defined hotkey from your profile (default key is 0).

Please note that for the bot to be able to target npc's you will have to set the target friendly hotkey to " j ".

'''Tipp to avoid missing keypress:'''
If your bot works in the background and you do some writings in a foreground window, your keypress of modifiers (CTRL/SHIFT/ALT) in the editor will be the cause that sometimes the RoM client receive a CTRL+0 instead of a keypress 0 (if 0 is your hotkey for the macro). To avoid that, it is recommendet to take a second action button and also assign your dummy macro to that second button. After doing that assign the hotkey CTRL+0 and ALT+0 to that second button. Also assign SHIFT+0 to the key 2 for your main MACRO button 0. By doing that you can avoid the miss of keypresses.

== Make a path ==
Now you'll need to make a waypoint script. Start MicroMacro and execute the rom/createpath.lua script when prompted. You just walk to each point you want in your waypoint list (try to avoid walking near any trees, fences, steep hills, etc.), and press NUMPAD 1. Once you've made your round (the waypoints should loop back and bring you near the start), press NUMPAD 3. Now type in the name you want to save it as (example: 'boars' would be good enough. Don't include any slashes, and the .xml extension is automatically applied).

== Configure RoM bot ==
Next you must make a profile. Go to the profile directory and make a copy of Default.xml, but rename it to whatever your character name is. It must be exact, but capitalization shouldn't mater. For the waypoint script option, you will apply the '.xml' extension this time.

To see how to configure your bot, go to [[RoM_Configuration|configuration]]

Heres a video tutorial on configuring your bot. [http://www.youtube.com/watch?v=mUe8g4Eplj4 YouTube link]

== Run ==
Run by starting micromacro and typing

rom/bot

To see the bot at full work, create a new character (at best a mage or a priest) at the pioneer village and start the bot with

rom/bot profile:l1-10

Then choose path '1-10Pi../l1t_start.xml' from the list. That will level you the character from level 1 to 10 and after doing that run to Varanas class hall (best works mage, priest and scout ... in that order).

I hope this helps! If you see anything i forgot to tell you about, please add it to this wiki page.