Jump to content

qwy

Members
  • Content Count

    20
  • Joined

  • Last visited

Community Reputation

7 Neutral

About qwy

  • Birthday August 13
  1. i26 The Mastermind's PetMouse by qwy Preamble This offsets my last mastermind post. I probably use this about 70% to 80% of the time. It's super easy, does what I need it to do and I can keep my hand on the mouse, for the most part. I just use a generic, left, right and middle scroll. Nothing special required. 1. How it's different I've seen other mouse based controls but nothing quite like this. Watching them maneuver through most every environment it would seem like there's a lot more work going on behind the scenes, then there actually is. You can move them around with an almost military like precision, with one covering while the other advances, with single clicks of the LBUTTON. Another unique feature is the RightDoubleClick, it was kind of fun having them for, "stance goto" but, ultimately, I preferred it this way. The follow command is perfect in a panic situation. Not unique, but a great feature is, mouse+go to-reticle/click=awesome. That's just math. 2. How it Works Similar to most other mastermind controls, it starts with selecting one of the four groups or, modes. There are (2) modes; flexible, consisting of lieutenants and minions and, strict, with either the boss or all-pets. Strict is meant literally. Like other pet controls, to break the connection, another group must be selected. The lieutenant and minion modes aren't actually groups. There's a sense of group control however, only one pet is ever actually receiving commands, at a time. Command is toggled, between pets, with the, "go to" bind. This mode relies on the, "PetCom" command which sticks to the last targeted pet. Therefore, targeting a pet, outside the group, interrupts the selected mode, until the next time a, "go to" command is issued, (bound to ALT+LBUTTON). This flexibility allows quick access to any pet and still be in command of the selected group. Just, kinda not really. This works well with my NumPad version, posted here. I can reach the targeting feature with my thumb and still keep my hand on the mouse. The bind keys were chosen from, what's left from that bind set, as well as the global tp bindset, mentioned in another guide. I find them fairly ergonomic, despite this and, I'd encourage taking them for a spin before swapping them out. Let's go to the binds; 3. The Binds 3.1 Pet Commands Keys Minions.txt Lieutenant.txt Boss.txt All.txt 2: PetCom attack PetComPow* attack PetComAll attack ALT+LBUTTON: TargetCustomNext mypet* TargetCustomNext mypet* PetComPow* go to PetComAll go to PetCom go to ALT+RBUTTON: PetCom stay PetComPow* stay PetComAll stay RightDoubleClick: PetCom follow PetComPow* follow PetComAll follow ALT+RightDC: PetCom defensive PetComPow* defensive PetComAll defensive SHIFT+RightDC: PetCom aggressive PetComPow* aggressive PetComAll aggressive CTRL+RightDC: PetCom passive PetComPow* passive PetComAll passive * This definitely requires primary specific files. Some editing is probably going to be necessary. 3.2 The PetMouse File Load Commands Keys Commands SHIFT+NUMPAD4: TargetCustomNext alive mypet <PrimarySpecific> $$ Load Minion.txt SHIFT+NUMPAD5: TargetCustomNext alive mypet <PrimarySpecific> $$ Load Lieutenant.txt SHIFT+NUMPAD6: Load Boss.txt SHIFT+ADD Load All.txt CTRL+ADD Load Off.txt 4. The FIles Off.txt | Minion.txt | Lieutenant.txt | Boss.txt | All.txt With just the (5) files, I'm not going to bother with a download. Simply copy from the forum and paste in to some new .txt files. 5. Installing 5.1 Off.txt A little editing is required. Determine the folder you're going to store these files in and, edit the (5) load commands, found in 4.1, replacing; Binds/PetMouse/Bots/<file>.txt, to match. Keep an eye out for, "Bots" before the file name, it's referring to the primary, it's not necessary. Next, notice, I'm, using the 2 Key, just above the W key for attack. It's super convenient and I'd recommend keeping it, if that works however, with this being the PetMouse Off state, edit this command line back to your usual. I went with bindloadfile here, to help troubleshoot, if needed. They can go back to bindloadfilesilent at any time. 5.2 Minion.txt and Lieutenant.txt Assuming, the 2 was fine for attack, only the, "<ID>" needs to be edited to something that reflects the given names of these pets. In other words, if you have Thugs and you named them Manny, Moe and Jack, going with, "ugs" or "Thugs", isn't going to work here. Both of the lieutenant and minion files will need this. You might have to get creative. 5.3 Boss.txt This one's easy. All (7) command lines need, "<ID>", to get edited to, at least, (3) sequential characters of their summing power. PetComPow, doesn't care what they're called. For example, if you have the Beasts primary, you're limited, first, to, "Summon Dire Wolf". The problem here is, "Summon" is used in the powers of all your pets so, you're actually restricted to, "Dire Wolf". Therefore, "Dir, ire, wol and olf" are all good. IN the case above, in 5.2, Thugs named Manny, Moe and Jack wouldn't be an issue. We'd be all set with, "ugs" The All.txt file is All.good so, let's talk loading. 6.Loading Macros | Menus & | Binds Oh my! Here's a few options. I scraped together a little popmenu with some petcomall hotkeys and pet window features. Save the whole thing using the .mnu extension and drop it in the c:/<installpath>/cox/data/Texts/English/Menus/ folder, if you have it. If not, generate those folders, if you want to use it. In the Off.txt file, add; <YourKeyToBind> popmenu PetMouse Enjoy!
  2. MMPad+Thugs * Not tested by qwy QuickLinks Top | Beasts | Bots | Demons | Mercs | Necro | Ninjas | Thugs 1. Preamble The attached download is primary specific and includes all the support docs not listed on this post. The other primaries binds, their menu commands and load options have been removed to minimize the clutter. 2. Default File @/!/MM/Thugs/Pad.txt No editing required. 3. Group Files Bruiser.txt | Enforcers.txt | Thugs.txt With exception of the command to target the boss pet, no editing necessary. See section 2.B of the top post. 4. Pet Files EnforcerA.txt | EnforcerB.txt | Thug1.txt | Thug2.txt | Thug3.txt These files need to link to individual pets. See section 2.C in the top post. 5. Rolling Bind Files 1up.txt | 2up.txt See the top posts section 3 and the support docs, for more information. 6. Support Docs LoadThugs.txt This is a primary specific version of the LoadMMPad+.txt file. There are no in-game functions but there are command options for loading the bind set to a logged in character. The attached .rar includes this version of the load commands and the full ReadMe, Install and Help.txt from above. 7. Optional Menus Thugs+.window | Thugs+.mnu This version of the window and menu are primary specific. If you're interested in more than one primary, I'd recommending using the version in the top posts section 5 or the top posts .rar file. 8. Downloads MMPad+Thugs.rar The download in this post is primary specific. If you're interested in additional primaries, I recommend the top post download. * Not tested - Testers Wanted! MMPad+Thugsv200703.rar
  3. MMPad+Ninjas * Not tested by qwy QuickLinks Top | Beasts | Bots | Demons | Mercs | Necro | Ninjas | Thugs 1. Preamble The attached download is primary specific and includes all the support docs not listed on this post. The other primaries binds, their menu commands and load options have been removed to minimize the clutter. 2. Default File @/!/MM/Ninjas/Pad.txt No editing required. 3. Group Files Oni.txt | Jounin.txt | Genin.txt With exception of the command to target the boss pet, no editing necessary. See section 2.B of the top post. 4. Pet Files JouninA.txt | JouninB.txt | Genin1.txt | Genin2.txt | Genin3.txt These files need to link to individual pets. See section 2.C in the top post. 5. Rolling Bind Files 1up.txt | 2up.txt See the top posts section 3 and the support docs, for more information. 6. Support Docs LoadNinjas.txt This is a primary specific version of the LoadMMPad+.txt file. There are no in-game functions but there are command options for loading the bind set to a logged in character. The attached .rar includes this version of the load commands and the full ReadMe, Install and Help.txt from above. 7. Optional Menus Ninjas+.window | Ninjas+.mnu This version of the window and menu are primary specific. If you're interested in more than one primary, I'd recommending using the version in the top posts section 5 or the top posts .rar file. 8. Downloads MMPad+Ninjas.rar The download in this post is primary specific. If you're interested in additional primaries, I recommend the top post download. * Not tested - Testers Wanted! MMPad+Ninjasv200703.rar
  4. MMPad+Necro * Not tested by qwy QuickLinks Top | Beasts | Bots | Demons | Mercs | Necro | Ninjas | Thugs 1. Preamble The attached download is primary specific and includes all the support docs not listed on this post. The other primaries binds, their menu commands and load options have been removed to minimize the clutter. 2. Default File @/!/MM/Necro/Pad.txt No editing required. 3. Group Files Lich.txt | Knights.txt | Zombies.txt With exception of the command to target the boss pet, no editing necessary. See section 2.B of the top post. 4. Pet Files KnightA.txt | KnightB.txt | Zombie1.txt | Zombie2.txt | Zombie3.txt These files need to link to individual pets. See section 2.C in the top post. 5. Rolling Bind Files 1up.txt | 2up.txt See the top posts section 3 and the support docs, for more information. 6. Support Docs LoadNecro.txt This is a primary specific version of the LoadMMPad+.txt file. There are no in-game functions but there are command options for loading the bind set to a logged in character. The attached .rar includes this version of the load commands and the full ReadMe, Install and Help.txt from above. 7. Optional Menus Necro+.window | Necro+.mnu This version of the window and menu are primary specific. If you're interested in more than one primary, I'd recommending using the version in the top posts section 5 or the top posts .rar file. 8. Downloads MMPad+Necro.rar The download in this post is primary specific. If you're interested in additional primaries, I recommend the top post download. * Not tested - Testers Wanted! MMPad+Necrov200703.rar
  5. MMPad+Mercs * Not tested by qwy QuickLinks Top | Beasts | Bots | Demons | Mercs | Necro | Ninjas | Thugs 1. Preamble The attached download is primary specific and includes all the support docs not listed on this post. The other primaries binds, their menu commands and load options have been removed to minimize the clutter. 2. Default File @/!/MM/Mercs/Pad.txt No editing required. 3. Group Files Commando.txt | Ops.txt | Soldiers.txt With exception of the command to target the boss pet, no editing necessary. See section 2.B of the top post. 4. Pet Files OpsA.txt | OpsB.txt | Soldiers1.txt | Soldiers2.txt | Soldiers3.txt These files need to link to individual pets. See section 2.C in the top post. 5. Rolling Bind Files 1up.txt | 2up.txt See the top posts section 3 and the support docs, for more information. 6. Support Docs LoadMercs.txt This is a primary specific version of the LoadMMPad+.txt file. There are no in-game functions but there are command options for loading the bind set to a logged in character. The attached .rar includes this version of the load commands and the full ReadMe, Install and Help.txt from above. 7. Optional Menus Mercs+.window | Mercs+.mnu This version of the window and menu are primary specific. If you're interested in more than one primary, I'd recommending using the version in the top posts section 5 or the top posts .rar file. 8. Downloads MMPad+Mercs.rar The download in this post is primary specific. If you're interested in additional primaries, I recommend the top post download. * Not tested - Testers Wanted! MMPad+Mercsv200703.rar
  6. MMPad+Demons * Not tested by qwy QuickLinks Top | Beasts | Bots | Demons | Mercs | Necro | Ninjas | Thugs 1. Preamble The attached download is primary specific and includes all the support docs not listed on this post. The other primaries binds, their menu commands and load options have been removed to minimize the clutter. 2. Default File @/!/MM/Demons/Pad.txt No editing required 3. Group Files Prince.txt | Demons.txt | Demonlings.txt With exception of the command to target the boss pet, no editing necessary. See section 2.B of the top post. 4. Pet Files DemonA.txt | DemonB.txt | Demonling1.txt | Demonling2.txt | Demonling3.txt These files need to link to individual pets. See section 2.C in the top post. 5. Rolling Bind Files 1up.txt | 2up.txt See the top posts section 3 and the support docs, for more information. 6. Support Docs LoadDemons.txt This is a primary specific version of the LoadMMPad+.txt file. There are no in-game functions but there are command options for loading the bind set to a logged in character. The attached .rar includes this version of the load commands and the full ReadMe, Install and Help.txt from above. 7. Optional Menus MMPad+Demons.window | Demons+.mnu This version of the window and menu are primary specific. If you're interested in more than one primary, I'd recommending using the version in the top posts section 5 or the top posts .rar file. 8. Downloads MMPad+Demons.rar The download in this post is primary specific. If you're interested in additional primaries, I recommend the top post download. * Not tested - Testers Wanted! MMPad+Demonsv200703.rar
  7. MMPad+Bots * Not tested by qwy QuickLinks Top | Beasts | Bots | Demons | Mercs | Necro | Ninjas | Thugs 1. Preamble The attached download is primary specific and includes all the support docs not listed on this post. The other primaries binds, their menu commands and load options have been removed to minimize the clutter. 2. Default File @/!/MM/Bots/Pad.txt No editing required. 3. Group Files Assault.txt | Protectors.txt | Drones.txt With exception of the command to target the boss pet, no editing necessary. See section 2.B of the top post. 4. Pet Files ProtectorA.txt | ProtectorB.txt | Drone1.txt | Drone2.txt | Drone3.txt These files need to link to individual pets. See section 2.C in the top post. 5. Rolling Bind Files 1up.txt | 2up.txt See the top posts section 3 and the support docs, for more information. 6. Support Docs LoadBots.txt This is a primary specific version of the LoadMMPad+.txt file. There are no in-game functions but there are command options for loading the bind set to a logged in character. The attached .rar includes this version of the load commands and the full ReadMe, Install and Help.txt from above. 7. Optional Menus Bots+.window | Bots+.mnu This version of the window and menu are primary specific. If you're interested in more than one primary, I'd recommending using the version in the top posts section 5 or the top posts .rar file. 8. Downloads MMPad+Bots.rar The download in this post is primary specific. If you're interested in additional primaries, I recommend the top post download. tested MMPad+Botsv200703.rar
  8. MMPad+Beasts * Not tested by qwy QuickLinks Top | Beasts | Bots | Demons | Mercs | Necro | Ninjas | Thugs 1. Preamble The attached download is primary specific and includes all the support docs not listed on this post. The other primaries binds, their menu commands and load options have been removed to minimize the clutter. 2. Default File @/!/MM/Beasts/Pad.txt No editing required 3. Group Files Dire.txt | Lions.txt | Wolves.txt Oh my! With exception of the command to target the boss pet, no editing necessary. See section 2.B of the top post. 4. Pet Files LionA.txt | LionB.txt | Wolf1.txt | Wolf2.txt | Wolf3.txt These files need to link to individual pets. See section 2.C in the top post. 5. Rolling Bind Files 1up.txt | 2up.txt See section 3 and the support docs, for more information. 6. Support Docs LoadBeasts.txt This is a primary specific version of the LoadMMPad+.txt file. There are no in-game functions but there are command options for loading the bind set to a logged in character. The attached .rar includes this version of the load commands and the full ReadMe, Install and Help.txt from above. 7. Optional Menus Beasts+.window | Beasts+.mnu This version of the window and menu are primary specific. If you're interested in more than one primary, I'd recommending using the version in the top posts section 5 or the top posts .rar file. 8. Downloads MMPad+Beasts.rar The download in this post is primary specific. For more than one primary, use the .rar in the first post. * Not tested - Testers Wanted! MMPad+Beastsv200703.rar
  9. i26 Mastermind NumPad Controls+ MMPad+ by qwy QuickLinks Top | Beasts | Bots | Demons | Mercs | Necro | Ninjas | Thugs Preamble: I've only rolled one MM since coming back, Bots. It's fair to say, I might not have rolled an MM at all, if I hadn't seen the original Numpad Controls posted on the Homecoming forum. I had forgotten all about how much fun Masterminds are with them. Before I got out of Outbreak, the Sandolphan's original binds were installed and I was fully reacquainted. So fun! As I leveled up, I kept adding to it every time a new idea came to mind. This version represents my, most sincere, first step from the original. I'm trying to stick to the simple elegance of the original, scaling back some of the far off, or clunky additions for another time. What's new: Not straying too far from the original, here are the key additions; An easy selection method for controlling individual pets Can target a specific pet, cycle through a group of pets or cycle through all of them Added "Petsay" to the selection method Trigger both upgrades in 1 click. - only bots have been tested Follow modes, have been moved to SUBTRACT, for easy slap panic All commands can now change the selected pet/group strance, i.e. defensive follow, passive stay, aggresive attack Dismiss added to select method Added popmenu with some basic commands, control options of the pet window, generate a variety macros and a bind cheat sheet. Added a custom.window to load the file and generate macros with icons consistent with the primary to summon and load numpad controls. What's different: It should look pretty familiar, right out of the box. A few key difference; The All.txt file has been replaced with Pad.txt and, is specific to each primary . There are now, (11) files per primary. (5) for individual control of each minion and lieutenant. Additional editing required. (2) for the toggle upgrades to occur in a single click. (1) Pad.txt, this versions, "All.txt" (3) One for each tier group Disclaimer The folder hierarchy mirrors my own. It's stored in the Installations data folder and has, what may appear to be, superfurlous sub folders. This is in anticipation of additional bind sets, I'm planning on sharing in the near future. Editing paths and file names, to suit your needs, shouldn't be an issue. with exception to the custom.window and Popmenu paths, which are required by the interface. Help Me / Help You If there are any questions, please don't hesitate to ask. If any files were edited as part of your installation, please describe the new variables on any requests for assistance. Not having rolled other primaries, any help testing and correcting mistakes I might have made, would be very much appreciated. 1. Binds according to selected pets: 1.A Base Binds NUMPAD0: Select All Key No Chord +ALT +SHIFT +CTRL Defensive Key Aggressive Key Passive Key NUMLOCK: - - - - DIVIDE: all pet say all minions Say all lieutenants say boss says MULTIPLY: open popmenu toggle custom.window SUBTRACT: all follow all def follow all agg follow all pas follow NUMPAD9: all go to all def got all agg got all pas got NUMPAD8: all attack target all def att target all agg att target all pas att target NUMPAD7: all stay all def stay all agg stay all pas stay NUMPAD6: all passive select boss alias NUMPAD5: all aggressive select lieutenant B NUMPAD4: all defense select lieutenant A NUMPAD3: select boss select minion 3 summon boss dismiss boss NUMPAD2: select lieutenants select minion 2 summon lieutenants dismiss lieutenants NUMPAD1: select minions select minion 1 summon minions dismiss minions NUMPAD0: select all nop dismiss target dismiss all ADD: roll upgrades #PADENTER: pet heal targeted DECIMAL: cycle target next pet all cycle target next minions cycle target next lieutenants target boss 1.B Group Binds NUMPAD1-3: Select Group Key No Chord +ALT +SHIFT +CTRL Defensive Key Aggressive Key Passive Key NUMLOCK: - - - - DIVIDE: selected group say all minions say all lieutenants say boss says MULTIPLY: open MMPad+ popmenu toggle MMPad+ custom.window SUBTRACT: selected group follow selected group def fol selected group agg fol selected group pas fol NUMPAD9: selected group go to selected group def got selected group agg got selected pas got NUMPAD8: selected group attack target selected group def att target selected group agg att target selected group pas att target NUMPAD7: selected group stay selected group def sta selected group agg sta selected group pas sta NUMPAD6: selected group passive select boss alias NUMPAD5: selected group aggressive select lieutenant B NUMPAD4: selected group defense select lieutenant A NUMPAD3: select boss select minion 3 summon boss dismiss boss NUMPAD2: select lieutenants select minion 2 summon lieutenants dismiss lieutenants NUMPAD1: select minions select minion 1 summon minions dismiss minions NUMPAD0: select all nop dismiss targeted pet dismiss all ADD: roll upgrades, all #PADENTER: pet heal targeted DECIMAL: Selected group target next pet cycle target next minions cycle target next lieutenants target boss 1.C Individual Binds ALT+NUMPAD1-6: Select Pet Key No Chord +ALT +SHIFT +CTRL Defensive Key Aggressive Key Passive Key NUMLOCK: - - - -- DIVIDE: selected pet say all minions say all lieutenants say boss says MULTIPLY: open MMPad+ popmenu toggle MMPad+ custom.window SUBTRACT: selected pet follow selected pet def fol selected pet agg fol selected pet pas fol NUMPAD9: selected pet go to selected pet def got selected pet agg got selected pet pas got NUMPAD8: selected pet attack target selected pet def att target selected pet agg att target selected pet pas att target NUMPAD7: selected pet stay selected pet def sta selected pet agg sta selected pet pas sta NUMPAD6: selected pet passive select boss alias NUIMPAD5: selected pet aggressive select lieutenant B NUIMPAD4: selected pet defense select lieutenant A NUMPAD3: select boss select minion 3 summon boss dismiss boss NUMPAD2: select lieutenants select minion 2 summon lieutenants dismiss lieutenants NUMPAD1: select minions select minion 1 summon minions dismiss minions NUMPAD0: select all dismiss selected pet dismiss targeted pet dismiss all ADD: roll upgrades. all #PADENTER: pet heal targeted DECIMAL: target selected pet cycle target next minions cycle target next lieutenants target boss 2. The Files QuickLinks Top | Beasts | Bots | Demons | Mercs | Necro | Ninjas | Thugs 2.A Default File: @/!/MM/<Primary>/Pad.txt - This was originally the All.txt file. As I started adding commands to the original, it began to take a more primary specific turn. It's still the default stance and loads all the other files for it's primary. With this file selected, all pets respond to base commands. Editing shouldn't be necessary. 2.B Group Files: @/!/MM/<Primary>/<Groups>.txt - Carried over from the original, there are still (3) group files named after their summoning power. These files use the command, "PetComPow" and, "PetSayPow" which identifies the name of the command that summons them. Renaming pets doesn't impact this command at all. The way they're targeted is the only exception. The boss uses the command, "PetSelectName". Lieutenants and minions use; "TargetCustomNext". Both of these commands require a string of letters, numbers or symbols, unique to that group, for this to work. I used the first (3) characters of the pets default name to identify their group, as my group file default name (with exception to Bots). For example, I named one of my lieutenants, "Norad Protocol", the other, "Orb Systems Pro" and made sure, "Pro" was unique to their group. 2.C Pet Files: @/!/MM/<Primary>/<Individual>.txt - There are (6) pets but, the boss file from group is loaded, regardless of how a boss is selected. That leaves us (2) files for lieutenants and, (3) for minions. These files use, "PetComName", "PetSayName" and, "TargetCustomNext" so renaming a pet can impact every command line. My unique pet file default name uses the last (2) characters of the actual default pet name, followed by, "A" or "B" for lieutenants and 1-3 for minions. When renaming a pet, consider how that name will link to both, the pet file and the targeting command in the group file. The commands in question can be edited as well however, consider my example from above. The actual default name for a bot lieutenant is Protector (I ignored Bot). The names I used, above, linked to my default for the group file using, "Pro" and, my default for pets using, "orA" and, "orB" Each primary has unique considerations however, I tried to keep things as simple as possible. Now that you're aware of the guidelines I followed, with a little creativity, you should be able to come up with something that works for you. 2.D Bind Files In effort to appear organized, binds are available in the proceeding posts. With (11) bind files, (4) support docs and (2) menus, per primary, things got a little cramped here, on the first post. The .rar on this first post, includes everything. The following posts, have attached .rar files that are specific to that posts primary. QuickLinks Top | Beasts | Bots | Demons | Mercs | Necro | Ninjas | Thugs 3. Rolling Binds Bound to the, "ADD" key, the Pad.txt triggers the first step, on the first use and loads 2up.txt, the second half. 1up.txt takes responsibility off of pad.txt, mirroring the command. The +/-, after the commands opening quote, initiates the two step behavior. This has only been used with Bots but, it should work on, at least, a few others. Watch how the icons respond, if it's not working. This is usually a good indicator on what changes need to be made. Sometimes, it's just a matter of changing the key press, itself. Sometimes, a long hold or, a quick tap, will produce different results. If it's not coming together, edit the three files and use them as a rotating bind set. @/!/MM/<Primary>/Pad.txt | @/!/MM/<Primary>/1up.txt ADD "targetcustomnext alive mypet$$powexecname upgrade one$$bindloadfilesilent @/!/MM/<Primary>/2up.txt" @/!/MM/<Primary>/2up.txt ADD "targetcustomnext alive mypet$$powexecname upgrade two$$bindloadfilesilent @/!/MM/<Primary>/1up.txt" 4. Support Docs Includes: ReadMe.txt | Install.txt | Help.txt | LoadMMPad+.txt 5. Optional Menus custom.window & Popmenu The custom window is essentially an in-game version of the LoadMMPad.txt file. The Popmenu has some pet controls, pet window tools, a cheat sheet for the binds and also serves as an in-game version of LoadMMPad.txt Downloads MMPad+.rar This is all bind files, consolidated menus and support documents for all primaries. The posts to follow will include the binds for copying and pasting off the forum and .rar files for individual primaries. The optional windows and menus will be primary specific so, if you end up using more than one primary, I suggest going with the versions on this post or this download instead. * Only Bots thoroughly tested. - Testers Wanted! MMPad+v200703.rar
  10. The macro's a great option, if you're trays are packed, this might be an alternative. New poses would be nice, with animations for all directions. Like the macro, I use all four to keep me guessing. It's not the same but, it's got its merits. W "+forward$$e flypose3" or, W "+forward$$e flypose1$$e flypose2$$e flypose3$$e flypose4"
  11. i26 Guide: BuildSaveFile; Navigating Relative Paths (qwy's mApps 2.0, Chapter 1.1) by qwy The following guide's focus is to provide a single source reference on default paths when saving or loading a file. All paths, were determined using Windows10 64-bit. If your installation varies in anyway outside of, "C:/<installPath>/CoX/", please post, or message me, your findings, with relevant system information. It's intention is to both, provide the initiated an ability to scan for anything relevant to them and a, "How to" to anyone who may need it. Why a guide? An admission of ignorance I love alts! I love how binds and the flexibility of the interface, can make playing an one alt, compared to another, almost feel like playing a different game. Back on live, I took advantage and, every alt's keys, windows and options grew further and further apart, until that time I lost all of it. I don't remember how it happened, an update? Maybe I had to reinstall? I probably did something stupid. This was over 10 years ago. I've done a bunch of stupid crap since then, I can't remember all of it. All I do remember, that was my first lesson on how things save around here. This was a little after CoV and a Mastermind, was my, "main" dejour. I wouldn't say he had a lot of binds, he was BOUND! I rebuilt, what I could, from memory but, it was a rush job. Not the caring refinement developed over time. Some of the binds were added while, the player I got them from, was still in the process of giving them to me. Those were just gone. When I was done, a little wiser now, optionsave, bindsave, all the saves. Rebuilding the first alt, after the MM, I made sure to run all those new-to-me save commands and, got my second lesson about how things save around here... Those aren't the commands I was looking for. I had just saved over the backed up mastermind files. Not only do I want to help others steer clear of this happening to them, I want to share what I've been doing with commands and pushing files around. I've had a really hard time searching for this kind of thing, which is fine. I'm pretty bold with system files, and I like coming up with scenarios and experimenting on them. Determining through trial and error, is still, "playing" to me. I know a lot of people aren't in to that kind of thing. I have more tutorials I want to write, but they all need this kind of information. Without references I can point to, I'm stuck with a choice; write this out everytime and patronize those that already know or talk someone who's learning, down a path that wipes out data they didn't want to lose. Why BuildSave: Two reasons; 1. It's easy. I can focus on the path part and not worry about the file, itself. 2. Was anyone else under the impression there wasn't a functioning command like buildsavefile? Somehow, I accepted it as a fact. I'm positive I've witnessed other people express, that was their impression as well. In forums, in chat, other places. A collective understanding, BuildSave is the only option. Searching variations of /BuildSaveFile, with and without underscores gets a couple of hits. Not enough to convince me, that collective understanding I thought I experienced, it wasn't just me. Might've been... /BuildSaveFile: Relative vs. Absolute Paths I was working on an unrelated project and, entered /buildsavefile, followed by random characters, in to chat expecting an error. It did not. if you read that last paragraph, you already know, I didn't know. Adequately distracted, I forgot about the first project and kicked off a new error campaign. As long as I wasn't trying to escape the installation root, relative paths passed. I'm not great at keeping notes but I kept enough for a highlight reel, I'll leave at the end. There were a couple of other surprises. .txt, added manually, after the fact, Totally fine. And, possibly the answer to why I've encountered a number of people who, like me, didn't think this was a functional option... absolute paths failed across the board. /BuildSaveFile Function: Generates a fixed-format text document focused solely on the commanding character's, active build. The user specifies the filename and optional, relative path within the CoX installation folder. Contains Name / level / origin / class Powers / level selected Number of slots per power enhancements slotted OnSubmit: Simple logic test of valid syntax Is Invalid: Default channel, "Error" reports, "UnableBuildSave" Is Valid: Default channel, "System" reports, "BuildSave" Modifiers: None known. Not needed Arguments: (1) <OptionalRelativePath>/<SpecifiedName>.txt Defaults To: <System>/<InstallPath>/<Account>/Builds/ Specify Path: Yes. Relative path only. Specified by valid system syntax and characters, followed by one, or more, forward slashes. Can Name: Yes. Specified after the last optional forward slash by any valid system syntax and characters, ending with the extension, ".txt" Absolute Paths: With Absolute paths, potentially set as, nop (joke), let's breeze through this. Your computer's hard drive. The one that the operating system is installed on. It's running the show so, it's top level folder, the one all other folders are within, is the system root. Absolute paths start there and apply to anywhere not there, within itself. Considering the breakdown above, for, "Defaults to:", I started with, "system". Your hard drive. Even with the absolute path, being partly responsible for my motivation to write a guide on using its counterpart, literal to its name, it is a definitive starting point, easily defined and recognized as "C:/", and leads away from itself. I had to shake my head using it for, "Defaults to", but, let's look at the alternative. Relative Paths: Relative paths are also literal, it can only be identified from a point other, than itself. For example, "", is the relative path counterpart for, "Defaults to:", above. I Feel like, it's trying as hard as a little path can. I just can't escape a sense that... something's a little off. Like, we're not getting the WHOLE story, huh? Ok, I'll keep moving. Visually, once the second half of the path is known, they're similar to other common folder structures. The key difference is this path doesn't concern itself with the system, as a whole, it's path to a destination is always relative to itself. An analogue simile might be flying in to a new city and using the airport to track a path to the hotel as a relative path. An absolute might be landing at the airport and tracking the path to the hotel from the, "Welcome to...." sign, on the outskirts of town. Maybe city hall.. Airports don't typically move around a lot.... I don't know. Something like that. It makes sense if you don't overthink it. Quick Reference Tables: Talking CIty of X, files spew from everywhere so, relative paths are relative to the file in question, which is nice. Not getting to into the weeds on this, here's a default folder cheat sheet. Default Folder: TypeSave Command Fixed Default Path Fixed File Name BindSave: C:/<installPath>/CoX/ keybinds.txt BuildSave: C:/<installPath>/CoX/<Account>/Builds/ build.txt ChatSave: C:/<installPath>/CoX/ chat.txt OptionSave: C:/<installPath>/CoX/ options.txt WDWSave: C:/<installPath>/CoX/ wdw.txt * Keep an eye out for the, "s" that's only half-way-in, a committed relationship with the option command. Hiding in clumps of commands, optionsSave and option.txt, see you before you see them. Default Folder: TypeSaveFile Command Unmodified Default Path User Generated "data" Folder BindSaveFile: C:/<installPath>/CoX/piggs/ C:/<installPath>/CoX/data/ BuildSaveFile: C:/<installPath>/CoX/<Account>/Builds/ Remains the same. ChatSaveFile: C:/<installPath>/CoX/piggs/ C:/<installPath>/CoX/data/ OptionSaveFile: C:/<installPath>/CoX/piggs/ C:/<installPath>/CoX/data/ WDWSaveFile: C:/<installPath>/CoX/piggs/ C:/<installPath>/CoX/data/ *One look inside the /piggs folder, is all it takes to know, it's not ideal. I haven't seen this anywhere so, grain of salt, I think of the data folder as the User Root. Things were encouraged to play with, default here. **File names must be specified by user or command will error. Navigating Relative Paths: I had said that Relative paths, require two points in order to be defined however, there's a third point to consider. They're commonly restricted within their environment, the installation root. How that affects us, simply put, the installation root is a brick wall. Indicated as, "CoX", on the graph below, saving to the left of that isn't an option. Considering the graph below, from the green BUILDS folder, if we wanted to move to the right, (referred to as "down"), entering a folder name, followed by ,"/" the forward slash moves us 1 step. To go back, (graph-left, "up" when talking to IT), instead of the folder name "../", two periods and a forward slash, takes us back 1 step. From the green BUILDS folder, moving right, we can take as many steps as we squeeze in to a single command but, if we're going the other direction, trying to save to a folder more than 2 steps back and our command errors. Folder Structure Puter Path to CoX stumes Build1 Data Build2 Yours Build3 Screens Build4 Account BUILDS Build5 Build6 Build7 * Unlike a board game, being, "in" a file, is represented as, to the right and one down . With that said, consider exhibit 11.C § 1.61 (1972). I'll go get those commands together. exhibit 11.C § 1.61 (1972) /buildsavefile "../../../CoX/BuildFileName.txt" /buildsavefile "../../../BuildFileName.txt" /buildsavefile "../../BuildFileName.txt" Anyways... Below, in the text editor, is our command with the paths to each of the 7 build folders mapped on the graph and, one for saving to the BUILDS folder. On other systems, common path options might be available but only up and down were recognized on my computer. (See notes) /builldsavefile ../../Costumes/Build1/TheFileSavedIn-1.txt /builldsavefile ../../data/Build2/TheFileSavedIn-2.txt /builldsavefile ../../data/Yours/Build3/TheFileSavedIn-3.txt /builldsavefile ../../screenshots/Build4/TheFileSavedIn-4.txt /builldsavefile TheFileSavedInBUILDS.txt /builldsavefile Build5/TheFileSavedIn-5.txt /builldsavefile ../../Build6/TheFileSavedIn-6.txt /builldsavefile ../../Build6/Build7/TheFileSavedIn-7.txt *if you've noticed the commands, don't exactly match the name, good eye! It's not a ruse. The table is just, whatever. Without function, I let form rule. The commands are here for easy editing. Parts with real world applications, I wanted to get right. NO GUARANTEES, NO REFUNDS! It's a Wrap! Commands first. Comparing the binds to the graph, a pattern is probably starting to stand out. Forget what you heard Paula Abdul going on about, it's two steps back.... then, whatever number of steps forward, if you're navigating to another install root folder. Typically, these commands generate the folders you've specified if they don't already exist. If that isn't happening, it's possible, your security settings are getting in the way. I'd guess generating folders, the old fashioned way, through your operating system, is probably going to buff that out. The minor inconvenience isn't worth altering otherwise satisfactory security. OK, it's over! I hope there was something good in here for you. Scrolling down, there's a quick, probably unnecessary, buildsave breakdown Preview of a saved build file - which barely gets a nod in guide related to build files... Maybe I'm tired, teetering on delusional but, it seems unnecessary. Souvenir macro and menu options to trigger the buildsavefile command Final thought on permissions vs bug (I'd be interested if anyone knows the answer) The scraps of test notes. There's nothing crazy but, the extensionless, sample was unexpected and the path symbol, "./" is ignored but not errored /BuildSave: Function: Generates a fixed-format text document focused solely on the commanding character's, active build, to the default path. OnSubmit: Is Invalid: Default channel, "Error" Reports, "UnableBuildSave" Is Valid: Default Channel, "System" Reports, "BuildSave" Modifiers: None known. Not Needed Arguments: N/A Defaults To: <System>/<InstallPath>/<Account>/Builds/ Specify: No. Name: build.txt Build File Preview: wy: Level 50 Natural Class_Controller Character Profile: ------------------ Level 1: Inherent Inherent Brawl Attuned_Pounding_Slugfest_D (1) Level 1: Inherent Inherent prestige_generic_Sprintp EMPTY Level 1: Inherent Inherent prestige_BestBuy_Sprintp EMPTY Level 1: Inherent Inherent prestige_EB_Sprintp EMPTY Level 1: Inherent Inherent prestige_Gamestop_Sprintp EMPTY Level 1: Inherent Inherent prestige_DVD_Glidep EMPTY Level 1: Inherent Inherent Sprint Attuned_Celerity_C (1) Level 2: Inherent Inherent Rest EMPTY Level 2: Inherent Fitness Swift Crafted_Fly (50+5) Level 2: Inherent Fitness Hurdle Crafted_Jump (50+5) Level 2: Inherent Fitness Health Attuned_Panacea_F (1) Prospects for keeping it on, or near your person: Macro /macroimage "Inspiration_Team_Rez_Lvl_4" "Capture Soul" "buildsavefile ../I get to go in the account folder. My mom says I'm important.txt" Popmenus: Option "S&ave as," "show chat$$beginchat /buildsavefile ../../data/Builds/" Option "TIMMEH !!!" "buildsavefile ../../data/YourSubFolder/TIMMEH/TIMMEH-time.txt" Option "Makin' Macro" <&macroimage "Inspiration_Team_Rez_Lvl_4" "Capture Soul" "buildsavefile ../../This/is/Serious.txt"&> Custom.window Button "S&ave as," "show chat$$beginchat /buildsavefile ../../data/Builds/ " Button "TIMMEH !!!" "buildsavefile ../../data/YourSubFolder/TIMMEH/TIMMEH-time.txt" Button Macro <&macroimage "Inspiration_Team_Rez_Lvl_4" "Capture Soul" "buildsavefile ../../data/YourSubFolder/TIMMEH/TIMMEH-time.txt"&> -FInal thought on permissions vs bug: Not being a security guy, or even a strong computer guy. All I can do it speculate but considering the following two points, I'm not confident it's a bug. - The account file may have additional restrictions the data, (I originally generated) doesn't have. - Build Absolute path error, mimics all file errors attempting to escape install root via relative -Test Samples: Saved to Account/Builds - a peach Passed/buildsavefile test.txt Saved to Account/Builds Opens once, .txt is restored no corruption Passed/buildsavefile test Saved to Account/Builds - ./ ignored Passed/buildsavefile ./test.txt Saved to Account/Buids/Test....and beyond Passed/buildsavefile /test/test.txt Passed/buildsavefile test/test\test\test.txt From Install Root, saved test/++ Passed/buildsavefile ../../test/test\test\test.txt Error/buildsavefile Error/buildsavefile . Error/buildsavefile ./ Error/buildsavefile /. Error/buildsavefile ../../../test.txt Error/buildsavefile ../../../test/test.txt Error/buildsavefile C:/coh/test.txt Error/buildsavefile C:\coh\test.txt Error/buildsavefile C:/<PathToWritePermissionsForUnknownUser>/test.txt -Control Passed/optionsavefile C:/coh/test.txt Passed/optionsavefile C:\coh\test1.txt Passed/optionsavefile C:/coh\test1.txt Passed/optionsavefile C:/<PathToWritePermissionsForUnknownUser>/test.txt Passed/chatsavefile C:/coh/test.txt Passed/chatsavefile C:\coh\test1.txt Passed/chatsavefile C:/coh\test1.txt Passed/chatsavefile C:/<PathToWritePermissionsForUnknownUser>/test.txt - Absolute path is an absolute no. - Client accepts and converts backslashes to forward, as part of a path - No issues navigating installation folder or generating new folders - Error reports and rejects attempts to escape folder via relative - No logic test of file extension. Saved viable file without extension - No logic test to preserve existing files NOT THE LAST COMMENT, THIS IS THE FINAL!!! if you're reading this line, this is is still on. I'll edit it out when this is over. I'm giving, at minimum, (5) 999,999,999,999 influence prizes to the top of the class. I've never done this before so to avoid a sticky situation, I'm on Excelsior and offering prizes capable of sending through the mail system. Cross server winners , are encouraged to roll an alt on Excelsior to manage a more involved transfer. Here we go... There's 2 questions; Question 1 I keep all my binds, together, inside the data folder. That's where bind files originate, it's their default. Similar to the build file originating in one of Accounts subfolders, I use a subfolder, for mine. Inside, each of my alts has their own folder, for all of their files. Each of My alts also. have a little personal popmenu with a link for each, of the three possible, builds to save, onclick, that link's build, to it's build folder. What's path does that link follow? It's not a trick question specific popmenus syntax isn't necessary Descriptive generic folders names irrelevant to the games operation are fine (this is a twist, alluded to in the content) Question 2 Whadja think 'bout exhibit 11-ampersand, or whatever? I'm looking for: Did any pass? Did any fail? Which did what? Did you see what I did there? I'm looking for correct answers, but the bonus points for funny add up faster. (Although, incorrect kind of means I suck at tutorials, huh? ) Be sure, it's crystal clear where to send your prize if hitting reply is not it. I don't imagine this is going to get much attention so, odds are probably pretty good. Please be patient with me. Winners are getting free influence, I'm going to have 5 billion less. (Possibly, even less if there's a 6th, 7th or 12th submission too good not to be a winner. Funny counts.) I have no idea what to expect as far as participation. If it's high, I'm going to wrap it up real fast and send out the prizes. I'm not looking to do turn this as a fulltime job. If it's low, prizes will go out by 7.11.2020. If it's sooo low, I decide to continue this beyond that date, it's season 2. You'll have cash, cash, money, money and ,season 1 winner's bragging rights. I reserve the right to include your submission to this thread however, I'm not sure I will. When it's over, is there a point? I'm on the fence. I want to hear from anybody interested in participating and I'm not going to ask any questions but, ideally, the prizes should go to the players , a billion is a game changing number. If it's just pocket change to you, let me know in your submission. I'll send the influence to the next runner up, in your name. For passing on the influence, in the spirit it was intended, you haven't subtracted from the winners circle. Instead, you'll be recognized as a Grand Poobah, entitling you to a set of purple IOs, of your choosing, lvl50 or, attuned,(it's a gesture?? What do I even offer you?!? you passed on a billion...) and, the final word on appending your submission to this tutorial, whether I'm on the fence or, not. Add that in your submission as well. OK, I'm really going now.
  12. i26 and beyond: The 5Chain Attack Assistant by qwy Preamble This is an ultra-basic rotator, common to a lot of applications. The only difference, It works with a floating tray for arranging attack chains and maintaining a visible reference of their progression. A single key, advances through each step. I feel a little foolish writing this, it's really just a rotator. With the tie in to a tray though, I started to notice I was using it all the time. I thought other people might get something out of this application as well. For anyone not familiar, I'll still walk through the steps. 1. Getting Started 1. Dedicated Floating Tray We need a dedicated, floating tray, for this. They're essentially power trays, just independant of your main tray. This can get a little confusing, in that, floating trays have an ID number and are capable of scrolling to other, "Tray numbers". Tray's layer with higher ID number towards the front. SInce I have this on all my characters, I use floating tray7 as the highest available. "Available", is really the only detail that matters. To choose by number, you can edit and run this; /windowshow tray# Or, on the top right of your main power tray, there's a, "+"symbol, just right of the, "Recipes" toggle. A click generates the lowest tray ID number available, which, couldn't be easier to change later, if a reason to, pops up. 2. Setting the Orientation Right click the new tray and set the orientation to 2x6 (2 wide, 6 high) so, that it resembles the large one, just right of the character, in the image below. 3. Power Icons and Binds The binds take this orientation to heart. The column on the left is triggered by the 1 key, it will fire each power in that column, from top to bottom. The column on the right, follows this same idea, using the 3 key. Each bind file was named to reflect, The Key | The Tray | It's Number in the Sequence. Only the icons you want to use in a chain should go in the tray. Arranging the order of power icons, is the only step in altering the chain. 4. Placement I don't usually click powers. I tend to keep the mouse in front and use binds to trigger. For that reason, it's really tiny and somewhere in the peripheral. I only care about keeping an eye on activation and cooldowns. The binds are pretty dumb so, pressing a trigger too soon, can throw the whole order off. The urge to spam the 1 & 3 key is very real. For that reason, characters tend to outgrow it, as they get more powerful, and I get more familiar. 5. Installing If you're using the .zip, the file structure for placing the files, starts in the, "data" folder inside your CoX installation folder. Unless you've already generated a data folder, you won't have one. Adding one, is the only way to get one. Once the folder is there, you can either drop the entire contents from extracted .zip or, manually generate the remaining folders until, it mirrors it. Installing it to other folders on your hard drive is fine. The file paths of the macros and commands in the files just need to be edited to match. If you have a real text editor like Notepad++, it's basically a single, elaborate, cut and paste, to get them all. 6. Loading the FIles I have the initial step on a global file in the install root's data folder. The, "@" is my subfolder. The following 10 files, are kept in a global catch all named, "!". There's a zip file, at the bottom, with individual files and this folder structure. Edit accordingly. Load Global.txt /macroimage "v_archetypeicon_stalker" "5Chain" "bindloadfilesilent @/Global.txt" @/Global.txt ---------------- 1 "powexectray 2 5$$bindloadfilesilent @/!/152.txt" 3 "powexectray 1 5$$bindloadfilesilent @/!/352.txt" ---- Use Macros Instead of Global.txt /macroimage "Brawling_ComboLevel1" "Melee" "powexectray 2 5$$bindloadfilesilent @/!/152.txt" /macroimage "Brawling_ComboLevel3" "Range" "powexectray 1 5$$bindloadfilesilent @/!/352.txt" @/!/151.txt ---------------- 1 "powexectray 2 5$$powexectoggleoff Ninja Run$$powexectoggleoff Beast Run$$powexectoggleoff Sprint$$powexectoggleoff Prestige Power Slide$$bindloadfilesilent @/!/152.txt" @/!/152.txt ---------------- 1 "powexectray 4 5$$powexectoggleoff Ninja Run$$powexectoggleoff Beast Run$$powexectoggleoff Sprint$$powexectoggleoff Prestige Power Slide$$bindloadfilesilent @/!/153.txt" @/!/153.txt ---------------- 1 "powexectray 6 5$$powexectoggleoff Ninja Run$$powexectoggleoff Beast Run$$powexectoggleoff Sprint$$powexectoggleoff Prestige Power Slide$$bindloadfilesilent @/!/154.txt" @/!/154.txt ---------------- 1 "powexectray 8 5$$powexectoggleoff Ninja Run$$powexectoggleoff Beast Run$$powexectoggleoff Sprint$$powexectoggleoff Prestige Power Slide$$bindloadfilesilent @/!/155.txt" @/!/155.txt ---------------- 1 "powexectray 10 5$$powexectoggleoff Ninja Run$$powexectoggleoff Beast Run$$powexectoggleoff Sprint$$powexectoggleoff Prestige Power Slide$$bindloadfilesilent @/!/151.txt" ---- @/!/351.txt ---------------- 3 "powexectray 1 5$$powexectoggleoff Ninja Run$$powexectoggleoff Beast Run$$powexectoggleoff Sprint$$powexectoggleoff Prestige Power Slide$$bindloadfilesilent @/!/352.txt" @/!/352.txt ---------------- 3 "powexectray 3 5$$powexectoggleoff Ninja Run$$powexectoggleoff Beast Run$$powexectoggleoff Sprint$$powexectoggleoff Prestige Power Slide$$bindloadfilesilent @/!/353.txt" @/!/353.txt ---------------- 3 "powexectray 5 5$$powexectoggleoff Ninja Run$$powexectoggleoff Beast Run$$powexectoggleoff Sprint$$powexectoggleoff Prestige Power Slide$$bindloadfilesilent @/!/354.txt" @/!/354.txt ---------------- 3 "powexectray 7 5$$powexectoggleoff Ninja Run$$powexectoggleoff Beast Run$$powexectoggleoff Sprint$$powexectoggleoff Prestige Power Slide$$bindloadfilesilent @/!/355.txt" @/!/355.txt ---------------- 3 "powexectray 9 5$$powexectoggleoff Ninja Run$$powexectoggleoff Beast Run$$powexectoggleoff Sprint$$powexectoggleoff Prestige Power Slide$$bindloadfilesilent @/!/351.txt" The toggleoff nonsense, is just something I tend to do. All my files have, seemingly irrelevant, commands peppered throughout. These were already there. I figure, if I'm pressing attack keys, a little resource conservation couldn't hurt. Absolutely irrelevant, here. 7. End of Life There's some value at higher levels, it makes an awesome little cruise control melee/range spammer. So yea, it' embarrassingly simple. The application, combined with the tray, has had enough impact, I'm willing to embarrass myself. Thanks for looking! Feel free to hit me up with any questions. @.zip
  13. qwy

    Guide Index

    i26 Guide: LeftDoubleClick Toggle, Another Twist on Global Teleport+Warshades Travel Binds | Binds | Binds for Specific Purposes i26 Unbindall (Keybindreset) I use it like it's an attack in the chain. A How to Recover Guide. How To Bind & Macro | Binds & Macros i26 Guide: BuildSaveFile; Navigating Relative Paths How To Bind & Macro | Binds & Macros i26 and beyond: The 5Chain Attack Assistant Binds for Specific Purposes | Introduction to Combat | Other Combat Mechanics i26 Expanded Mastermind NumPad Controls+ Binds for Specific Purposes | Binds & Macros | Remapping i26 The Mastermind's PetMouse Binds for Specific Purposes | Binds & Macros | Remapping
  14. i26 Unbindall (Keybindreset) I use it like it's an attack in the chain. A How to Recover Guide. by qwy Preamble Personally, I've found using them often means never really needing them. If you're unfamiliar they wipe your active (Client managed) bind file clean. It's all gone. No more binds you had a hand in. No option for recovering them. They have ceased to be. It probably sounds like I was being facetious with the title and first sentence. I wasn't. Commands adside, the result of a glitch, a hiccup loading a bind or even certain input errors can result in the same end effect. I used to use a popular movement based bind set that is constantly loading files. Often, as things started heating up, BOOM! Bindload misfire! Heavily modded keys, all make with the bye bye. Around the 112thteen time, is when I first met unbindall, our eye caught each other across a busy cmdlist. I knew right away, I was on a road to recovery. Of healing. We got pretty serious, right away. I learned some hard lessons in the beginning but, I kept looking for excuses to get together. Peppering bind files with it like a love struck middleschooler, defacing a textbook with the name of their first crush. The most meaningful of which is a reset on every alt, I hit constantly. The more I'd hit it the fewer problems I'd have. This is typically how I turn off ninja sprint or, beast surge, I can't even remember the last time I even had a problem. Unbindall is the wind that gives my alts wings, their license to soar. Example CTRL+R "up 0$$down 0$$forward 0$$backward 0$$left 0$$right 0$$camreset$$unbindall$$bindloadfilesilent @/Global.txt$$bindloadfilesilent @/Rojas/General.txt$$bindloadfilesilent @/1/A.txt$$bindloadfile @/Rojas/1/A/1.txt" 1. The First Step Without a few ducks lined up, ahead of time, this command is a bad day, waiting to happen. There's a lot of heads on this hydra. It's a little hard sticking to a single step and have it provide an actual value, on its own. I'm going to bounce around two key points with this and, recovery methods are going to get the most stage time. The second especially if, like me, you've got mad altoholism, is ongoing to be an evolution. It's certainly, the most daunting step, cultivating a global bind profile. If you just have a couple of characters and playing at lower levels, it's not important yet although, the concepts here will help you save and recover just as well. In all scenarios, knowing what's on the active file, what you actually want on it, what should be accessible to all alts, what the current character needs are, where the hell are all these files and how you're going to get them where they need to be, is a long road but it starts with knowing what you already have. That's where bindsave comes in. 2. Active, original and default files AKA Keybind.txt and the spectors. Even if you just have one main, getting familiar with some of the inner workings isn't a bad idea, if you've got a lot of advanced level alts, a global bind profile is a really good idea. A hot of the presses copy of the original bind file is a great start. That puts backing up your current active files on the table and of course, methods to back up and load. so, let's start by getting the client interface tools involved. Part way through, we're jumping on the fast track for a comparative argument on the value of this guide. We need to backup the active file and to get a fresh copy of the original file. We can't actually see either, only copies that are first, parsed in an order that's based on numerical values of key ID. More on that later. The one file we can see, is Keybind.txt, aka the default file. There seems to be an artifact of a default version of this file we can't see. It occasionally loads, onselect, of the big dropdown. It might not happen here however, check the work, along the way. It's not a problem these steps won't overcome, incidentally. Keybinds.txt is a long-term committed. love triangle with /bindsave and /bindload. Those commands are almost short enough to be a viable recovery plan using a slashcommand. For one alt, anyway. Navigate to the root of your installation folder. If you're having trouble, search for cityofheroes.exe, it's in the folder we want. Once you find it, copy and paste it right in the root, there. It might not be important, I actually don't even care what's on it. You might later, so, if that happens, there it is. If you're feeling confident, login an established alt, with lots of work done, or, for the less confident, there should be some of your influence on a new characters bind file if you want to roll a new one. If you're not sure, enter the following bind in to chat. Change CTRL+' , if you already have something on that it. 2.1 Test bind /bind CTRL+' "t $name, I'm a copy of the active file" In all cases, we have our copy of the root, we're logged in on a character, known to have an altered bind, let's save over the keybind.txt. Within the client, navigate to the option menu's, keymapping tab, and hit the top-right, blue button, "save to default". Go back to the game folder and copy and paste it again. Open up the copy, make sure you're seeing what you expected to see. The bind above should be on the second line, if you used it. So, "save to default", and, "load from default" are keybinds.txt's side pieces. Renaming the file between saves, you could backup all your toons this way. I wouldn't but, you get the idea. On left side of the keymapping tab, is the big dropdown, I mentioned, you could set it to original, hit save to default, go back to the folder, change the name of keybind.txt to global.txt, (this is that thing I keep talking about.) change the name of the copy we made before this one, back to keybinds.txt, navigate back to the options Keymapping tab and hit the second from top blue buttons or, just run this. 2.2 Back on the fast track /bindsave$$unbindall$$bindsavefile KeybindsNEW.txt$$bindload In fact, we could of skipped this whole thing with; 2.3 The step skipper /bindsavefile c:/CoH/UnbindBackup/Active.txt$$unbindall$$bindsavefile c:/CoH/UnbindBackup/OG-Fresh.txt$$bindload$$bindsavefile c:/CoH/UnbindBackup/OG-Root.txt$$bindloadfile c:/CoH/UnbindBackup/Active.txt The point was, to put in to perspective the difference between commands ready to trigger vs, relying on the interface alone. The keymapping tab's dropdown should probably stay on default however, the deeper down this rabbit hole, the less important the entire tab becomes. The command finished all the heavy lifting. The original copy was made and your active binds have been restored. Let's take a quick look at the new file. It should be in a folder named data with keybind.txt. Although, If you haven't already made a data folder, you don't have one. Make one now, it's good. Unnecessary here but, I'll have more on that in future guides. After you generated the data folder, before opening it, go to the piggs folder. Inside is KeybindsNEW.txt. Move it to the data folder and get familiar with it, before adding to it. Ideally, it grows into something useful for all your toons but, in those catastrophic moments, your binds are going to be down anyway, and this guide is about getting them back. Getting back on track, it's a catastrophe, your binds are down, this file, as it is now, those are the binds in play. Having had that bird's eye view, adds a bit of calm to the situation. Opposed to having your team watch you autorun, full frontal leeerroooyy style, in to the AV, while you're navigating to the blue buttons, let's take a look at some other options. 3. Back to the catastrophe The first thing we need is some backups. However, we're going to skip that for the time being. Ideally, they're created with commands, that can easily exceed the chat character limit. This brings popmenu's and custom.windows in to play. So, keep that in mind as we cover the restore options, below and, grab the commands for save and load, that suit you. With that, partly, out of the way, here are the choices; the big blue buttons, slashcommands, macros, popmenus and custom.windows. 3.1 Macros If they're already in your tray, it's fixed, game on! Otherwise, you'll have to get them there. Relative Path /macroimage "TalonsOfVengeance_MorbidCut" "SuperflySnuka" "camreset$$unbindall$$bindloadfilesilent Binds/global.txt$$bindloadfilesilent Binds/AT/general.txt$$bindloadfilesilent Backups/XXXX/binds.txt" Absolute Path /macroimage "TalonsOfVengeance_MorbidCut" "SuperflySnuka" "camreset$$unbindall$$bindloadfilesilent c:/CoX/Binds/global.txt$$bindloadfilesilent c:/CoX/Binds/AT/general.txt$$bindloadfilesilent c:/CoX/XXXX/general.txt$$bindloadfile c:/CoX/XXXX/build2binds.txt" /macroimage "TalonsOfVengeance_MorbidCut" "Custom Window" "customwindowtoggle ." /macroimage "TalonsOfVengeance_MorbidCut" "my pop" "popmenu NameOfWindow" The first one works for a basic global environment. It grabs the global bind file, a bind file, unique to that AT and another one unique to the active environment (build, interface or play style) Edited for your situation, it's like nothing even happened. The other two, just move the situation to step 2. Without the legwork upfront, none of them excel. 3.2 Popmenu - and, why not? 2.1 True, the bindload option requires a reboot. But, if you command the command to command chat to write the command... Relative Path: Option "Recover" <&show chat$$beginchat /"chatloadfile Backups/XXXX/chat.txt$$optionloadfile Backups/XXXX/options.txt$$wdwloadfile Backups/XXXX/wdw.txt$$bindloadfile Binds/global.txt$$bindloadfile Binds/AT/general.txt$$bindloadfile Backups/XXXX/binds.txt"&> Option "Bu&tton Machine" "show chat$$beginchat /bindloadfile binds/Macros.txt" --- Absolute Path: Option "Recover" <&show chat$$beginchat /"chatloadfile c:/CoX/XXXX/chat.txt$$optionloadfile c:/CoX/XXXX/options.txt$$wdwloadfile c:/CoX/XXXX/wdw.txt$$bindloadfile c:/CoX/Binds/global.txt$$bindloadfile c:/CoX/Binds/AT/general.txt$$bindloadfile c:/CoX/XXXX/binds.txt"&> Option "Bu&tton Machine" "show chat$$beginchat /bindloadfile c:/CoX/binds/Macros.txt" ...and, press enter. Voila! The first option loads the window preferences, chat setup, options settings and the 3 bind files for the global scenario I mentioned above. With the character limit raised, we're far from having to worry about command lengths. The second, a macro button machine file (patent pending). WIth this idea, once this file is loaded, the keys will generate macros that perform whatever variety of commands you can think of. Here's an example. 1 macroimage Brawling_ComboLevel1 Melee "powexectray 2 5$$gototray 9$$bindloadfilesilent @/!/152.txt" 3 macroimage Brawling_ComboLevel3 Range "powexectray 1 5$$gototray 9$$bindloadfilesilent @/!/352.txt" Q "macroimage TalonsOfVengeance_MorbidCut Q targetcustomnext enemy Quantum" E "macroimage v_archetypeicon_stalker E beginchat /bind E targetcustomnext notteammate notmypet base " Example macros were readily available for cut and paste. they're kind of useless here 2.2 Popmenu/sub menu Here's an example submenu with a reset macro to restore individual alts? Menu "Oh yes" { Divider Title "- There Here-" Title "The Dream Team is Here" Divider Divider Option "Super Fly Snuka" <&macroimage TalonsOfVengeance_MorbidCut "Super fly" "bindloadfilesilent @/Global.txt$$bindloadfilesilent @/Snuks/General.txt$$bindloadfilesilent @/Snuks/RelevantPathStuff/binds.txt"&> Option "Jack the Snake" <&macroimage TalonsOfVengeance_MorbidCut "Jake the Snake" "bindloadfilesilent @/Global.txt$$bindloadfilesilent @/Snakie/General.txt$$bindloadfilesilent @/Snakie/RelevantPathStuff/binds.txt"&> Option "Iron Shiek" <&macroimage TalonsOfVengeance_MorbidCut "Iron Shiek" "bindloadfilesilent @/Global.txt$$bindloadfilesilent @/Shiknessest/General.txt$$bindloadfilesilent @/Shiknessest/RelevantPathStuff/binds.txt"&> Divider } In all cases, access to a popmenu, is going to need a non-bind solution to make it pop (Read, Macro). With the potential of hotkeys though, once it's open, it's got a bunch of potential to help keep you alive until binds are back up. Either way, not a bad option to keep in your back pocket. 3.3 custom.window By far, the best choice, in this particular circumstance, in my opinion. No need to look for it, no confusing it with something else and depending on a couple of other factors, a character limit, well above anything we'd want here. Window . 0 0 100 150 Button "" "" Button Apps "macro_image GenericPower_AutoOverlay APPS popmenu APPS" Button "" "" Button ToonLaunch3000 "" Button Relative "unbindall$$bindloadfilesilent XXXX/global.txt$$chatloadfile XXXX/chat.txt$$optionloadfile XXXX/options.txt$$wdwloadfile XXXX/wdw.txt$$bindloadfilesilent Binds/AT/XXXX.txt$$bindloadfilesilent XXXX/General.txt$$bindloadfilesilent XXXX/build1binds.txt" Button "" "" Button "" "" Button Absolute "unbindall$$bindloadfilesilent c./CoX/XXXX/global.txt$$chatloadfile c./CoX/XXXX/chat.txt$$optionloadfile c./CoX/XXXX/options.txt$$wdwloadfile c./CoX/XXXX/wdw.txt$$bindloadfilesilent c./CoX/Binds/AT/XXXX.txt$$bindloadfilesilent c./CoX/XXXX/General.txt$$bindloadfilesilent c./CoX/XXXX/build1binds.txt" Button --- "" Button Macros "" Button "Super Fly Snuka" <&macroimage TalonsOfVengeance_MorbidCut "Super fly" "bindloadfilesilent @/Global.txt$$bindloadfilesilent @/Snuks/General.txt$$bindloadfilesilent @/Snuks/RelevantPathStuff/binds.txt"&> Button --- "" Button "" "" Open 0 End Example: Snipped from custom.window. Yea, I named it, ".". 4. Adding the ability to use Custom and Pop menus The stickied guides for adding these menus are great! Easy to understand and the options themselves, won't require as many steps as I've got here. I've got a lot to learn. I'm more inclined to experiment. Blowing up stuff is more fun than documenting an explosion. I've really got a lot to learn... Check out those guides, if you haven't. Then, set yourself up with a couple of options to restore. 5. Generating the backups to load So, the commands that save are the same as the ones to load, the only difference, is the actual word, "save" and "load". Once you've decided which option you'd like to use, edit the paths, "XXXX" as the character name and make a copy of it. From there, change the, "loads" to, "save" or the, "saves" to, "load", leaving you with a matched set. Don't forget to save after big changes, high holidays and on leap years. Get a real text editor, if you don't have one and lookout for future guides, exploring the potential of file managed, global profiles. 6. Anti-climatic conclusion and... unbindall, the reason it hasn't stomped out my spirit? Combined with a following bindload, or series of bindloads, in a single command, they all happen around the same time. You always want to write them in the order you want to execute. Consider the last string in section 2, there would have been no need to go to the install folder at all, it generates an archive folder and saves the active bind file, unbinds everything and saves a copy of it in the new folder, and uploads the original keybind.txt and saves a copy to the new folder and than loads the original active bind file like nothing even happened. As I was writing this out, I decided to test what would happen if I shuffled the order, some of the results were unexpected so, it never hurts to test things under controlled environments. Ultimately, the first pass was the plan I was trying to execute and in that order, it did exactly that. Disclaimer If any additions, corrections, errors or elaboration stand out, let me know. If anyone recognizes work that should be contributed to another author, I'm more than happy to remove, extend credit or take whatever steps are appropriate to remedy the situation. Hope this is helpful.
  15. I have a lvl50 Stone Tank, lvl50 Warshade, lvl50 Peacebringer and other characters with teleport or, mystic flight. Along the way, I've come to know what I like and don't like. I also have a lot of binds and a lot of alts, leading me, like a lot of people I'd guess, to start putting energy in to one global profile to cover as much as makes sense and smaller profiles for toons that develop out of it. I'm up to 11 level 50s in all so, that global has matured a lot along the way. There's great guides on this topic already. They've definitely helped steer me along the way. if this is something you're interested in, I highly recommend checking the previous posts for more information. This guide will be focused on what I haven't come across yet. Couple quick things, 1. I haven't tried Jaunt yet. I suspect this works but it hasn't been tested. With P2W flight and Ninja/Beast Run, I don't tend to lean towards travel powers like back in live. My stone tank's run speed at almost 70mph. KInd of an extreme example although, at an average of 60mph on others... anyway. 2. I've messed around with powexeclocation but ultimately, my preference for teleport is excename. I use powexeclocation for other things and I'm fairly confident it can be used here, interchangeably. 3. I only like LeftDoubleClick, sometimes. I use the client to grab a, "fresh off the press" copy of keybind.txt as the base for my global file. I splurged on some extra characters and named it Global.txt. This first bit goes in there. @/Global.txt SHIFT+LBUTTON "powexecname Translocation$$powexecname Jaunt$$powexecname Teleport$$powexecname White Dwarf Step$$powexecname Shadow Step" LeftDoubleClick nop CTRL+LeftDoubleClick "bindloadfilesilent @/!/LDCTP1.txt" My active binds are kept in the Install/data folder. My subfolder is, "@", where all the binds go. CTRL+LeftDoubleClick loads a file to mimic SHIFT+LBUTTON. It's in another subfolder named, "!". It's for anything global, Global.txt couldn't manage alone. Edit to taste. @/!/LDCTP1.txt LeftDoubleClick "powexecname Translocation$$powexecname Jaunt$$powexecname Teleport$$powexecname White Dwarf Step$$powexecname Shadow Step" CTRL+LeftDoubleClick "bindloadfilesilent @/!/LDCTP0.txt" CTRL+: Flips LeftDoubleClick back to my preferred default, off. @/!/LDCTP0.txt LeftDoubleClick nop CTRL+LeftDoubleClick "bindloadfilesilent @/!/LDCTP1.txt" This manages itself until the next reset. Warshade Minimum So, on to warshades. We have Shadow Step covered, so Dwarf is all we're missing. I'm using, a minimalist global folder structure here. Everyone has their own methods, so I wanted to present a, "just the facts" version to illustrate my thinking and conforms to other methods with less to cut. Afterwards, a puffed-up opinion piece, closer to what I use. That being said, Essentially, I'm mimicing the above. 1. @/WSToonName/NotDwarfBinds.txt - Minimum <KEY1> "powexectoggleon Black Dwarf$$bindloadfilesilent @/Global.txt$$bindloadfilesilent @/WSToonName/IsDwarfBinds.txt" This is a bare minimum option. <KEY1> loads the Dwarf binds. 2. @/WSToonName/IsDwarfBinds.txt - Minimum SHIFT+LBUTTON powexecname Black Dwarf Step LeftDoubleClick powexecname Black Dwarf Step CTRL+LeftDoubleClick "bindloadfilesilent @/!/WS-LDCTP0.txt" <KEY2> "powexectoggleoff Black Dwarf$$bindloadfilesilent @/Global.txt$$bindloadfilesilent @/WSToonName/NotDwarfBinds.txt" Unlike the multi power option, I prefer LeftDoubleClick's default is functional if I go Dwarf. <KEY2>, pops back to human form and Shadow Step is restored. 3. @/!/WS-LDCTP0.txt - Minimum LeftDoubleClick nop CTRL+LeftDoubleClick "bindloadfilesilent @/!/WS-LDCTP1.txt" This keeps the activity, back and forth, in the global folder . 4. @/!/WS-LDCTP1.txt - Minimum LeftDoubleClick powexecname Black Dwarf Step CTRL+LeftDoubleClick "bindloadfilesilent @/!/WS-LDCTP0.txt" And, like the first bit, this manages itself until <KEY2> gets pressed. Then, were back to square one. WIth that, the teleport part is finished. It's nothing fancy but, hopefully useful. Warshade Options So, here's a little more QOL and global flexibility. The teleport part is essentially the same. For anyone just getting familiar with this, we're rolling binds. Anyone who's spent any time with them will testify, interrupts, too-much-too-fast keyboard action or occasional glitches can knock them out of sync. With easy access to reset them, it's hardly worth mentioning. WIthout, possible disaster. Likely frustration. There's a lot of ways to do this and, here's a couple I use a variation of. 1. @/Nictus/BuildWithDwarf/NotDwarfBinds.txt SHIFT+1 "powexectoggleon Dark Nova$$windowhide Tray7$$gototray 4$$unbindall$$bindloadfilesilent @/Global.txt$$bindloadfilesilent @/Nictus/General.txt$$bindloadfilesilent @/!/Kheld.txt$$bindloadfilesilent @/Nictus/BuildWithNova/IsNovaBinds.txt" SHIFT+3 "powexectoggleon Black Dwarf$$windowhide tray7$$gototray 4$$unbindall$$bindloadfilesilent @/Global.txt$$bindloadfilesilent @/Nictus/General.txt$$bindloadfilesilent @/!/Kheld.txt$$bindloadfilesilent @/Nictus/BuildWithDwarf/IsDwarfBinds.txt" SHIFT+C "+$$powexectoggleon Penumbral Shield$$powexectoggleon Twilight Shield$$powexectoggleon Gravity Shield" CTRL+C "powexectoggleoff Black Dwarf$$powexectoggleoff Dark Nova$$windowshow tray7$$gototray 9$$unbindall$$bindloadfilesilent @/Global.txt$$bindloadfilesilent @/Nictus/General.txt$$bindloadfilesilent @/Nictus/BuildWithDwarf/NotDwarfBinds" CTRL+R "up 0$$down 0$$forward 0$$backward 0$$left 0$$right 0$$camreset$$unbindall$$bindloadfilesilent @/Global.txt$$bindloadfilesilent @/Nictus/General.txt$$bindloadfilesilent @/Nictus/BuildWithDwarf/NotDwarfBinds.txt" I've added spaces, for legibility, that will need to be deleted before using. The rest of these can be edited for your pleasure. The Keys are relevant accept to illustrate one of the QOL pieces. SHIFT+1: Only added to illustrate where toggling on Nova fits in. SHIFT+3: Toggles Dwarf on, handles some window & tray stuff and then the binds load as follows. unbindall: I use this like it's part of an attack chain. Personally, I've found using it often means not really needing it. *(READ FOOTNOTE BEFORE USE!!) Global.tx: Now, it's my personal clean slate. Nictus/AllBuildBInds.txt: The Character's general binds load to catch Global overrides or, anything unique. Kheld.txt: I have global file for both forms, shared by PBs & WS so, Kheld.txt... This would be where it goes, if you do to otherwise, it's dead to us. BuildWithDwarf/NotDwarfBinds.txt: I spend more time on the human form so, a division. SHIFT+C: Notice the +$$ in the front, that's why I added the key names, it serves two functions In human, it kicks on two shields at once. More importantly, it picks up a cue from SHIFT+C in the next file and kicks on gravity shield, coming out of the other forms. If there's a bind issue, it buys a little time. CTRL+C: Emergency protocol if anything interrupted SHIFT+C. In most cases, rolling SHIFT+C works so, another key is the only choice for insurance. (Unbindall is in here too.) CTRL+R: Restores default NotDwarf state. I use this command for reset on everything. (Unbindall is in here too.) 2. @/Nictus/BuildWithDwarf/IsDwarfBinds.txt SHIFT+LBUTTON powexecname Black Dwarf Step LeftDoubleClick powexecname Black Dwarf Step CTRL+LeftDoubleClick "bindloadfilesilent @/!/Kheld/WS-LDCTP0.txt" SHIFT+3 "windowhide tray7$$gototray 4" SHIFT+C "-$$powexectoggleoff Black Dwarf$$powexectoggleoff Dark Nova$$windowshow Tray7$$gototray 9$$unbindall$$bindloadfilesilent @/Global.txt$$bindloadfilesilent @/Nictus/AllBuildBinds.txt$$bindloadfilesilent @/Nictus/BuildWithDwarf/NotDwarfBinds.txt" CTRL+C nop CTRL+R "up 0$$down 0$$forward 0$$backward 0$$left 0$$right 0$$camreset$$unbindall$$bindloadfilesilent @/Global.txt$$bindloadfilesilent @/Nictus/General.txt$$bindloadfilesilent @/!/Kheld.txt$$bindloadfilesilent @/Nictus/BuildWithDwarf/IsDwarfBinds.txt" The teleport binds show up again. The path added a subfolder named /Kheld/ which isn't necessary. It's only there to further illustrate the global purpose. SHIFT+1: Is gone, carried over from the last file and still toggles Nova on. SHIFT+3: We're in Dwarf so, this just maintains the window and tray stuff. SHIFT+C: Starts with -$$ to carry over to the last SHIFT+C command and auto toggle a primary shield. Both forms are toggled off, window & tray stuff then load the previous state. (Unbindall is in here too.) CTRL+C: With the rolling bind on SHIFT+C having more to offer, I only wanted CTRL+C if, SHIFT+C fails. Deleting it here, preserves its original command if, preferred. CTRL+R: Restores default NotDwarf state. I use this command for reset on everything. (Unbindall is in here too.) The last two steps from the Minimum version are nearly identical. Only the paths have changed to protect the innocent. We went from, @/!/WS-LDCTP0.txt to. @/!/Kheld/WS-LDCTP0.txt. *UNBINDALL/KEYBINDRESET: These two commands are identical. They will wipe your active (Client managed) bind file clean. You won't be able to recover what was lost. Bindsavefile, managing files locally and knowing what you need to load and when, is imperative to successfully implementing either of these. If you're not sure what these do, don't use them without doing some homework. I apologize for endlessly nagging about this. I'd just hate to find out, I was the guy that walked you through vaporizing your data, like it didn't matter. If this tutorial was helpful, I posted a recovery guide right here. Thanks for checking out the guide! Let me know If there's any corrections, improvements or elaboration in order.
×
×
  • Create New...