Close
Page 3 of 3 FirstFirst 1 2 3
Showing results 21 to 24 of 24
  1. #21

    Default

    Quote Originally Posted by Barelan View Post
    We havn't taken any casting mechanics out of the game.
    You have a timer that says "even if I press this button, do not cast this spell until X time has passed". That is taking casting out of the game's hands. You point to it and say it's cooldown monitoring, I point to it and say "Fantastic, now I can create a macro to automatically perfectly time rolling HoTs without having to worry about overwriting too soon, missing one and letting them drop or spamming myself out of mana, so I can throw it on my all my keys and as long as I'm facerolling somewhere between my DPS and tank, I never need to worry about actively healing."

    Can I make a rolling HoT macro in game? Sure can, but can the one I make in game determine when, in seconds, to move on to the next spell? No, it can't. I can throw as many commas in there as I want but they can't tell time. Some fights I may hit 10 commas a second, some I may only hit 2, some I may push out 15. The complications that arise with that is the price I pay for using castsequence to minimize the number of buttons I have to deal with. With your setup, 10 seconds is always 10 seconds, nevermind latency, nevermind what else is going on in the game.
    Blog : Herding Khats
    Team : Kina - Çroaker - Messkit - Lìfetaker - Wìdowmaker
    Newbie Guides : Multiboxing Vol. 1 - Multiboxing Vol. 2 - HotKeyNet - Jamba
    The Almighty Lax made a liar out of me, apparently I DO get prizes for it.
    *Commences Wielding the Banhammer like there's piñatas up in here and I'm Lady Thor*

    _ Forum search letting you down? Use the custom Google search _

  2. #22

    Default Sounds like we should pass on this one

    I think that, given the reaction, we should probably not implement this feature at this point.

    To summarize:

    Blizzard will not comment on a given application. They take the view that functionality can change (both in the app and in their software) so this prevents them from commenting.

    Their stance is that as long as one key causes no more than one action, it is OK. Automation seems to be defined as when an application takes an action with no user input.

    According to the above, what we propose would be "legal" but Blizzard also say that it is up to the individual to decide on whether the application they use is acceptable. This is our issue.

    So far we have been extra careful to ensure that our application cannot be used to break TOS. GCP was build from the start to be a legal multi-boxing program. We could have bolted our management functions on to existing platforms, but that would have removed our ability to ensure that this remains true. In that sense we have spent time and money on ensuring this compliance.

    Everything that we do in GCP can be achieved in other products - GCP just makes it easy.

    Based on this thread, it would seem that adding this functionality would enter a grey area, and we should probably avoid that. We feel that preserving our exclusive "can't break the TOS" feature is probably more important, even if we lose out on some potentially cool functionality.

    You people have helped clarify this for me, and I'd like to thank all the people who have so far responded to this.

    Once again, thanks for the feedback
    Phil@GameCommanderPro.com
    www.GameCommanderPro.com
    Aarelan (Paladin), Barelan(Hunter), Carelan(warlock), Darelan(priest),Earelan(mage) - My "nearly" level 30 blood elf mixed team on Stormrage - current "mains"
    Akow, Bkow, CKow, Dkow - My lvl 70 tauren druids on Stormrage (I haven't had time for WOTLK as I've been working on the software)

  3. #23

    Default

    Well he is asking here to see what the reaction is of people who are in the know, before going to Blizzard for the final say. I often will bounce ideas off of the people here before doing things, thats what forums are for.

    Its a lot grey as its the timeing part that is questionable. You are not allowed to introduce timing into macros. Logic that goes. If its time A cast A if its time B then cast B is little different then putting in a fixed delay.

    This is illgal:

    /cast 1
    /delay 10
    /cast 2

    Thus this is also illegal:

    /cast 1
    if delay less then or equal 9 cast 1 again else cast 2


    .....

    28 BoXXoR RoXXoR Website
    28 Box SOLO Nalak 4m26s! Ilevel 522! GM 970 Member Guild! Multiboxing Since Mid 2001!

  4. #24
    Member
    Join Date
    Sep 2008
    Location
    Calgary, AB and Vancouver, BC
    Posts
    7638
    Blog Entries
    2

    Default

    If you'd like to implement this type of feature, I'd really consider using a /Click Castsequence builder within your application.

    Have it time how quickly you spam your key. Based on your spam speed, have the "wizard" place the correct number of comma's.

    Choose spell 1, spell 2, spell 3 etc. You could go with a graph for each individual sequence. So people can see the cast time for a given spell is 1.75 seconds. The spell duration is as long as the red (pick a color) bar goes.

    Then have the ability to put in multiple sequences, and prioritize which is more important.

    That way, you're offering something that makes Click Castsequences much easier. At the same time, you're not doing anything at all, which could not be accomplished within the basic wow ui, without any macro's at all. Cannot really get into too much trouble, limiting yourself to what can already be accomplished. But, offering it in a way that's a ton easier to create the macro's - Just pick the spells you want and have the wizard build the macro's for you.

Posting Rules

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