heh, it's ok to be random.  That's my normal state of mine.  Thanks for coming by!

Hey RD, welcome.  Yeh, SMF is pretty cool. 

Rofl.  Welcome back.  Hopefully this place will be around for a while.

;=================================================================
; Script Name: TrailMyx's Advanced Journal Scanner
; Author: TrailMyx
; Version: 1.0
; Shard OSI / FS: OSI / FS?
; Revision Date: 10/20/2007
; Purpose:
;   Use these subs to quickly find text in your #journal entries.  These subs
; use #jindex for flawless journal scanning and is much more reliable than using
; standard indexing of #journal and #SYSMSG.
;
;   Now it is possible to manage separate journals based on unrelated text.  It's now possible
; to monitor spellcasting, bandaging, stealing, or anything else without a TM_AdvJournalSync
; potentially removing text needed for another UO funciton.
;
;   New is the ability to either gosub or call these functions without the need to change the
; header!  When calling, a limit of 10 arguments is allowed, but more can be added by editing the
; call interface section.
;
;  Examples:
;     gosub TM_AdvJournalSync speech 100 ; sync "speech" journal space, set #LPC to 100 from default of 1000
;     gosub TM_AdvJournalScan speech VALID Find_this_text and_find_this_too ; will not advance copy of #jindex
;     gosub TM_AdvJournalScan heal VALID_ADVANCE you_heal_what that_patient_is_not ; advances pointer after scan
;     gosub TM_AdvJournalScan spellcast NONE fizzle ; no spam checking and doesn't advance #jindex copy automatically
;
;  Subs included:
;     TM_AdvJournalSync - Must call this in initialzation
;     TM_AdvJournalScan - see header for details....
;
;  Release history:
;    v1.0 - Initial release.
;
;  Requirements:
;    Nothing special
;
;  Credit:
;    If you use these subs, please leave credit for me somewhere in your script header.
;=================================================================

... Snipped from another thread...

By this example:

gosub TM_AdvJournalScan heal VALID_ADVANCE you_heal_what that_patient_is_not

The first argument "heal" what you are calling this particular journal scanner.  Since you can have different scanners looking for different things and behaving differently, then you can set this.  An example of multiple journal scanners is perhaps you are looking for journal information that's spell casting related, but another part of your script is looking for journal output that's healing related.  Now you can separate these.

The second argument can be the following values:

NONE: defaults to basic journal scan (no SPAM checking, no #jindex pointer copy advancing)
ADVANCE: no spam checking, advances #jindex copy
VALID: invokes SPAM filtering, no advance of #jindex copy
VALID_ADVANCE, VALIDADVANCE, ADVANCE_VALID, etc.: invokes SPAM filtering, advances of #jindex copy

arguments after the first and the second are considered strings you will be searching for to appear in your journal.

About SPAM filtering:

With the NONE option, the script will not filter the journal and will agree with any resulting match with the list your supply as arguments.  

With the VALID option, the script will compare several criterion to the text found within your journal.  These criteria are:
(Joe_Spammer is a fictional grief player trying to mess with your script)

1) Journal entry does not contain ":_" i.e. "Joe_Spammer:_you_heal_what" <will not trigger>
2) Journal entry does contain ":_", but is the first text <this will pass, example boat commands, taming>
3) Journal entry does contain "Your_Charname:_you_heal_what..." <this will pass, since YOU said it.>
4) Journal entry does contain "Joe_Spammer:_Your_Charname:_you_heal_what" <this will not pass because your character name did not come first>

Note there are combinations of the above examples, and may require you to play with it a bit.

With the ADVANCE option, the script will automatically sync the jindex copy when you do a search.  There are times however when you might want to search the same journal information again for another trigger word, so you can sync by hand by:

gosub TM_AdvJournalScan heal VALID you_heal_what that_patient_is_not
if #RESULT = #TRUE
{
  gosub TM_AdvJournalSync heal
  .. do something about it..
}

Finally, you notice that most of my scripts will call TM_AdvJournalSync at the beginning of the script execution for each journal scanner, but will include a number for the second argument:

 gosub TM_AdvJournalSync heal 100
  gosub TM_AdvJournalSync CastSpell 100

This is just setting the default #LPC for each scanner.  If you have time-critical needs, you may invoke faster scanning for subsequent TM_AdvJournalScan calls.

;-----------------------------------------------------------
; Script Name: TrailMyx's Pet Gump Healing
; Author: TrailMyx
; Version: 1.0
; Client Tested with: 5.0.9
; EUO version tested with: 1.5 109
; Shard: OSI, FS
; Revision Date:  3/26/2007
; Public Release: ...
; Global Variables Used: None
; Purpose/Features:
;   This will attempt to pull up your pet's healthbar and heal according to
;   %heal_percentage
;-----------------------------------------------------------

Test code included!

;=================================================================
; Script Name: TrailMyx's HTML journal dump
; Author: TrailMyx
; Version: 1.0
; Shard OSI / FS: OSI / FS?
; Revision Date: 2007/07/09
; Purpose:
; Subs included:
;   Use these routines to dump contents of your journal to an HTML file.
;
;  Release history:
;
;  Requirements:
;=================================================================


;-----------------------------------------------------------
; Script Name: TrailMyx's Smart/Repeating IDOC House Placer v1.6
; Author: TrailMyx
; Version: 1.6
; Client Tested with: 5.0.2
; EUO version tested with: 1.5 106
; Shard: OSI, FS
; Revision Date:  3/17/2007
; Public Release: ...
; Global Variables Used: None
; Global Namespaces used: globalhouseplace
; Purpose:
;   Fast house placement, remembers your house selection for placement retrys.
;

With the invention of the house placement tool, it became almost impossible to repeatedly place a house more than once using a script.  With this script, it will remember what house you tried to place and continue to place it until you stop the script or it places successfully.

This script has the same features of my Simple'n'Easy script, but it learns the housing choice, so you only have to navigate the tool to your housing selection once.  It is also compatible with OSI and RunUO shards (the pixcol of the house placement gump text for these are different)

Also, this script is capable of communicating with my Autolooter 2.0x script.  I will have to adjust this a bit when I finally release the 2.0 version, because this script will run repeatedly until you break.  Not the best thing when you may also want to loot. 

I would recommend you log into the UO test shard to experiment with house placements before you try using any placement script.  It's always best to be prepared!

Enjoy!

TM

;-----------------------------------------------------------
; Script Name: TrailMyx's IDOC Monitor/Looter v1.0c
; Author: TrailMyx
; Version: 1.0c
; Client Tested with: 5.0.2
; EUO version tested with: 1.5 106
; Shard: OSI, FS
; Revision Date:  3/17/2007
; Public Release: ...
; Global Variables Used: None
; Purpose:
;   1) Will watch a house sign for changes to the status and log the
;      progression of the collapse of a house.  This can help increase
;      your chance to be physically available during the collapse since you
;      will know the near exact time when the house changed to IDOC.
;   2) Allow the user to enter a looting profile where individual items
;      can be selected for looting.
;   3) These items can be prioritized into two categories, normal and priority
;   4) Priority items looting attempts are exhausted before proceeding to the
;      normal loot list.
;   5) If an item is found to be out of range, the character will PATHFIND
;      to the item location so a drag may be attempted.
;   6) Loot profile editor allows the user to quickly add/delete items
;      from each looting profile
;   7) These profiles may be saved to a configuration file so a script
;      can be re-started and still have the profile available.  Also, this
;      is useful for when you want to have two or more accounts sharing
;      the same looting profile to increase your chances of accululating the
;      IDOC loot.
;   9) Optimized looter that searches your event pathfind path to be sure
;      you don't pass something else that's on your list.
;  10) Maintain hidden status before and after a looting session and during
;      camping; you have to have hiding greater than 65.0.
;
;  This program wasn't really written to be sub-ed out, so everthing is
;  accessed in std namespace and shared amongst the subs.
;
;-----------------------------------------------------------



What this script does:
1) Monitor a house sign and note when the status changes going from Slightly, Fairly, Greatly and Collapsing.  The time associated with these changes are recorded into a log file.  The logfile also records times at a pre-programmed interval just in case your client crashes; you can at least know what the status of the house was during the time when your client was active.

2) Once the house sign dissappears, the script will start processing the two lists of items you can generate and automatically loot these items on the ground.  You don't have to be within range; the script will move your character to where it finds these items located on the ground.  If you run past something that should be picked up, the script will snag that item before proceeding to the item originally intended.

3) The priority list will be processes first, followed by the normal list of items.
4) Your character can remain hidden before and after the looting process selected by the checkmark.
5) You can save your lists of loot items to a lootfile.  If you want to share this with more than one client, you can increase the odds of snagging the good items!

Enjoy!

TM


This is an update of a very old script I wrote long ago when I was playing on OSI.  I added a nice GUI and loot add/delete function.  The interface is pretty self-explainatory, so just give it a try. 

I have done recent testing on my own RunUO server and I have optimized the loot collection pathing, log file handling and user interface.  Works pretty well now, and should work on OSI just fine.  I haven't run this new looter on a production shard other than my test shard, so any recent feedback would be greatly appreciated.

Also, it should be said that you need to know what's in the house to loot, so the looting part of the script is pointless on OSI and a private house.  (Unless of course you are friended to the house and have access to the front doorsteps. ) The IDOC monitor portion should work fine, however.

Things to remember:

Some items are placed as deed in a house.  So some vet rewards, and other items may not fall to the ground when a house decays.  Most of the time, they just dissappear.

Changes for next version:
 - Add somewhat state to decay range.  Was accidentally deleted at some point.
 - Add check to see if items on list have been re-locked down
 - Add checkmark to allow user to dismount beetle and open pack when house falls.