Jump to content
The Beta Account Center is temporarily unavailable ×
Double XP is active on all shards

kenlon

Members
 View Profile  See their activity

  • Posts

    264

  • Joined

  • Last visited

Reputation

178 Excellent

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. kenlon
    Yeah, my assumption was it would be separate, I was just using the name. Which I probably should have clarified. Maybe make "Edit defaults" one of the available buttons at startup and go from there?
  2. kenlon
    Yeah, doesn't matter what you call the "default". I named my default profile to "base binds" which seemed appropriate to me, since all the other profiles are build on them.
  3. kenlon
    I ended up binding ESC to "/wdw_load" (after saving the window layout I want to use to Homecoming/settings/live/wdw.txt with /wdw_save) since I use the same layout for all characters. I used a custom bind, since your wdw save/load option uses wdwsavefile/wdwloadfile and I don't need separate window layouts at the moment. Just FYI. Another thing, the "default profile" being just a regular profile that you then use when creating new profiles has some drawbacks. If I add a new bind (custom or otherwise) to my default, or change one of my custom binds, I have to either recreate all my character-specific profiles or make the change to all of them myself. What I would really want, as an end user, is the following: The default profile is independent from manually created profiles, and when opening a profile for editing, the default is used as a base and then overwritten with any profile-specific changes that have been made. I can set all the movement type binds in the default, and then if I load a build/profile that has the associated powers in them, they are added to the binds written out by that profile. If I revise a shared bind, custom or not, all I have to do is open all the profiles, write out binds, save profile. Which is a much faster process than either recreating or manually saving and importing multiple custom binds, since you can't do a set at once. From looking over the code, that would be a bit of a pain to implement (at the very least), but I figured I'd at least mention it, given that you're already mucking around in the "which powers does this profile actually have" bits of Bindcontrol. The simplest way to do it, seems to me (though it may not be the best), would be to change up the file format so that each bind entry has an additional field that marks whether the bind is profile-specific or not. If the bind is from the default, not profile specific, then when opening the profile BindControl will update those binds to whatever the default has been changed to.
  4. kenlon
    I was considering binding ESC to the close all windows option, so I was curious about binding it.
  5. kenlon
    Saw you had a v0.32-test4 tagged, so I checked it out. The Incarnate powers are bindable now, but I ran into a small issue. PowerBinder doesn't have /powexec_location so I had to do it as a custom command. (I bound my Lore pet with "/powexec_location me" so they'd just drop at my feet in one click.) Edit: Additionally, is there a particular reason that ESC is unbindable, or is it just because hitting ESC to close windows is the default assumption of BindControl?
  6. kenlon
    Would also be handy for things like powexec binds too, would make it simpler when setting up self-buff binds.
  7. kenlon
    Found an issue with test3: If you try to bind Incarnate powers, it doesn't quite work right. Example: the preview bind string for Ageless Core Epiphany is "powexectoggleon <class 'type'> Core Epiphany".
  8. kenlon
    I really wish I knew what about your setup keeps getting the exe flagged by Defender. It's heuristic, since it's always a 'ml' detection. How are you packaging this? EDIT: I did just update the defs in the hopes that a new set would have clue, but no luck.
  9. kenlon
    Nope, this doesn't work, sadly.
  10. kenlon
    Found a bug with v0.32 - if you do "Import saved build" it doesn't bring in any of your default profile settings. (And I did a "save as default" with my basic profile in 0.32 in case anything had changed with how it was saved in the ini file). Doing "new profile" inherits settings just fine.
  11. kenlon
    What could possibly go wrong, I ask you? 😄 So far, it does seem to work smoothly enough.
  12. kenlon
    Honestly, you make a good point. Just having a checkbox for "Clear any existing team selection binds" would probably split the difference nicely. As a first pass, that works.
  13. kenlon
    Another thing, since I'm poking around with bits of BindControl I hadn't used before: The 'import saved build' option is neat, but simply possessing a travel pool really shouldn't automatically assume that you have the travel power (since just about anyone who has any sort of serious build will have Hasten, but probably not Super Speed). Only actually setting a default keybind if you actually have taken the power seems like a reasonable way to do it to me.
  14. kenlon
    As I am now awake from my nap, I'll give it a try. It looks good so far - instant saving/loading, no issue saving the basic binds profile as default, and my combine binds all work in game. Did notice one thing: when I turn on the Combined Team/Pet Select option and set the keybinds, it doesn't unset the default "Select Teammate" binds if you already have them. In my case, I use Shift+1/2/3/4 for the first four, and Shift+q/w/e/r for five through eight. If I look in the in-game keybinds menu, Select Teammate 5 through 8 are still bound to Shift+5/6/7/8 (which are the defaults for the classic keybind profile). If I'm setting something through BindControl, it should probably unset the vanilla binds for the same thing to avoid confusion.
  15. kenlon
    Okay, I am deeply amused: I can't save my finished Basic Binds profile as default. (I will admit to being largely amused because in my day job I'm usually the one asking, "What the hell was that user thinking?) 😄 Basic Binds.bcp
×
×
  • Create New...