Elves get a higher percentage colored ore in addition to an alleged increase in the frequency of the rare gem types.

I will take a look!!

I modified the waypoint recording script to use hashmarks to break up the data points so that I could use TM's string parser to break them up when I pull them into a script.

Then I added a step by step pathfind through the waypoints by modifying the waypoint script, and used that to create a second script that will make files for hatchet/shovel strikes along the waypoint, using a similar naming convention.

I now have a set of scripts that I can use to make rails for mining or lumberjacking. It takes about five minutes to record a decent rail, and another 5-10 to add the shovel/hatchet data points.

Using EN's data file tool I wrote a simple hotkey script to write a rail data file as follows:

Set %Rail_Name SPR1
Set %File_Name %Rail_Name
Set %File_Name_txt %File_Name , .txt
Set %File_Path C:\Users\CRS\Desktop\EUO\
Set %File_Path_And_Name_txt %File_Path , %File_Name_txt
Set %WP_Save WP
GoSub ENs_ClearFile %File_Path_And_Name_txt
Set %X 0
Repeat
      {
      onhotkey f4
      Set %HotKey4 True
      onhotkey f5
      Set %HotKey5 True
      If %HotKey4 = True
         {
         Set %X %X + 1
         Set %WP_Save . %X %WP_Save , %X
         Set %WP . %X X . #CHARPOSX , Y . #CHARPOSY , Z . #CHARPOSZ
         Event exmsg #charid 3 4 %WP . %X
         gosub ENs_SaveData %File_Path_And_Name_txt %WP_Save . %X
         Set %HotKey4 False
         }
      }
Until %HotKey5 = True
Set %WP_Count %X
Gosub ENs_SaveData %File_Path_And_Name_txt WP_Count
Halt

I ran the code, hit F4 four times and then hit F5. The rail file is named SPR1 and looks like this:

; ENs Var Save
Set %WP1 X2164Y2169Z7
Set %WP2 X2164Y2169Z7
Set %WP3 X2164Y2169Z7
Set %WP4 X2164Y2169Z7
Set %WP_Count 4
Next I will add in the character count code.

I did a little more testing with this code and confirmed that you can use a variable in the gosub ENs_SaveData call line.

The tool becomes really flexible once you start using string and apend as it will allow you to pair a sequenced variable with a sequenced variable name (See below). If you run a character counter you can use that as a trigger to use the same process to promote the file name -- so yes, I think we do want a counter sub also.

I broke apart the file path from the file name so that the name could easily be promoted with a trigger from a character count sub.  While is not used in this example, I wanted to show that I had it working to demonstrate that automatically promoting the file name is possible.

My test script looked like this:

Set %Test_Variable Blah
Set %Test_Variable_Save Test_Variable
Set %File_Name Data_test
Set %File_Path C:\Users\CRS\Desktop\EUO\
Set %File_Name_txt Data_test . .txt
Set %File_Path_And_Name_txt %File_Path , %File_Name_txt
goSub ENs_ClearFile %File_Path_And_Name_txt
For %X 1 10
    {
    Set %Test_Variable_Save . %X %Test_Variable_Save , %X
    Set %Test_Variable . %X %Test_Variable , %X
    gosub ENs_SaveData %File_Path_And_Name_txt %Test_Variable_Save . %X
    }
Halt
The data file it created, appeared in my UO file named Data_test.txt  and it looks like this:

Set %Test_Variable1 Blah1
Set %Test_Variable2 Blah2
Set %Test_Variable3 Blah3
Set %Test_Variable4 Blah4
Set %Test_Variable5 Blah5
Set %Test_Variable6 Blah6
Set %Test_Variable7 Blah7
Set %Test_Variable8 Blah8
Set %Test_Variable9 Blah9
Set %Test_Variable10 Blah10
Pretty much exactly what I was looking for EN!!


 

225 quests Yeilded (10,350 residue)

100 110 Scrolls (44%) | combining for 120 imbue scroll
125 105 scrolls (56%) | 6250 cleanup points

4 Chisels: 1 each: Shadow, Copper, Gold, Verite

Your tool kit got me thinking, so figured I would ask!