Jump to content
Hotmail and Outlook are blocking most of our emails at the moment. Please use an alternative provider when registering if possible until the issue is resolved.

Recommended Posts

Posted

This is an incredibly small and nerdy thing, and since I'm not familiar with the underlying code of the parser for CoH, it may be impossible. However: 

When attempting to do binds that combine and then use inspirations, having to use the full names for them makes things very difficult to fit inside the 255 character limit.

For example, one step in my "combine and use an accuracy inspiration" bind wants to be as follows: 

F1 "inspcombine focused_rage keen_insight$$inspcombine good_luck keen_insight$$inspcombine take_a_breather keen_insight$$inspcombine dramatic_improvement keen_insight$$inspexecname keen insight$$inspcombine rugged keen_insight$$bindloadfilesilent C:\coh\default\cbinds\1-1.txt"

 

This is 280 characters, meaning that even if I play around with path/filename for the bindfile, I'm SOL. 

 

However, if there was also an abbreviation that could be used in the bind language to refer to inspirations, I would be able to do something like this, which is 190 characters:

F1 "inspcombine dam2 acc2$$inspcombine def2 acc2$$inspcombine end2 acc2$$inspcombine heal2 acc2$$inspcombine res2 acc2$$inspexecname acc2$$bindloadfilesilent C:\coh\default\cbinds\1-1.txt"

 

Just for clarity, the naming I'm suggesting is 'inspiration type' + 'level', so insight would be acc1, keen insight would be acc2, uncanny insight would be acc3, and so on.  

  • Like 1

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...