This topic contains 7 replies, has 2 voices, and was last updated by  bagz 6 days, 20 hours ago.
Viewing 8 posts - 1 through 8 (of 8 total)
    • Kilroymcduff Participant
      December 3, 2017 at 12:23 am #30562

      <?xml version=”1.0″ encoding=”iso-8859-1″?>
      <!DOCTYPE muclient>
      <!– Saved on Saturday, December 02, 2017, 11:03 PM –>
      <!– MuClient version 4.94 –>

      <!– Plugin “RepArmor” generated by Plugin Wizard –>

      <muclient>
      <plugin
      name=”RepArmor”
      author=”Khamael”
      id=”79cefed11a8bfcf1934110fe”
      language=”Lua”
      purpose=”Armor Repair”
      save_state=”y”
      date_written=”2017-12-02 23:01:09″
      requires=”4.94″
      version=”1.0″
      >

      </plugin>

      <!– Get our standard constants –>

      <include name=”constants.lua”/>

      <!– Triggers –>

      <triggers>
      <trigger
      enabled=”y”
      expand_variables=”y”
      group=”Armor Repair”
      match=”You finish your work and hold up the fully repaired armor.”
      sequence=”100″
      >
      <send>wear @armor</send>
      </trigger>
      <trigger
      enabled=”y”
      expand_variables=”y”
      group=”Armor Repair”
      match=”You finish your work and hold up the fully repaired container.”
      sequence=”100″
      >
      <send>wear @armor</send>
      </trigger>
      <trigger
      enabled=”y”
      group=”Armor Repair”
      match=”You finish your work and hold up the fully repaired shield.”
      sequence=”100″
      >
      <send>wear shield</send>
      </trigger>
      </triggers>

      <!– Aliases –>

      <aliases>
      <alias
      match=”reparmor *”
      enabled=”y”
      expand_variables=”y”
      group=”Armor Repair”
      send_to=”12″
      sequence=”100″
      >
      <send>SetVariable(“armor”,”%1″)
      Send(“rem %1”)
      Send(“repaira %1″)</send>
      </alias>
      </aliases>

      <!– Timers –>

      <timers>
      <timer second=”30.00″ offset_second=”0.00″ >
      <send>showclan morgukai
      showclan morgukai</send>

      </timer>
      <timer minute=”15″ second=”0.00″ offset_second=”0.00″ send_to=”10″
      >
      <send>clancoms Company announcement, our Station cannot be involved in any battlegroups. Do not battlegroup it.</send>

      </timer>
      <timer minute=”1″ second=”30.00″ offset_second=”0.00″ >
      <send>hum</send>

      </timer>
      <timer minute=”2″ second=”0.00″ offset_second=”0.00″ >
      <send>chitter</send>

      </timer>
      <timer minute=”8″ second=”0.00″ offset_second=”0.00″ group=”BH” >
      <send>endurance</send>

      </timer>
      <timer enabled=”y” minute=”11″ second=”0.00″ offset_second=”0.00″ >
      <send>save</send>

      </timer>
      <timer minute=”13″ second=”0.00″ offset_second=”0.00″ group=”BH” >
      <send>limber</send>

      </timer>
      </timers>

      <!– Variables –>

      <variables>
      <variable name=”armor”>armg</variable>
      </variables>

      </muclient>

    • Kilroymcduff Participant
      December 3, 2017 at 12:28 am #30564

      So, no help file, sorry guys, but I will help you out here.

      The alias for this is “reparmor *”

      * = whatever you are repairing, use a keyword.

      If you have two things with the same name, and they both need repaired, such as “golden band” the best thing to do is to send:

      reparmor gold;reparmor gold

      That’ll remove both pieces and start repairing one. Once the first one is repaired, the script will put it back on. Once it’s back on, send:

      repairarmor gold (still using the golden band as and example in this case)

      Once you finish repairing that, since the variable is still set to “gold,” it’ll put it back on automatically, too.

      Khamael worked on this a while, and did a great job with it. I’m sure there are improvements to be made, but this was good enough for us so we stopped working on it. And I worked on it as in Kham was like “man, this ain’t working for some reason, any suggestions?” and I spitballed at him a bit. All credit goes to him, though, for putting in the work.

    • bagz Participant
      December 4, 2017 at 5:33 pm #30569

      You should edit your OP as it exported more than just this alias in the plugin. Clan related and character emotes are in there.

      I took the liberty copying this into an xml, adding a summary of your second post in as info and removing your timers and variables that you accidently exported.

      added:
      <!– Plugin help –>
      <aliases>
      <alias script=”OnHelp” match=”reparmorhelp” enabled=”y” />
      </aliases>

      to the bottom of the plugin file so when you type ‘reparmor:help’ it will show the contents of the info I added.

      https://www.dropbox.com/s/0mriqi3scfsiugf/LOTJRepairArmor.xml?dl=0

      Also, out of curiousity… What does the @ do in “wear @armor” ? is that another way of calling a variable?

      • This reply was modified 1 week ago by  bagz.
      • This reply was modified 1 week ago by  bagz.
      • This reply was modified 1 week ago by  bagz.
    • Kilroymcduff Participant
      December 4, 2017 at 9:12 pm #30575

      Yeah, @armor is the variable being called on during the command.

      It was my first time using the plugin wizard, so I kinda goofed it up. Thanks for cleaning it up. Also… the variable wasn’t by accident, it’s the only one I have and necessary for this to work.

    • Kilroymcduff Participant
      December 4, 2017 at 9:13 pm #30576

      Here is a cleaned up version for the forums:

      <?xml version=”1.0″ encoding=”iso-8859-1″?>
      <!DOCTYPE muclient>
      <!– Saved on Saturday, December 02, 2017, 11:03 PM –>
      <!– MuClient version 4.94 –>

      <!– Plugin “RepArmor” generated by Plugin Wizard –>

      <muclient>
      <plugin
      name=”RepArmor”
      author=”Khamael”
      id=”79cefed11a8bfcf1934110fe”
      language=”Lua”
      purpose=”Armor Repair”
      save_state=”y”
      date_written=”2017-12-02 23:01:09″
      requires=”4.94″
      version=”1.0″
      >

      </plugin>

      <!– Get our standard constants –>

      <include name=”constants.lua”/>

      <!– Triggers –>

      <triggers>
      <trigger
      enabled=”y”
      expand_variables=”y”
      group=”Armor Repair”
      match=”You finish your work and hold up the fully repaired armor.”
      sequence=”100″
      >
      <send>wear @armor</send>
      </trigger>
      <trigger
      enabled=”y”
      expand_variables=”y”
      group=”Armor Repair”
      match=”You finish your work and hold up the fully repaired container.”
      sequence=”100″
      >
      <send>wear @armor</send>
      </trigger>
      <trigger
      enabled=”y”
      group=”Armor Repair”
      match=”You finish your work and hold up the fully repaired shield.”
      sequence=”100″
      >
      <send>wear shield</send>
      </trigger>
      </triggers>

      <!– Aliases –>

      <aliases>
      <alias
      match=”reparmor *”
      enabled=”y”
      expand_variables=”y”
      group=”Armor Repair”
      send_to=”12″
      sequence=”100″
      >
      <send>SetVariable(“armor”,”%1″)
      Send(“rem %1”)
      Send(“repaira %1″)</send>
      </alias>
      </aliases>

      <!– Variables –>

      <variables>
      <variable name=”armor”>armg</variable>
      </variables>

      </muclient>

    • bagz Participant
      December 5, 2017 at 2:18 am #30579

      those are your local variables though. the plugin can set its own variables.

    • bagz Participant
      December 5, 2017 at 2:18 am #30580

      also your timer is still showing in the OP

      😉

Viewing 8 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic.
Skip to toolbar