Close
Showing results 1 to 10 of 15

Hybrid View

  1. #1

    Default

    I think he was saying, if you could do it in HKN, to win those people over, you would need to be able to do it in your new program. Like, round robin (toggle). If your new program can't do round-robin, it might not win people from HKN, since you can do it there. If you can't do white list or blacklist (I press "2" and only computer #2 repsonds to it or don't broadcast anything other than 1-0 and F1-F12), then it might be limiting. If you can't talk to multiple computers, again, probably won't win new people. I wouldn't worry about having to do everything that everything else can do. You can expand later, just get something that works first.
    If you want to do something no eles has done, Mac and PC use hasn't been done. Mouse broadcasting has been done, but it is mostly a WOW thing (camera position and player facing) more than a broadcasting thing (my opinion).

  2. #2

    Default

    Quote Originally Posted by ElectronDF View Post
    I think he was saying, if you could do it in HKN, to win those people over, you would need to be able to do it in your new program.
    Yeah, I think I took the discussion too literally. But your interpretation -- that the new program should duplicate HotkeyNet's features -- wouldn't be practical either because it would take too long, and I don't think it could be done with a GUI interface. HotkeyNet has too many features, and I don't think it's possible to design a GUI that would allow the user to define all the behaviors that can be defined with the script language.

    Some random examples of HotkeyNet's features:

    -- HotkeyNet lets people paint panels of buttons on the screen using their own artwork, and they can assign the buttons to execute pieces of scripts conditionally based on many different conditions.

    -- HotkeyNet lets the user kill mutexes to which external processes hold open handles;

    -- HotkeyNet allows people to use the chat line in a game as an input field for commands that are defined in HotkeyNet's scripts;

    -- etc.

    There are dozens of non-trivial features like that in HotkeyNet. Each of them would take a substantial amount of time to reimplement, test, and document.

    If I were writing a multiboxing program from scratch, I would forget HotkeyNet and implement what I described above (the feature set of old Mojo). Such a program can grow in any desired direction, so there are no limits. But that's what I would start with.
    Last edited by Freddie : 07-06-2011 at 05:49 AM
    �Author of HotkeyNet and Mojo

Posting Rules

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •