Avernal
-
Posts
47 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Store
Articles
Patch Notes
Posts posted by Avernal
-
-
5 hours ago, Ukase said:
While I appreciate the tip, for this guy, that's taking things way too far. It's just too convoluted for me to wrap my head around.
It really isn't. It's as simple as saving those four files to your settings/live/binds subfolder and typing /bindloadfile "binds\TBH1.txt" in chat. After that everything is automatic. -
On 10/26/2024 at 5:34 AM, Ukase said:
So, I appreciate your suggestions.
The thing is - if I put TB on auto, then I have to manually click hasten (although, fair enough, not as frequently)
Bit of a thread necro, but I'm levelling a Ice/Marine Corruptor myself and spotted this comment, which I think I can help with.
You can use rotating bind files to automate more than one power being on auto.
Example from my own (all saved in settings/live/binds with the indicated filename). In practice this will swap Hasten and Toroidal Bubble as the auto power whenever you move/jump/fly down with CTRL, activate any of your powers, click either mouse button or use mouse thumb buttons to trigger things. I usually have my alt tray set-up with a build up/aim power in slot 1, healing or utility in slot 2, then shift+thumb buttons follow suit with another damage buff in slot 3 and another heal/utility (usually an end heal etc.) in slot 4.
TBH1.txtW "+forward$$bindloadfilesilent binds\TBH2.txt" A "+left$$bindloadfilesilent binds\TBH2.txt" S "+backward$$bindloadfilesilent binds\TBH2.txt" D "+right$$bindloadfilesilent binds\TBH2.txt" SPACE "+up$$bindloadfilesilent binds\TBH2.txt" CTRL "+down$$bindloadfilesilent binds\TBH2.txt" TAB "unselect$$powexec_unqueue$$target_enemy_near$$bindloadfilesilent binds\TBH2.txt" BUTTON4 "powexecaltslot 2$$bindloadfilesilent binds\TBH2.txt" SHIFT+BUTTON4 "powexecaltslot 4$$bindloadfilesilent binds\TBH2.txt" BUTTON5 "powexecaltslot 1$$bindloadfilesilent binds\TBH2.txt" SHIFT+BUTTON5 "powexecaltslot 3$$bindloadfilesilent binds\TBH2.txt" LBUTTON "+ $$- $$bindloadfilesilent binds\TBH2.txt" RBUTTON "+mouselook$$bindloadfilesilent binds\TBH2.txt" 0 "powexecslot 10$$bindloadfilesilent binds\TBH2.txt" 1 "powexecslot 1$$bindloadfilesilent binds\TBH2.txt" 2 "powexecslot 2$$bindloadfilesilent binds\TBH2.txt" 3 "powexecslot 3$$bindloadfilesilent binds\TBH2.txt" 4 "powexecslot 4$$bindloadfilesilent binds\TBH2.txt" 5 "powexecslot 5$$bindloadfilesilent binds\TBH2.txt" 6 "powexecslot 6$$bindloadfilesilent binds\TBH2.txt" 7 "powexecslot 7$$bindloadfilesilent binds\TBH2.txt" 8 "powexecslot 8$$bindloadfilesilent binds\TBH2.txt" 9 "powexecslot 9$$bindloadfilesilent binds\TBH2.txt"
TBH2.txtW "+forward$$powexecauto hasten$$bindloadfilesilent binds\TBH3.txt" A "+left$$powexecauto hasten$$bindloadfilesilent binds\TBH3.txt" S "+backward$$powexecauto hasten$$bindloadfilesilent binds\TBH3.txt" D "+right$$powexecauto hasten$$bindloadfilesilent binds\TBH3.txt" SPACE "+up$$powexecauto hasten$$bindloadfilesilent binds\TBH3.txt" CTRL "+down$$powexecauto hasten$$bindloadfilesilent binds\TBH3.txt" TAB "unselect$$powexec_unqueue$$target_enemy_near$$powexecauto hasten$$bindloadfilesilent binds\TBH3.txt" BUTTON4 "powexecaltslot 2$$powexecauto hasten$$bindloadfilesilent binds\TBH3.txt" SHIFT+BUTTON4 "powexecaltslot 4$$powexecauto hasten$$bindloadfilesilent binds\TBH3.txt" BUTTON5 "powexecaltslot 1$$powexecauto hasten$$bindloadfilesilent binds\TBH3.txt" SHIFT+BUTTON5 "powexecaltslot 3$$powexecauto hasten$$bindloadfilesilent binds\TBH3.txt" LBUTTON "+ $$- $$powexecauto hasten$$bindloadfilesilent binds\TBH3.txt" RBUTTON "+mouselook$$powexecauto hasten$$bindloadfilesilent binds\TBH3.txt" 0 "powexecslot 10$$powexecauto hasten$$bindloadfilesilent binds\TBH3.txt" 1 "powexecslot 1$$powexecauto hasten$$bindloadfilesilent binds\TBH3.txt" 2 "powexecslot 2$$powexecauto hasten$$bindloadfilesilent binds\TBH3.txt" 3 "powexecslot 3$$powexecauto hasten$$bindloadfilesilent binds\TBH3.txt" 4 "powexecslot 4$$powexecauto hasten$$bindloadfilesilent binds\TBH3.txt" 5 "powexecslot 5$$powexecauto hasten$$bindloadfilesilent binds\TBH3.txt" 6 "powexecslot 6$$powexecauto hasten$$bindloadfilesilent binds\TBH3.txt" 7 "powexecslot 7$$powexecauto hasten$$bindloadfilesilent binds\TBH3.txt" 8 "powexecslot 8$$powexecauto hasten$$bindloadfilesilent binds\TBH3.txt" 9 "powexecslot 9$$powexecauto hasten$$bindloadfilesilent binds\TBH3.txt"
TBH3.txtW "+forward$$bindloadfilesilent binds\TBH4.txt" A "+left$$bindloadfilesilent binds\TBH4.txt" S "+backward$$bindloadfilesilent binds\TBH4.txt" D "+right$$bindloadfilesilent binds\TBH4.txt" SPACE "+up$$bindloadfilesilent binds\TBH4.txt" CTRL "+down$$bindloadfilesilent binds\TBH4.txt" TAB "unselect$$powexec_unqueue$$target_enemy_near$$bindloadfilesilent binds\TBH4.txt" BUTTON4 "powexecaltslot 2$$bindloadfilesilent binds\TBH4.txt" SHIFT+BUTTON4 "powexecaltslot 4$$bindloadfilesilent binds\TBH4.txt" BUTTON5 "powexecaltslot 1$$bindloadfilesilent binds\TBH4.txt" SHIFT+BUTTON5 "powexecaltslot 3$$bindloadfilesilent binds\TBH4.txt" LBUTTON "+ $$- $$bindloadfilesilent binds\TBH4.txt" RBUTTON "+mouselook$$bindloadfilesilent binds\TBH4.txt" 0 "powexecslot 10$$bindloadfilesilent binds\TBH4.txt" 1 "powexecslot 1$$bindloadfilesilent binds\TBH4.txt" 2 "powexecslot 2$$bindloadfilesilent binds\TBH4.txt" 3 "powexecslot 3$$bindloadfilesilent binds\TBH4.txt" 4 "powexecslot 4$$bindloadfilesilent binds\TBH4.txt" 5 "powexecslot 5$$bindloadfilesilent binds\TBH4.txt" 6 "powexecslot 6$$bindloadfilesilent binds\TBH4.txt" 7 "powexecslot 7$$bindloadfilesilent binds\TBH4.txt" 8 "powexecslot 8$$bindloadfilesilent binds\TBH4.txt" 9 "powexecslot 9$$bindloadfilesilent binds\TBH4.txt"
TBH4.txtW "+forward$$powexecauto Toroidal Bubble$$bindloadfilesilent binds\TBH1.txt" A "+left$$powexecauto Toroidal Bubble$$bindloadfilesilent binds\TBH1.txt" S "+backward$$powexecauto Toroidal Bubble$$bindloadfilesilent binds\TBH1.txt" D "+right$$powexecauto Toroidal Bubble$$bindloadfilesilent binds\TBH1.txt" SPACE "+up$$powexecauto Toroidal Bubble$$bindloadfilesilent binds\TBH1.txt" CTRL "+down$$powexecauto Toroidal Bubble$$bindloadfilesilent binds\TBH1.txt" TAB "unselect$$powexec_unqueue$$target_enemy_near$$powexecauto Toroidal Bubble$$bindloadfilesilent binds\TBH1.txt" BUTTON4 "powexecaltslot 2$$powexecauto Toroidal Bubble$$bindloadfilesilent binds\TBH1.txt" SHIFT+BUTTON4 "powexecaltslot 4$$powexecauto Toroidal Bubble$$bindloadfilesilent binds\TBH1.txt" BUTTON5 "powexecaltslot 1$$powexecauto Toroidal Bubble$$bindloadfilesilent binds\TBH1.txt" SHIFT+BUTTON5 "powexecaltslot 3$$powexecauto Toroidal Bubble$$bindloadfilesilent binds\TBH1.txt" LBUTTON "+ $$- $$powexecauto Toroidal Bubble$$bindloadfilesilent binds\TBH1.txt" RBUTTON "+mouselook$$powexecauto Toroidal Bubble$$bindloadfilesilent binds\TBH1.txt" 0 "powexecslot 10$$powexecauto Toroidal Bubble$$bindloadfilesilent binds\TBH1.txt" 1 "powexecslot 1$$powexecauto Toroidal Bubble$$bindloadfilesilent binds\TBH1.txt" 2 "powexecslot 2$$powexecauto Toroidal Bubble$$bindloadfilesilent binds\TBH1.txt" 3 "powexecslot 3$$powexecauto Toroidal Bubble$$bindloadfilesilent binds\TBH1.txt" 4 "powexecslot 4$$powexecauto Toroidal Bubble$$bindloadfilesilent binds\TBH1.txt" 5 "powexecslot 5$$powexecauto Toroidal Bubble$$bindloadfilesilent binds\TBH1.txt" 6 "powexecslot 6$$powexecauto Toroidal Bubble$$bindloadfilesilent binds\TBH1.txt" 7 "powexecslot 7$$powexecauto Toroidal Bubble$$bindloadfilesilent binds\TBH1.txt" 8 "powexecslot 8$$powexecauto Toroidal Bubble$$bindloadfilesilent binds\TBH1.txt" 9 "powexecslot 9$$powexecauto Toroidal Bubble$$bindloadfilesilent binds\TBH1.txt"
-
Just for clarity on the above - make sure the entire bind within the quotation marks does not exceed around 235 characters. If you work within that constraint you should not get errors, exceeding that number causes the game to cut off the end (causing error messages), which is probably what happened with your original taunt bind.
As an example - each of these are considered 86 characters (the entire section inside the quotations) - keep your taunt messages short enough that the total bind doesn't exceed 235 characters:
Taunt1.txt"+ $$- $$powexecname Taunt$$say Taunt message 1$$bindloadfilesilent c:\binds\taunt2.txt"Taunt2.txt
"+ $$- $$powexecname Taunt$$say Taunt message 2$$bindloadfilesilent c:\binds\taunt3.txt"Taunt3.txt
"+ $$- $$powexecname Taunt$$say Taunt message 3$$bindloadfilesilent c:\binds\taunt4.txt"Taunt4.txt
"+ $$- $$powexecname Taunt$$say Taunt message 4$$bindloadfilesilent c:\binds\taunt1.txt"
In practice that is going to queue Taunt and say one message when you push the key down, then it'll queue Taunt again and say the next message when you release the key. If you only want it to do one thing per button press, remove "+ $$- $$" from the beginning of each.
Use things like the "+ " and "- ", removing underscores from slash commands and a relative bind path to trim down the length of your commands. For a relative bind path you just put all your binds into your "homecoming/settings/live" subfolder and you can then use "bindloadfilesilent taunt1.txt" without any path, or create a binds subfolder inside of that and use "bindloadfilesilent binds\taunt1.txt". Might not seem like much but trimming the length down even by a few characters helps with rotating bind files. -
On 2/3/2025 at 11:50 AM, Maelwys said:
FWIW; if you're having trouble with two commands not being able to kick in simultaneously on a single button press; you can try something like:
[c:\Temp\cohbind1.txt]
KEY "+down$$-down$$command1$$bind_load_file_silent c:\Temp\cohbind2.txt"
[c:\Temp\cohbind2.txt]
KEY "+down$$-down$$command2$$bind_load_file_silent c:\Temp\cohbind1.txt"
Holding down KEY will activate the first command and load the second bindfile... and releasing KEY will activate the second command and load the first bindfile.
Pressing KEY (holding then releasing) should do both providing the first command doesn't take too long to process/activate (in which case it'll usually just queue it up)
Don't even need the 'down' in there - you can do:"+ $$- $$"Binds are limited to around 235-240ish characters before they start glitching out, if you exceed that it will indeed break your rotating binds (which is what I suspect happened for the OP). So using fewer characters is an all around win and a single space is the shortest version of those two-state bind rotations. You can remove all the underscores from 'commands_like_this' also, 'commandslikethis' does the same thing.
-
Got a friend who is playing City of Heroes for the first time in 2024, loves pet classes so made a Mastermind, but is colourblind. Made this little cheat sheet image for him and figured it'd be useful to others so am sharing here too.
-
2
-
-
Simple idea that would add a good bit of QoL to bind files. Powexec_auto requires you to use an actual power name for the bind rather than a tray slot number, adding a powexec_auto_slot command would allow people to instead make a single bind that sets that tray slot number to your auto queued power.
Essentially you'd be able to use something like the following to queue the first tray slot in your main/second/third power tray, so on and so forth:powexecautoslot 1 powexecautoaltslot 1 powexecautoalt2slot 1
It'd be a huge QoL improvement for people using say Perma-Dom builds that are using the bind file loops discussed here: -
On 12/11/2022 at 9:07 PM, BlackSpectre said:
As you know, one of the big problems with using /monitor_attribute with binds is the dang 256 character limit! Not only is the slash command long, but the attribute names are also very long. I did some poking around and discovered several number codes and a bunch of random letters for attribute names. I also found out the command searches for the attribute names using some sort of inconsistent text or pattern matching that helped me figure out some abbreviations.
There is a known bug with the command that prevents the use of "Energy Defense" and "Energy Resistance" as attribute names. When those names are used, "Negative Energy Defense" and "Negative Energy Resistance" pop up instead. Luckily, I discovered you can use the number "7" as a substitute name for "Energy Defense", and "DamageType[4]" as a substitute name for "Energy Resistance."
Anyway, here's the list of codes and abbreviations I came up with (I also updated the Wiki with this info):
1=Toxic Defense
2=AoE Defense
3=Smashing Defense
4=Lethal Defense
5=Fire Defense
6=Cold Defense
7=Energy Defense
8=Negative Energy Defense
9=Psionic Defense
ED=Ranged Defense
MEL=Melee DefenseBAS=Base Defense
L R=Lethal Resistance
G R=Smashing Resistance
RE R=Fire Resistance
Cold R=Cold Resistance
GY R=Negative Energy Resistance
NIC R=Psionic Resistance
C R= Toxic ResistanceDamageType[4]=Energy Resistance
CC=Accuracy Bonus
SE P=Confuse Protection
T E=Current Endurance
NT H=Current Hit Points
DA=Damage Bonus
SU=Endurance Consumption
XP=Experience Debt
XT=Experience to Next Level
D P=Hold Protection
INF=Influence
NH=Inherent
TC=Last Hit Chance
DS=Level Shift
X H=Max Hit Points
ME B=Recharge Time Bonus
Y RA= Recovery Rate
RA=Regeneration Rate
PVE=Stealth Radius (PvE)
T B=To Hit Bonus
FL=Flying Speed
PI=Jumping Speed
RU=Run Speed
This is great, messing around with it to try and slimline the number of required bind files - there is a mistake in your code for Regeneration Rate though - it seems to call 'Regeneration Resistance', reckon you can find the right shorthand for it? -
I've been forced to do another 2.25hrs of actual work this morning AND grocery shopping in the world outside as a result of server outages. This is wholly unacceptable. 😐
-
1
-
-
Edited first post and updated with a blank template file so it's easier to make your own copies for other queued powers.
-
I bet you could make this dynamically able to jump back up a tier (to a lesser damage state) by setting up a bind in every file for powexecaltslot 1, 2 and 3 (where you have your healing abilities) that makes the bind loop jump back one or more stages. That way as you're activating Dull Pain etc. during normal gameplay your costume reflects that. Shame about the cooldown on CC though.
-
On 6/20/2021 at 12:11 PM, SmalltalkJava said:
this is great!
I adapted this for my electric heals and absorb. But I noticed that if I don't have anything targeted then the ability in the first file doesn't go off. the nearest freindly is targeted. But no ability firing on the Key down. When I release the key, then the second ability does fire off. It works great if I already have the nearest friendly targeted.
v "+ $$- $$targetcustomnear friend alive$$powexecname Insulating Circuit$$bindloadfile binds/electricbuff2.txt"
and
v "+ $$- $$powexecname Rejuvenating Circuit$$bindloadfile binds/electricbuff.txt"
Does it behave that way regardless of which targeting method you use? I noticed you're using near instead of next, the behaviour is the same on both? -
So, I did 15mins of work... 😣😐
It's been a dark, dark day in history.-
5
-
1
-
-
1 minute ago, kinterra3050 said:
Do we know why they're down?
Their discord updates seem to suggest they think that OVH's general maintenance is somehow affecting their servers-
1
-
-
I can't handle the pressure! Don't do it! You can't make me!
You can almost hear the collective sigh of the CoH community right now. 😆-
1
-
3
-
1
-
-
6 hours ago, SmalltalkJava said:
I have tried /bind shift+lbutton petcomall goto$$petcomall attack when i have a mob target and it just does the "goto" part. I use /bind SHIFT+LBUTTON petcomall goto
Try doing that as two files and using the push-toggle trick, see if that works:
goto1.txtSHIFT+LBUTTON "+ $$- $$petcomall goto$$say Alright!$$bindloadfilesilent goto2.txt"
goto2.txtSHIFT+LBUTTON "+ $$- $$petcomall attack$$say Get this clown!$$bindloadfilesilent goto1.txt"
It'll run step 1 as you hold the buttons down and step 2 as you release, might be a way to get it working but let me know how it goes. -
Only just spotted this now or would've answered sooner.
The Advanced Binds topic is something I update and improve fairly regularly if I find a smoother way to do it, and it's all written with a plain English explanation of WHY something is typed a certain way, WHAT the files are to be named and WHERE you need to save them. Even if you don't understand everything that's going on in them 100% it'll explain a good chunk of it so you better understand similar stuff in future and you can literally just copy & paste the code bits in to a text file and save them where it tells you. You don't need to understand them to use it. -
Updated again and now recommend using the two bind version as it's smoother, runs the conversions more frequently and seems to produce better and more consistent results for your damage output than the three file version. Added an explanation of how I got my mouse side button binds down in size to allow them to be included in the convert rotation and a screenshot of my powers tray and mouse so it's easier to understand how those longer strings work.
Some explanations for the changes to the binds:
With movement keys and left/right mouse function - the default binding *needs to come first*, before the convert insps string, or the key will get 'stuck'. (E.G. "+mouselook$$whatever_else_here" works but if you use "whatever_else_here$$+mouselook" it will break and you'll be stuck in mouselook mode, or forward if you did it on W, etc. etc.)
With the number keys for powers, the mouse side buttons etc. - you can (and should) put the default binding AFTER the convert insps string. This will stop any powers you've queued to activate by hitting a key from getting unqueued or weird hitches. (E.G. for the 1-0 keys and BUTTON4 + BUTTON5 you want "whatever_else_here$$+powexecslot 1" instead of "powexecslot 1$$whatever_else_here")
BUTTON4 "powexecname Healing Flames" is just longer than BUTTON4 "powexecaltslot 1" - it's the difference between just bang on the 246 character limit or 10 characters over it at 256:inspcombine Keen_Insight Focused_Rage$$inspcombine Dramatic_Improvement Focused_Rage$$inspcombine Take_A_Breather Focused_Rage$$inspcombine Good_Luck Focused_Rage$$inspcombine Rugged Focused_Rage$$powexecaltslot 1$$bindloadfilesilent binds/F2.txtI personally like to use the powexecname binds with my mouse side buttons but it was annoying me that I'd be converting insps constantly except for when I was activating my damage buffs, that little interruption becomes more and more noticable the longer you play with these binds. So by making the bind activate a slot in my secondary/tertiary trays instead I could still keep the button mapping I liked but also attach the convert script to them as well. Win-win.
-
1
-
-
Updated the first post and bind files to make a few changes:
- Changed the order of the commands on the 1-0 keys to avoid hitching when it tried to activate a power *THEN* fiddle with insps, it now runs the insp command first then the power queue.
- Using shorter syntax (feedback from AboveTheChemist and JAMMan)
- Enabled Small Inspiration Drops - then added those back in to the combine rotation and Numpad 1 binds.
- Disabled Team & Dual Inspiration Drops - removing the need for extra files to delete the resist, defense/resist and heal/end inspirations. These were essentially slowing down acquisition of useful insps anyway now that Small Insps are back on.
You'll find it far smoother and more consistently keeping up 600% damage cap on a Brute now (or other ATs caps).
-
9 hours ago, Shred Monkey said:
First of all fantastic guide. It gave me everything I needed in a clear, concise format. And the bind file method is quite powerful.
However, isn't this a bit of overkill? I just set up a bind to convert tier 1s mapped to 1, tier 2s to 2, and tier 3s to 3. Since those are in my primary attack chain, they get quite a bit of use, and it seems to be enough. I considered binding duplicates in 4,5, and 6... but after running a few missions, it seems that just the single bind for each tier is keeping up with the drops just fine.
Not really - my attack chain on my farmer is four powers most of the time, plus queuing incarnates from time to time, and I move about a lot to manage aggro caps. This way it doesn't really miss a beat on generating reds for me as I move about dynamically. I'd say it has *less* utility for someone who is just planning on AFK farming or isn't moving about as much since the loop wouldn't be running as much or at all.
You can definitely make something simpler that does just three powers for three tiers, but you'd be missing things like deleting inspirations that can't be combined (you can turn them ALL off uniformly but it just means you're getting less insps and disables their Red versions also) and it wouldn't be running those steps as often, moreso enflamed if you don't have Hasten perma yet - for example on farmers who are just slotting and gearing up still. -
On 5/31/2021 at 10:49 AM, godslayer said:
I don't suppose there is a way to change the font style in chat I am sending out to others.
For example, for a monster-themed character, use a horror ttf font style to change the text others read when I send it out.
No, the changes affect what you see in your client only, it looks the same as normal for everyone else. -
6 hours ago, SmalltalkJava said:
Looks like you have a typo in the Farm1.txt. you have this... It looks like you need to remove the \binds portion. (I think)
numpad1\binds
Additionally. do you have the tier 1 inspirations turned off? I noticed that it doesn't seem to be combining the basic "Lucks" and so forth
Good spotting - have just fixed. 😊
And yes, I have Wakies, Break-Frees and Small Insps disabled and just use medium to large plus team/dual. You could re-enable small insps but would probably have to add an extra file or two to the loop to include all the extra small insp names (copying the same format as above). It should work and could potentially just be set up to include all insps with none disabled. -
Here's a slightly more complicated example to demonstrate how you would add a third or fourth auto power in.
This one is from my Thugs/Time MM, it queues up Hasten, Chrono Shift and Farsight as three separate auto powers, in a constant rotation whenever I fly around, attack or use my heal/buff shortcuts. I like to use my mouse side-buttons for these and have the same basic layout across all my alts (button5 is actually the top side-button on my mouse and button4 the bottom, this will not be the same for everyone and will vary from mouse to mouse - if you're also using a Swiftpoint Z, this is for you) but wanted to include those actions as triggering my auto queue loops. I've also added in my Vengeance bind that tries to target a dead teammate and cast the power.
Note that my keybinds for movement include CTRL for down (flying) instead of the default X. I've also changed the way TAB targeting behaves as I don't like it's default behaviour, you might prefer this version but if not the target_enemy_near bit is technically all you need (and it doesn't need the underscores either).
To simplify what all the text in the code blocks below is doing - it's six steps that go like this - do whatever the keybind is supposed to do normally plus:
Step 1 - Filler step to ensure things don't get out of synch
Step 2 - Queue Hasten as an auto powerStep 3 - Filler step to ensure things don't get out of synch
Step 4 - Queue Chrono Shift as an auto power
Step 5 - Filler step to ensure things don't get out of synch
Step 6 - Queue Farsight as an auto power
At the end of each step it loads the next file in order, when it reaches Step 6 it loops back to Step 1.
The Vengeance bind is using the "+ $$- $$" prefix so that it behaves like a push-toggle - when I push the key combination down - it runs the command and moves to the next step. Then it does it a second time when I release the keys. This is just useful for speeding up the process of targeting a dead teammate and then activating the power in this example.
Thugs/Time MM Auto-Queue Loop (Hasten + Chrono Shift + Farsight):SpoilerFile 1 'HATime1.txt' - located in a '/binds' sub-folder of my Homecoming installation ('/settings/live/')
This is the important dummy/filler file I mentioned above between the two auto-queue files, File 3 is functionally identical to this but you change 'HATime2.txt' on the load command to 'HATime4.txt' to ensure it continues the sequence correctly.w "+forward$$bindloadfilesilent binds\HATime2.txt" a "+left$$bindloadfilesilent binds\HATime2.txt" s "+backward$$bindloadfilesilent binds\HATime2.txt" d "+right$$bindloadfilesilent binds\HATime2.txt" SPACE "+up$$bindloadfilesilent binds\HATime2.txt" CTRL "+down$$bindloadfilesilent binds\HATime2.txt" TAB "unselect$$powexec_unqueue$$target_enemy_near$$bindloadfilesilent binds\HATime2.txt" BUTTON4 "powexecname Temporal Mending$$bindloadfilesilent binds\HATime2.txt" BUTTON5 "powexecname Power Boost$$bindloadfilesilent binds\HATime2.txt" SHIFT+BUTTON5 "+ $$- $$targetcustomnear defeated friend notmypet$$powexecname Vengeance$$bindloadfilesilent /binds/HATime2.txt" LBUTTON "bindloadfilesilent binds\HATime2.txt" RBUTTON "+mouse_look$$bindloadfilesilent binds\HATime2.txt" 0 "powexecslot 10$$bindloadfilesilent binds\HATime2.txt" 1 "powexecslot 1$$bindloadfilesilent binds\HATime2.txt" 2 "powexecslot 2$$bindloadfilesilent binds\HATime2.txt" 3 "powexecslot 3$$bindloadfilesilent binds\HATime2.txt" 4 "powexecslot 4$$bindloadfilesilent binds\HATime2.txt" 5 "powexecslot 5$$bindloadfilesilent binds\HATime2.txt" 6 "powexecslot 6$$bindloadfilesilent binds\HATime2.txt" 7 "powexecslot 7$$bindloadfilesilent binds\HATime2.txt" 8 "powexecslot 8$$bindloadfilesilent binds\HATime2.txt" 9 "powexecslot 9$$bindloadfilesilent binds\HATime2.txt"
File 2 'HATime2.txt' - located in a '/binds' sub-folder of my Homecoming installation ('/settings/live/')
This one queues up Hasten.
w "+forward$$powexecauto hasten$$bindloadfilesilent binds\HATime3.txt" a "+left$$powexecauto hasten$$bindloadfilesilent binds\HATime3.txt" s "+backward$$powexecauto hasten$$bindloadfilesilent binds\HATime3.txt" d "+right$$powexecauto hasten$$bindloadfilesilent binds\HATime3.txt" SPACE "+up$$powexecauto hasten$$bindloadfilesilent binds\HATime3.txt" CTRL "+down$$powexecauto hasten$$bindloadfilesilent binds\HATime3.txt" TAB "unselect$$powexec_unqueue$$target_enemy_near$$powexecauto hasten$$bindloadfilesilent binds\HATime3.txt" BUTTON4 "powexecname Temporal Mending$$powexecauto hasten$$bindloadfilesilent binds\HATime3.txt" BUTTON5 "powexecname Power Boost$$powexecauto hasten$$bindloadfilesilent binds\HATime3.txt" SHIFT+BUTTON5 "+ $$- $$targetcustomnear defeated friend notmypet$$powexecname Vengeance$$powexecauto hasten$$bindloadfilesilent /binds/HATime3.txt" LBUTTON "powexecauto hasten$$bindloadfilesilent binds\HATime3.txt" RBUTTON "+mouse_look$$powexecauto hasten$$bindloadfilesilent binds\HATime3.txt" 0 "powexecslot 10$$powexecauto hasten$$bindloadfilesilent binds\HATime3.txt" 1 "powexecslot 1$$powexecauto hasten$$bindloadfilesilent binds\HATime3.txt" 2 "powexecslot 2$$powexecauto hasten$$bindloadfilesilent binds\HATime3.txt" 3 "powexecslot 3$$powexecauto hasten$$bindloadfilesilent binds\HATime3.txt" 4 "powexecslot 4$$powexecauto hasten$$bindloadfilesilent binds\HATime3.txt" 5 "powexecslot 5$$powexecauto hasten$$bindloadfilesilent binds\HATime3.txt" 6 "powexecslot 6$$powexecauto hasten$$bindloadfilesilent binds\HATime3.txt" 7 "powexecslot 7$$powexecauto hasten$$bindloadfilesilent binds\HATime3.txt" 8 "powexecslot 8$$powexecauto hasten$$bindloadfilesilent binds\HATime3.txt" 9 "powexecslot 9$$powexecauto hasten$$bindloadfilesilent binds\HATime3.txt"
File 3 'HATime3.txt' - located in a '/binds' sub-folder of my Homecoming installation ('/settings/live/')
This is essentially File 1 duplicated - but loading in the next number in sequence - you need these Dummy/Filler file between every auto power queuing step to ensure the loop doesn't break and it functions properly.
w "+forward$$bindloadfilesilent binds\HATime4.txt" a "+left$$bindloadfilesilent binds\HATime4.txt" s "+backward$$bindloadfilesilent binds\HATime4.txt" d "+right$$bindloadfilesilent binds\HATime4.txt" SPACE "+up$$bindloadfilesilent binds\HATime4.txt" CTRL "+down$$bindloadfilesilent binds\HATime4.txt" TAB "unselect$$powexec_unqueue$$target_enemy_near$$bindloadfilesilent binds\HATime4.txt" BUTTON4 "powexecname Temporal Mending$$bindloadfilesilent binds\HATime4.txt" BUTTON5 "powexecname Power Boost$$bindloadfilesilent binds\HATime4.txt" SHIFT+BUTTON5 "+ $$- $$targetcustomnear defeated friend notmypet$$powexecname Vengeance$$bindloadfilesilent /binds/HATime4.txt" LBUTTON "bindloadfilesilent binds\HATime4.txt" RBUTTON "+mouse_look$$bindloadfilesilent binds\HATime4.txt" 0 "powexecslot 10$$bindloadfilesilent binds\HATime4.txt" 1 "powexecslot 1$$bindloadfilesilent binds\HATime4.txt" 2 "powexecslot 2$$bindloadfilesilent binds\HATime4.txt" 3 "powexecslot 3$$bindloadfilesilent binds\HATime4.txt" 4 "powexecslot 4$$bindloadfilesilent binds\HATime4.txt" 5 "powexecslot 5$$bindloadfilesilent binds\HATime4.txt" 6 "powexecslot 6$$bindloadfilesilent binds\HATime4.txt" 7 "powexecslot 7$$bindloadfilesilent binds\HATime4.txt" 8 "powexecslot 8$$bindloadfilesilent binds\HATime4.txt" 9 "powexecslot 9$$bindloadfilesilent binds\HATime4.txt"
File 4 'HATime4.txt' - located in a '/binds' sub-folder of my Homecoming installation ('/settings/live/')
This one queues up Chrono Shift.
w "+forward$$powexecauto Chrono Shift$$bindloadfilesilent binds\HATime5.txt" a "+left$$powexecauto Chrono Shift$$bindloadfilesilent binds\HATime5.txt" s "+backward$$powexecauto Chrono Shift$$bindloadfilesilent binds\HATime5.txt" d "+right$$powexecauto Chrono Shift$$bindloadfilesilent binds\HATime5.txt" SPACE "+up$$powexecauto Chrono Shift$$bindloadfilesilent binds\HATime5.txt" CTRL "+down$$powexecauto Chrono Shift$$bindloadfilesilent binds\HATime5.txt" TAB "unselect$$powexec_unqueue$$target_enemy_near$$powexecauto Chrono Shift$$bindloadfilesilent binds\HATime5.txt" BUTTON4 "powexecname Temporal Mending$$powexecauto Chrono Shift$$bindloadfilesilent binds\HATime5.txt" BUTTON5 "powexecname Power Boost$$powexecauto Chrono Shift$$bindloadfilesilent binds\HATime5.txt" SHIFT+BUTTON5 "+ $$- $$targetcustomnear defeated friend notmypet$$powexecname Vengeance$$powexecauto Chrono Shift$$bindloadfilesilent /binds/HATime5.txt" LBUTTON "powexecauto Chrono Shift$$bindloadfilesilent binds\HATime5.txt" RBUTTON "+mouse_look$$powexecauto Chrono Shift$$bindloadfilesilent binds\HATime5.txt" 0 "powexecslot 10$$powexecauto Chrono Shift$$bindloadfilesilent binds\HATime5.txt" 1 "powexecslot 1$$powexecauto Chrono Shift$$bindloadfilesilent binds\HATime5.txt" 2 "powexecslot 2$$powexecauto Chrono Shift$$bindloadfilesilent binds\HATime5.txt" 3 "powexecslot 3$$powexecauto Chrono Shift$$bindloadfilesilent binds\HATime5.txt" 4 "powexecslot 4$$powexecauto Chrono Shift$$bindloadfilesilent binds\HATime5.txt" 5 "powexecslot 5$$powexecauto Chrono Shift$$bindloadfilesilent binds\HATime5.txt" 6 "powexecslot 6$$powexecauto Chrono Shift$$bindloadfilesilent binds\HATime5.txt" 7 "powexecslot 7$$powexecauto Chrono Shift$$bindloadfilesilent binds\HATime5.txt" 8 "powexecslot 8$$powexecauto Chrono Shift$$bindloadfilesilent binds\HATime5.txt" 9 "powexecslot 9$$powexecauto Chrono Shift$$bindloadfilesilent binds\HATime5.txt"
File 5 'HATime5.txt' - located in a '/binds' sub-folder of my Homecoming installation ('/settings/live/')
This is essentially File 1 duplicated - but loading in the next number in sequence - you need these Dummy/Filler file between every auto power queuing step to ensure the loop doesn't break and it functions properly.
w "+forward$$bindloadfilesilent binds\HATime6.txt" a "+left$$bindloadfilesilent binds\HATime6.txt" s "+backward$$bindloadfilesilent binds\HATime6.txt" d "+right$$bindloadfilesilent binds\HATime6.txt" SPACE "+up$$bindloadfilesilent binds\HATime6.txt" CTRL "+down$$bindloadfilesilent binds\HATime6.txt" TAB "unselect$$powexec_unqueue$$target_enemy_near$$bindloadfilesilent binds\HATime6.txt" BUTTON4 "powexecname Temporal Mending$$bindloadfilesilent binds\HATime6.txt" BUTTON5 "powexecname Power Boost$$bindloadfilesilent binds\HATime6.txt" SHIFT+BUTTON5 "+ $$- $$targetcustomnear defeated friend notmypet$$powexecname Vengeance$$bindloadfilesilent /binds/HATime6.txt" LBUTTON "bindloadfilesilent binds\HATime6.txt" RBUTTON "+mouse_look$$bindloadfilesilent binds\HATime6.txt" 0 "powexecslot 10$$bindloadfilesilent binds\HATime6.txt" 1 "powexecslot 1$$bindloadfilesilent binds\HATime6.txt" 2 "powexecslot 2$$bindloadfilesilent binds\HATime6.txt" 3 "powexecslot 3$$bindloadfilesilent binds\HATime6.txt" 4 "powexecslot 4$$bindloadfilesilent binds\HATime6.txt" 5 "powexecslot 5$$bindloadfilesilent binds\HATime6.txt" 6 "powexecslot 6$$bindloadfilesilent binds\HATime6.txt" 7 "powexecslot 7$$bindloadfilesilent binds\HATime6.txt" 8 "powexecslot 8$$bindloadfilesilent binds\HATime6.txt" 9 "powexecslot 9$$bindloadfilesilent binds\HATime6.txt"
File 6 'HATime6.txt' - located in a '/binds' sub-folder of my Homecoming installation ('/settings/live/')
This one queues up Farsight, then starts over at the first file, creating our loop.
w "+forward$$powexecauto Farsight$$bindloadfilesilent binds\HATime1.txt" a "+left$$powexecauto Farsight$$bindloadfilesilent binds\HATime1.txt" s "+backward$$powexecauto Farsight$$bindloadfilesilent binds\HATime1.txt" d "+right$$powexecauto Farsight$$bindloadfilesilent binds\HATime1.txt" SPACE "+up$$powexecauto Farsight$$bindloadfilesilent binds\HATime1.txt" CTRL "+down$$powexecauto Farsight$$bindloadfilesilent binds\HATime1.txt" TAB "unselect$$powexec_unqueue$$target_enemy_near$$powexecauto Farsight$$bindloadfilesilent binds\HATime1.txt" BUTTON4 "powexecname Temporal Mending$$powexecauto Farsight$$bindloadfilesilent binds\HATime1.txt" BUTTON5 "powexecname Power Boost$$powexecauto Farsight$$bindloadfilesilent binds\HATime1.txt" SHIFT+BUTTON5 "+ $$- $$targetcustomnear defeated friend notmypet$$powexecname Vengeance$$powexecauto Farsight$$bindloadfilesilent /binds/HATime1.txt" LBUTTON "powexecauto Farsight$$bindloadfilesilent binds\HATime1.txt" RBUTTON "+mouse_look$$powexecauto Farsight$$bindloadfilesilent binds\HATime1.txt" 0 "powexecslot 10$$powexecauto Farsight$$bindloadfilesilent binds\HATime1.txt" 1 "powexecslot 1$$powexecauto Farsight$$bindloadfilesilent binds\HATime1.txt" 2 "powexecslot 2$$powexecauto Farsight$$bindloadfilesilent binds\HATime1.txt" 3 "powexecslot 3$$powexecauto Farsight$$bindloadfilesilent binds\HATime1.txt" 4 "powexecslot 4$$powexecauto Farsight$$bindloadfilesilent binds\HATime1.txt" 5 "powexecslot 5$$powexecauto Farsight$$bindloadfilesilent binds\HATime1.txt" 6 "powexecslot 6$$powexecauto Farsight$$bindloadfilesilent binds\HATime1.txt" 7 "powexecslot 7$$powexecauto Farsight$$bindloadfilesilent binds\HATime1.txt" 8 "powexecslot 8$$powexecauto Farsight$$bindloadfilesilent binds\HATime1.txt" 9 "powexecslot 9$$powexecauto Farsight$$bindloadfilesilent binds\HATime1.txt" -
1 hour ago, Avernal said:
Will have to give it a go then - if it behaves that's good as it's another character shorter on the total string, makes life a bit easier for some of the longer ones hitting the limit.
OK, so not only did it work without the dot, but you can remove the slash entirely too (binds/ instead of ./binds/) - shaving off an extra two characters. 😊
This is awesome because in some of my bind loops I was only short of a lousy couple of characters that meant having to split the bind in to an extra file. Have just set up a Hasten/Chrono Shift/Farsight auto power loop on my Thugs/Time MM to test the above and am pretty chuffed it worked. Will update the guides to remove those extra unneeded characters. 😀-
1
-
-
16 hours ago, AboveTheChemist said:
I've done a number of various binds, most of which are stored in sub-folders, and have never needed the ./ notation (or to specify the full path) for them to work properly under Windows 10. I had to adjust the relative path slightly when I migrated from Tequila to the HC launcher, but other than that just using bare relative paths has always worked fine for me.
Will have to give it a go then - if it behaves that's good as it's another character shorter on the total string, makes life a bit easier for some of the longer ones hitting the limit.
Time to give scrappers super strength
in Scrapper
Posted
You know what I've found a really refreshing and unique mechanic that might work well for a retuned Super Strength? The way Unrelenting from the Prescence Pool removes the crash of Unleash Potential from Force of Will, yet both powers add some nice boosts to a character. I took these on one of my Stalkers randomly as I'd never touched those pools on any character before and whilst it was an unorthodox approach I ended up absolutely loving it and how they synergised together.
Having Rage's crash mitigated by making it unstackable but able to refresh would be one good way to reward people investing in the recharge to achieve it, another way might be adding a second utility power to SS that smoothed out some of its shortcomings by itself, but could also be used in tandem with Rage to remove the crash.