
Originally Posted by
'Vyndree',index.php?page=Thread&postID=138883#post 138883
Sorry, Lax. I just got back from my lunch with my workgroup.
You want me to read the source code of both ClickBoxer and InnerSpace (since they both work together) in order to form an opinion? I apologize if I made mistakes in my interpretation of the locked thread, but I think everyone will agree with me that the original ClickBoxer thread is not exactly easy to read. You'll notice that I also quoted your full statement regarding the ToU section along with my synopsis, so if I have misinterpreted you, there is still the full quoted text to be read and reinterpreted above.
As for my post in the CS forum, I've updated as I go and I think it would be awesome if you'd like to fix any mistakes I've made. If you don't have a world of warcraft account that can post on the official US forums, I'd be happy to directly copy/paste any statement you'd like to make if you just want to post it in this thread. I started the thread purely to end a debate of opinions and so we can put the disagreements to rest -- whether or not my opinion is right or wrong is irrelevant and I've tried to keep any bias out of it.
Like I said in my original post, any expert in ClickBoxer is welcome to add their thoughts and/or definitions to the thread, and to correct my limited knowledge as well. As the developer/owner you'd be the ideal person to drive the thread, since it's in the best interest of your product to get a solid confirmation on whether or not your interfacing and input methods are kosher with the game rules.
My interests are solely for the account safety of the community, so my knowledge of the product, development, and design is limited. You can't argue, though, that it's new ground to implement a "click replicator" and that it largely hasn't been proven or disproven by the GMs. So it's my interest to get that solidarity -- whether it's yes or no.
I have World of Warcraft accounts that CAN post, however I do not feel that my posting on the WoW forums would add to the value of the thread. Just as we see here on dual-boxing.com, there would be people responding who will voice their opinion of me, and the conversation would degrade into uselessness instead of an objective look at the matters at hand. I would like to post a thread like that, but there are reasons that I simply cannot describe to you at this time, so I'm sorry for that at the moment. I agree that a response from Blizzard would settle the score, and I do understand your motive in posting the thread, and I do not disagree with that.
The problem is that as it stands, the thread began with a misinterpretation of the video I made and audible brought up here. The portion you see me completing the quests, I first switched to each window and opened the quest window -- I'm told that an in-game macro can be used, probably in conjunction with assist, to do that quicker, but that's beside the point -- and then hit my repeater toggle (I bound it to the MR button on my G15). Moving the mouse on the main screen and then clicking at the desired position, caused the same actions to be replicated on the background windows -- the way this works is no different than replicating key presses, it's just done with mouse positioning and clicking instead. Another press of my repeater toggle key, and replication stops.
The clicks on the ClickBoxer window press keys, for assist, melee attack, stomp, and so on. The same thing is also done in portions of the video with binds. In this case, I was binding G15 through G18 for e.g. my round robin stomp, follow, assist, and lightning bolt. The ClickBoxer window as Suvega described on the thread is overlayed on the game and skinned to look similar to WoW, and it can be interacted with (similar to how you might interact with X-Fire, for people who use that).
I'm not suggesting that you should or could read the source code to Inner Space. What I am suggesting is that the source code to ClickBoxer reveals the essentials to how it works. The ClickBoxer layout used in the video is shown here: http://www.lavishsoft.com/wiki/index...Boxer#Layout_2 -- there is nothing else to ClickBoxer, that's all the code to it. For example:
Code:
<button name='atk 2'>
<X>250</X>
<Y>2</Y>
<Width>48</Width>
<Height>16</Height>
<Text>atk 2</Text>
<OnLeftClick>
<![CDATA[
relay "all other" press 2
]]>
</OnLeftClick>
</button>
This defines a button on the interface, and when clicked it will perform: relay "all other" press 2
I think what that will do is pretty clear without explanation, but if not, it will relay to all of the other windows, to press 2.
Same for Repeater, which is also open source. http://www.lavishsoft.com/wiki/index.php/IS:Repeater -- the download contains only an .iss file that can be opened with any text editor. The code is not incredibly complex, it contains comments, and should be relatively easy for people to follow even without programming experience. The nuts and bolts of it is simply an event that Inner Space fires when you press a button, including mouse buttons. When the event fires that you pressed or released a button, the same relay "all other" press <key> is used (or -release). Mouse clicks have a slightly different syntax, but is still essentially the same. The difference for mouse is that the current X,Y position of the cursor is also passed along. Frankly, I'm amazed that mouse replication is a new concept, and as it is still 1 key to 1 action, I would be surprised if it is disallowed.
And while your questions are fine, I suspect that "making dynamic decisions" would not be allowed, and that "reading WoW's memory" with respect to game data as opposed to its interaction with Windows is not allowed (note that running World of Warcraft in Cedega or Wine on Linux is allowed, and does not read anything different than Inner Space).
The problem I do have is that people reading that thread now have the false impression that ClickBoxer does these things because you said it did. I just feel it was a slight bit irresponsible to assume that there was any dynamic decision making based on WoW memory going on, and to perpetuate that on the WoW forums without being sure of it. But like I said, I believe that you were well-intentioned by attempting to get a response, it's just that your post kind of begs for a negative response from a blue or green poster who might respond based on what you said, rather than the substance of the application.
Connect With Us