Jump to content


Photo

GEARSWAP: coding a mythic weapon


    7 replies to this topic

    #1 wickedpriest

    wickedpriest

      Member

    • Members
    • PipPip
    • 24 posts

      Posted 29 December 2014 - 10:19 PM

      I want some code that you can plop into any Gearswap file and make it work with their particular mythic weapon.

       

      I've managed to find this bit of code to show what I'm looking for but I'm still missing the other code to actually make it viable for any mythic weapon. The code telling one to auto weaponskill particularly

       

      windower.register_event('tp change', function(tp)
              if Autows == 1 then
              if not buffactive['amnesia'] then
                  if buffactive["Aftermath: Lv.3"] then
                      if player.tp > 999 and   player.status == 'Engaged' then
                          windower.send_command('input /ws "Tachi: Fudo" <t>')
                      end
                  elseif player.tp > 2999 then
                      windower.send_command('input /ws "Tachi: Rana" <t>')
                  end
              end
          end
      end)
      

      -----------

       

       

      I have a Yagrush and a carnwehan I want to work as above. simply flopping it into their files and changing the namesdoes not work. and I have no idea how to setup autows....

       

      There are mentions and whispers and fragments of this being viable but have not been able to see an actual file produced that has this within it. Please help. thanks!



      #2 Arcon

      Arcon

        Advanced Member

      • Windower Staff
      • 1189 posts
      • LocationMunich, Germany

      Posted 29 December 2014 - 10:57 PM

      This is something that does not really belong into GearSwap. Here's how simple it is in a standalone addon:

       

      windower.register_event('tp change', function(tp)
          if tp >= 1000 then
              windower.send_command('input /ws "Fast Blade" <t>')
          end
      end)

       

      Can add any further rules as you see fit. Or, if you don't need any fancy rules, load AutoExec and write this line:

      //ae register tp_1???|tp_2???|tp3000 input /ws "Fast Blade" <t>



      #3 wickedpriest

      wickedpriest

        Member

      • Members
      • PipPip
      • 24 posts

        Posted 29 December 2014 - 11:58 PM

        I don't get it.

         

        -rules for automatic weaponskilling rudras at 1000; I have that.

         

        I want rules for holding tp and using mordant rime @3000 if AM3 is not active and then automatically switching back to rudra's and ws @1000while it's active.... the whole point of a mythic weapon is to maintain aftermath level 3; I don't get what your trying to provide with you're response.

         

        So something that automatically maintains a mythic's aftermath level 3. thereby switching between two different weaponskills based on buff active and using them at different TP levels; I don't see how what you provided is doing that. I don't mean it negatively; your a great contributor to the game but I just am wanting a clear and concise answer if this can be done or not; I haven't seen any truely working examples.



        #4 Schliematt

        Schliematt

          Member

        • Members
        • PipPip
        • 18 posts

          Posted 30 December 2014 - 01:45 AM

          He gave you the code for a basic addon there and said you can add further rules as you see fit. this is where you add your specific desires of when and where to use the weaponskill. I could be wrong but gearswap doesnt normally do things unless you try to use an action or at trigger, or a buff changes or something. Both your guys's code start the same so maybe it doesnt work in gearswap, you have to make an addon.

           

          But autoexec can trigger a ws based on tp like he suggested. Its what I would have suggested. Ive used it from time to time to do WS points with a mule on occasion.

           

          On further thought, maybe something like this (prolly need some rearranging here from smarter peoples) Since The aftermath is what is more important here you want to focus on that first:

           

          if not buffactive["Aftermath: Lv.3"and player.status =='Engaged' then

               if player.tp <2999
                    cancel_spell()

               else

                    send_command('input /ws "Tachi: Fudo" <t>')

               end

          else
               if player.tp >999and player.status =='Engaged'then

                    send_command('input /ws "Tachi: Rana" <t>')
               end
          end

           

          And hes not jsut a contributer for the game he is one of the windower devs.



          #5 wickedpriest

          wickedpriest

            Member

          • Members
          • PipPip
          • 24 posts

            Posted 30 December 2014 - 02:26 AM

            He gave you the code for a basic addon there and said you can add further rules as you see fit. this is where you add your specific desires of when and where to use the weaponskill. I could be wrong but gearswap doesnt normally do things unless you try to use an action or at trigger, or a buff changes or something. Both your guys's code start the same so maybe it doesnt work in gearswap, you have to make an addon.

             

            But 1.)autoexec can trigger a ws based on tp like he suggested. Its what I would have suggested. Ive used it from time to time to do WS points with a mule on occasion.

             

            On further thought, maybe something like this (prolly 2.)need some rearranging here from smarter peoples) Since The aftermath is what is more important here you want to focus on that first:

             

            if not buffactive["Aftermath: Lv.3"and player.status =='Engaged' then

                 if player.tp <2999
                      cancel_spell()

                 else

                      send_command('input /ws "Tachi: Fudo" <t>')

                 end

            else
                 if player.tp >999and player.status =='Engaged'then

                      send_command('input /ws "Tachi: Rana" <t>')
                 end
            end

             

            And hes not jsut a contributer for the game he is one of the windower devs.

             

            1.) yes; we all know this allready.

            2.) That is the reason I made a post! I need someone to figure it out for me so i can copy and paste :XD

             

            We need this figured out once and for all please~ someone just make the generic code and tell us what to do with it so when ever someone gets a new shiney mythic they can just toggle it on/off



            #6 Arcon

            Arcon

              Advanced Member

            • Windower Staff
            • 1189 posts
            • LocationMunich, Germany

            Posted 30 December 2014 - 02:36 AM


             



            I don't get it.

             

            -rules for automatic weaponskilling rudras at 1000; I have that.

             

            I want rules for holding tp and using mordant rime @3000 if AM3 is not active and then automatically switching back to rudra's and ws @1000while it's active.... the whole point of a mythic weapon is to maintain aftermath level 3; I don't get what your trying to provide with you're response.

             

            So something that automatically maintains a mythic's aftermath level 3. thereby switching between two different weaponskills based on buff active and using them at different TP levels; I don't see how what you provided is doing that. I don't mean it negatively; your a great contributor to the game but I just am wanting a clear and concise answer if this can be done or not; I haven't seen any truely working examples.

             

            I know nothing about Mythics and scripts like these never work right, but the rules are very easy to adjust:

             

             

            require ('luau')
             
            ws = {
                SAM = {
                    aftermath = "Tachi: Fudo",
                    regular = "Tachi: Rana",
                THF = {
                    aftermath = "Rudra's Storm",
                    regular = "Mordant Rime",
                }
            }
             
            windower.register_event('tp change', function(tp)
                local player = windower.ffxi.get_player()
                if player.status == 1 and tp >= 1000 and ws[player.main_job] then
                    windower.send_command('input /ws "%s" <t>':format(ws[player.main_job][table.find(player.buffs, 272) and 'aftermath' or 'regular']))
                end
            end)
             

            And hes not jsut a contributer for the game he is one of the windower devs.

             

            I think that's what he meant :)

             

            We need this figured out once and for all please~ someone just make the generic code and tell us what to do with it so when ever someone gets a new shiney mythic they can just toggle it on/off



            #7 Schliematt

            Schliematt

              Member

            • Members
            • PipPip
            • 18 posts

              Posted 30 December 2014 - 03:55 AM

              That is addon code correct Arcon?



              #8 Arcon

              Arcon

                Advanced Member

              • Windower Staff
              • 1189 posts
              • LocationMunich, Germany

              Posted 30 December 2014 - 07:12 AM

              Yes, although it should work in GS as well. May need to remove the require('luau') line at the top, since GS has had some issues with including files, but exposes all the important bits anyway. But like I said, this should not go into GS user files in the first place.






              1 user(s) are reading this topic

              0 members, 1 guests, 0 anonymous users