SolarStrike wiki - User contributions [en]

RoM Bot

2012-08-14T18:56:57Z

173.27.241.58:

* [[RoM Getting started|Getting started]] - Download the installation files and run the demo
* [[RoM Configuration|Configuration]] - Configure the RoM bot to your needs
* [[RoM Waypoinf files|Waypoint files]] - Working with waypoint files
* [[RoM Functions|Functions]] - List of functions you can use in your own profile events and waypoint files.
* [[RoM Variables|Variables]] - List of important variables you can use in your own profile events and waypoint files.
* [[RoM Custom Scripting|Examples & Tutorials]] - Learn how to do various tasks with the RoM Bot.
* [[RoM Troubleshooting|Troubleshooting]] - How you can help yourself if you get problems.
* [[RoM FAQ|FAQ]] - For all those overly-common problems or questions.
* [[RoM Bot Events]] - For when you want to develop the perfect profile.
* [[Working with Quests]] - Tips and tricks to make the bot complete daily quests and others.
* [[Addon Repository]] - Listing of RoM bot addons collected from the forums.

'''Other resources:'''
* [http://theromwiki.com/index.php/List_of_Functions API List of Functions]
* [http://theromwiki.com/index.php/List_of_Events API List of Events]
* [http://pwsdb.narod.ru/cyrdos.html Cyrillic->DOS Converter (useful for Russian client fixes)]

RoM Bot

2012-08-14T17:41:21Z

173.27.241.58:

RoM Bot

2012-08-14T17:40:13Z

173.27.241.58: Testing ConfirmEdit Wiki extension

RoM Auto repair

2012-06-01T20:44:10Z

173.27.241.58: Undo revision 1004 by 91.121.152.54 (Talk)

= 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( 90 > dura ) 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( 0.9 > dura ) 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" />
<option name="INV_AUTOSELL_NOSELL_STATSNUMBER" value="2" />
</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.
|-
| style="border-bottom:1px dotted #000000;" | INV_AUTOSELL_NOSELL_STATSNUMBER
| style="border-bottom:1px dotted #000000;" | Items with this number of named stats wont be sold. It doesn't count unnamed stats or stats added to rune slots. Especially useful to avoid accidentally selling your costly stated gear. The default value is '3'.
|}

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.

Working with Quests

2012-05-28T23:12:00Z

173.27.241.58: /* Using RoMBot Functions with Quests */

== Using RoMBot Functions with Quests ==
The number one RoMBot function you are going to need when trying to interact with quest interfaces is the sendMacro function and its relative the RoMScript function; Both of these functions allow the bot to communicate with the Runes of Magic client by running lua code through the in game macro. Functions that you will need will be listed below.

'''RoMScript( _script );'''

Send a macro to the client and execute it ingame by pressing the MACRO hotkey. There are up to 10 return values possible.

'''sendMacro( _script );'''

Same as "RoMScript. Additionally you will see a message in the MM window.

'''getQuestStatus( _questname )'''

This will return the status of the quest. It will return 'complete' if the quest is completed and ready to be turned in, 'incomplete' if you have accepted the quest but haven't

completed it yet and 'not accepted' if you have not accepted the quest. The use of this function requires that the ingamefunctions folder be installed in the games addon folder.

'''player:target_Object(_objname, _waittime, _harvestall, _donotignore);'''

This will target an object similarly to target_NPC but this function has more options to cater for the different behaviors of different objects.

_objname = name or id of object to target. Accepts partial names.(Required)

_waittime = time to wait if the object takes time to open in ms. (Optional, default is 0)

_harvestall = true if you wish to collect all in the immediate area.(Default is false ie. opens/collects only once)

_donotignore = By default, when collecting multiple objects with the _harvestall option, the bot will ignore the current node when searching for the next nearest node so it can quickly move on to the next node while the current one is still disappearing. Set this option to 'true' if you don't want to ignore the current node because it requires more than 1 click to collect it. (Default is false).

Examples:

player:target_Object("Harf Daily Quest Board") -- Targets 'Harf Daily Quest Board' with no wait time afterward.

player:target_Object("Mysterious Mound",3000) -- Target then wait 3 seconds for search to end. Done only once.

player:target_Object("Ranch Hen", 8000, true, true) -- Feed all nearby hens, waiting 8s after each. And do not ignore the current hen when searching for the next closest.