Stev

botter!!! Lies! Bots don't exist on RuneScape remember? A Jagex mod once told me that.

nice lie jagex. anyway, that's to bad, I didn't use them personally, but I can see the adventage, and it seems more of a convenience then something that gives you an upper hand. Sorry Wicked. :mellow: Yeah, go after the people giving themselves a quick button for quick prayer at bosses, or taking some of the grinding out of skilling, or switching weapons at TDs, or quick teleporting with equipped items. People who are actually sitting at their computer. Yeah, I can see the HUGE advantage we're gaining. Maybe if this was used in PvP, then I can see it as being wrong as most people can't switch as quickly, but seriously Jagex? I would love to sit down and have a conversation with a JMod (Not from TIF), without them staying for 3 minutes and saying, "Gotta go get back to work!" I have spoken with Mod Kathy in the past when she came to a 99 party of mine. I mentioned the TD gear switch script in very high detail and was told it was OK. Jagex, I've never lashed out before and have always really kept my cool. You can see that my posts on this topic have been calm, collective, and simply debating my side. But seriously, you are full of [cabbage]. You're claiming that you'll ban the users of scripts that simply save 5-10 milliseconds of time. Often time, they don't save any time, yet simply make it easier/more enjoyable. Users who are actually sitting at our computers and have to deal with the bull-[cabbage] of real bots while getting killcount at Armadyl, for example. Why I try to write scripts and functions to help out for a game I don't even play is beyond me. Especially when Jagex themselves couldn't give a [cabbage] about the game. I try to make their game more enjoyable and easier for people (Which saves them a maximum of a few milliseconds, if any at all), and they threaten to ban. Meh, the way RuneScape's going, in a few years or so we won't be seeing RuneScape around anyways.

Sry, I just couldn't help but LOL at this quote. Go ban some real bots. Maybe the thousands at Avansies (All with 99 Range/HP/Defence/etc)? Maybe even the thousands at Tzhaar? No? How about the [cabbage] load at the Fishing Guild? Ah, still nothin'. Do the hundreds at blue/green dragons tickle your fancy? Hm, didn't think so. Maybe check out Sorcerers Garden? I hear there's also thousands there. Again, no? Do the people making your game less boring/more fun/customizable work for you? Yes? great. (As if you can even tell) Lmfao! They forgot the: I'm glad to see they looked through all but what?... 20 lines of the code at most? But, what ever, Jagex. Thanks for your time. Love, Wicked - il Foreva li

For something like this, you may be more interested in [Function] Box(). Although, it'd be better off using GDI+, but ya got a ways until scripting with that. :P.

Was going to do it in C++, or even Java, but TBH AHK and GDI+ was the far easiest and required far less work. If I have to make all the changes in the "To-Do", then I'll be using just C++.

I need a bit more information then this. For example: What client are you using? It should work in all browsers, the Jagex client, and SwiftKit. What version of windows are you running? It requires at least Windows 98, since versions before that do not have GDI+. Do you see the key icon in the bottom right in your tray menu? Can Keying[dot]exe be seen in your task manager processes? If so, what's it's memory usage (Should be 3-6MB if it's running properly)? Any other information that you could provide may help. Also, apparently some users running Windows 7 are still having transparency issues with the following keys: green wedge, orange corner and crescent, silver rectangle and yellow crescent. The backgrounds are turning up black. I'm going to unpack Resource.dll, edit those keys files, re-save them and re-pack the Resource.dll.

Updated: Unpack Keys.Zip. Must read: If you've downloaded or used the previous one, you must go to My Documents and delete the Keying folder. The old one must not be running while, or you will be unable to delete this directory. AVG seems to have a problem with Unpack Keys. It is most likely due to one of the updates below marked with an *. Simply add it to your trusted applications list if this is a problem. The VirusTotal scan results for Unpack Keys can be found here. (1/43). The VirusTotal scan results for Keying can be found here. (0/37). To show the GDI+ window, hold left CTRL. To select colors, grids, or shapes, left click. To set home teleport, middle click on a grid. To clear a grid of keys, simply right click it. If you are worried about Unpack Keys, the source code is below: [spoiler=Unpack Keys - Source Code] #NoTrayIcon Gui, 1: -Caption +Border +AlwaysOnTop Gui, 1: Margin, 5, 5 Gui, 1: Add, Progress, w200 h15 vS HWNDS +0x8 -Smooth Gui, 1: Show,, Unpacking Files... PostMessage, 0x40a, 1, 0,, % "ahk_id " S IfNotExist, % A_MyDocuments "\Keying" FileCreateDir, % A_MyDocuments "\Keying" IfNotExist, % A_MyDocuments "\Keying\Resource" FileCreateDir, % A_MyDocuments "\Keying\Resource" FileInstall, C:\Keying\Resource\Resource.dll, %A_MyDocuments%\Keying\Resource\Resource.dll FileInstall, C:\Keying\Resource\Keying16x16.ico, %A_MyDocuments%\Keying\Resource\Keying16x16.ico FileInstall, C:\Keying\Keying[dot]exe, %A_MyDocuments%\Keying\Keying[dot]exe FileCreateShortcut, %A_MyDocuments%\Keying\Keying[dot]exe, %A_Desktop%\Keying.lnk, %A_MyDocuments%\Keying Run, %A_MyDocuments%\Keying\Keying[dot]exe ExitApp If you are still worried, and would rather not use Unpack Keys, or if AVG won't let you, you can skip the Unpack Keys by creating a folder in My Documents called Keying. You can then extract this ZIP file to that location (My Documents\Keying). As you can see from the source code of Unpack Keys, that's all it does. :P. A screenshot of the new layout: [spoiler=Screenshot] Updates: Home teleport option! Changed the layout to be, what I thought to be, a tad easier. Rather then unpacking and having it store/use 64 key images, all the images are packed into a Resource.dll. This means: faster, no transparency issues/corrupt files. * All-in-all, it should run smoother and require less memory usage. Freezing issues should be fixed. I believe it was a problem with the GDI+ trying to create the PBITMAP from the key image file. Now that it used Resource.dll, this should no longer be an issue! * - See above in the Must Read list. The contents of Resource.dll are listed below and can be verified using various tools such as Resource Hacker: [spoiler=Resource.dll] To-Do: Add the option to remap keys, as some don't have middle mouse buttons. Add the option to capture/display the last captured dungeon map. Possibly add the ability for other members in the DG to edit the map. This will require a secure method of PC communication, which will take time. Add an auto-update feature. Merge with the skill script to add/display rooms with skill doors or resources or altars. Thought/comments/questions/concerns?

What'd I miss on April 15th? ...Or did I hear about it and just not put the correct date to it? >.< If it's not permissible to post it, then please don't bother. :).

Will do. As Grimy said, that'd be a real pain in the ass to code, but not entirely out of the question. I'd have to look at which ways to make the PCs communicate with each other, etc. It's a great idea, but will take some time to implement. I've also been thinking about positioning it directly over the map to make it easier to tell which square is which. Also, the quick printscreen idea where you can quickly grab/display a screeny of the map would be very easy... I've already got the screenshot functions written to screeny certain areas of the RuneScape applet.

Ah... A valid point. Sry, I will look into that.

Your welcome! Pitac83, I will look into it. I have a machine with Vista and will see if I can reproduce the problems on it. Can you do me a favor? I tested it with SwiftKit and it still worked just the same, but can you try unning RuneScape in a browser/the Jagex client? What happens then? The idea of home teleport will be added. I woke up in severe pain, so I won't be coding right away, but as soon as I can, I'll add it. Thai_ton, I have a dungeoneering script that is for just what you ask. It was the same general grid layout as the Keying script, but no keys/items along the bottom. Clicking in a square more then once would cycle through the skill icons alphabetically for that square. Right clicking would make it cycle backwards... If I am making any sense. I've since deleted that script, but I did send it to Cheeesy and several others first, maybe I can get it off of one of them. If there is interest for this as well, I can/will write an unpacker and update/optimize the script itself. It had a very small memory leak (wasn't removing the previous images/brushes/pens from memory, so over time the memory usage for the script grew pretty big) but it was very small and therefore I didn't worry about it (It would have to be running for days straight to matter). Thanks for all the feedback! Is there any interest in the skill door one? If so, I can merge the keying one with it... Say left Ctrl will open the keys on the left, right Ctrl will open the skills on the right?

Not sure what you mean by deletion, but middle clicking a square removes the keys in it.

I'm being told that some of the key images are coming out with a black background, while others are transparent. Is anyone else having this problem?

"my scripts can be legal 1:1, but not as they are currently" Again boils down to the user. If they prefer, they can use the Move functions instead of the Click functions. And if you look, for ever Click function on that thread, there is a move one to do the equivalent as 1:1.

But 1:1 is no different from 2:2 or 3:3 or 4:4. etc. Having x amount of inputs result in x amount of actions is the same whether it's 1, 2, 3, 4, 5 or more. And as pointed out, when the functions are used for 1:1, they are faster and more efficient anyways, so why should it bother Jagex if someone choses to take a slower/less efficient route? I thought this whole thing was about someone having an advantage over the rest of the players. Someone using them to be 2:2, 3:3, etc, is actually giving themselves a disadvantage compared to the speed of 1:1. Although it's easier, it's still a disadvantage.

Aha! So it begins! Full-screen support should be relatively easy to add. Just give me some time... I've only been coding when the pain in my knee isn't too unbearable.

Some are faster 1:1, some are faster 2:2. So do we pick and chose so that they must be the slower or the 2? Also, most of my functions do exactly as that one does. Simply moves to a location and clicks. Therefore, most are faster as 1:1 and not 2:2. Look at click summoning, click inventory item, click prayer, click spell... All the same. A move and a click. All, with the setup above, would be in-fact faster as 1:1. Therefore the argument of the 2:2s being quicker, therefore should not be allowed, is invalid. Is a few milliseconds really worth that hassle of TIF trying to disallow TEF links from being posted. Are those few milliseconds worth the hassle of arguing back and forth about Jagex e-mails and [cabbage]? Especially since, as you've seen, when my functions are used 1:1 they are, in fact, faster!

I'm not sure what you mean by "becomes unresponsive". Does releasing left Ctrl make the GDI+ window disappear again or can you simply not click any more boxes? What version of Windows are you running?

Say I did... ::q:: RS_Click_Quick_Prayer() ;~ Pressing q, then pressing space, will click quick prayer. ...and... q:: RS_Move_Quick_Prayer() ;~ Pressing q moves the mouse to the quick prayer. You must then click. I can press q-space just as fast as I can press q and click. In fact, I could probably press q then click much faster then I could press q-space. Therefore, your 1:1 is much faster then the 2:2, the one you are arguing is bad.

::q:: RS_Click_Quick_Prayer() Return There's an example. For that to click your quick prayer, you would have to press q, release the key, and then press space/enter/esc/etc. 2 inputs. Then the function is still running when you click one key, not when you click two, that's the problem. @ginger, yes I've edited it. What do you mean by the functions is still running? Also, the second button must be pushed for this to work. And I'm not talking both pressed at once, such as ^F1. You must press q, release it, and press space. Then the function doesn't run when you press Q, it runs when you press space, and it all runs when you press space (one input). The only way this could be legal is if you could somehow run half the function when you press Q, and the other half when you press space. Then you are getting into my 1:1, 2:2, 3:3 argument. It will not run without the Q and the space being pressed. It will not run by simply pressing Q or by simply pressing space. Both actions are needed. And I put a script up, my first post this morning, which did the first half for the first input, then the second half with the second input; My RS_Move_... functions. But, what is the big difference between pressing 2 buttons and then 2 actions being done, compared to pressing the first button, it does the first half, then pressing the second button and it does the other half. They still require 2 actions for the exact same outcome.

::q:: RS_Click_Quick_Prayer() Return There's an example. For that to click your quick prayer, you would have to press q, release the key, and then press space/enter/esc/etc. 2 inputs. Then the function is still running when you click one key, not when you click two, that's the problem. @ginger, yes I've edited it. What do you mean by the functions is still running? Also, the second button must be pushed for this to work. And I'm not talking both pressed at once, such as ^F1. You must press q, release it, and press space.

The most the script does, and there are tools and software to monitor this if you don't believe me and you'd like to check, is: Creates a directory in My Documents called Keying. Extracts the GIF key images, which were actually grabbed from Tip.It (Try going to 64 pages, and saving 64 images -.-) Extracts and creates a shortcut for the Keying script. :).

Y_Guy, don't look at them as ^F1 being one input. Two actions are being required (You have to press two keys). Two actions are being generated. ::q:: RS_Click_Quick_Prayer() Return There's an example. For that to click your quick prayer, you would have to press q, release the key, and then press space/enter/esc/etc. 2 inputs. Again, that is up to them. I simply provide the building blocks and foundation for them to build upon.

As I am friends with many people in DGS, I was asked to write a script/program to help those learning to key and for those who may have a hard time keeping track of keys in a dungeon; And so I did. This had been done in a webpage, found here, but I didn't like the design/layout/click and drag, so I created an application which can be seen in a screenshot below. [spoiler=Screenshot] I have uploaded the script seen above in an extractor. For those who are unsure about downloading such files, I've uploaded the file to VirusTotal which scans it with 43 of the most well-known anti-viruses. The results were: File name: Unpack Keys[dot]exe Submission date: 2011-05-31 11:46:14 (UTC) Current status: finished Result: 0/ 43 (0.0%) As you can see, not even a warning. A link to the scan can be found here: http://www.virustotal.com/file-scan/report.html?id=ae5037395115842c09963cbbb0de299199f6e84444eac0a2641ab9d7517a5e01-1306842374 A link to the installer can be found here. How to use: Unpack the files - this will create a shortcut on your desktop and run the Keying script. With the RuneScape window active, holding left Ctrl will show the GDI+ window. Select a key and a color and place them in a square by clicking it. More then one key can be added to a square! To clear a square, click it with your middle mouse button. To reload the program, right click it's tray icon and select "Reload". For those who are still unsure, the source code can be provided. This was written simply to help out my friends in DGS and those willing to learn to key. I did not spend much time making it perfect, but if I see there's enough interest for it, I will send more time on it. It does not interact at all with the RuneScape applet; It simply creates an interactive GDI+ window which is "stickied" to the top left corner. As I don't dungeoneer, any criticism is appreciated. What should I add/remove? No one is forcing you to download the above tool, but as RuneScape is designed for and aimed toward adults (Or so they claim), I assume you can make your own decision. Thanks, Stev.

My scripts are not functioning. If you simply copied and pasted any of the functions in that first post and executed it, nothing would happen. Sure, the functions produce many actions. But if it's going against the 1:1 rule, that's the fault of the user; they set the requirements to call such functions. If my functions aren't 1:1, that your fault. :). However, I've added functions for those paranoid, uneducated people who seem to think they go against 1:1. I introduced along side the RS_Click_... functions, a new set of RS_Move_... functions. They produce simply one action. For example, say you had your inventory open and tried... F3:: RS_Move_Prayer(3) ...it would move the mouse over the prayer tab as to not create more actions then 1. If your prayer tab was open, it would move your mouse to the 3rd prayer. You could use those RS_Move_... functions for things like Firemaking... Log_Color:=0x000000 ;~ Use RS_Get_Inventory_Item_Color() to get the color of the logs and store it into Log_Color Home:: RS_Move_Inventory_Item(1) Return End:: Loop, 28 If(RS_Get_Inventory_Item_Color(A_Index)==Log_Color) { RS_Move_Inventory_Item(A_Index) Break } Return See? Nothing illegal done here. Pressing Home moves the mouse to the first inventory item slot, that's it. Pressing End moves the mouse to the first found log in your inventory, that's it. 1:1. So you could Firemake with (And this is legal according to TIF standards)... Home (Move mouse) Left Click End (Move mouse) Left Click Home (Move mouse) Left Click End (Move mouse) Left Click ... However, according to you, the TIF administrators and mods, the above is legal. What you're having problems with is scripts being 2:2 or 3:3. Pushing 2 buttons and then the 2 actions being performed. I thought macros and things were illegal if they gave players and unfair advantage. Is it not? How is changing a script from 1:1 to 2:2 or 3:3 giving them an advantage? After-all, the following are the exact same... ^F3:: RS_Click_Quick_Prayer() ;~ Moves the mouse to the quick prayer and clicks. 2 actions produce 2 outputs. 2:2. ...and... F3:: RS_Move_Quick_Prayer() ;~ Moves the mouse to the quick prayer. The user must then press a second button to click. 2 actions produce 2 outputs. 1:1. They both require to buttons to be pushed for the same outcome. Why in God's name are you making such a big [bleep]ing deal over it? Is the first one giving someone an advantage that the second one isn't? Is the first one any faster then the second? No? Then what the hell is the big deal? You people seem to think those functions and scripts were written with ill-intent. "Zomg! Botting with AHK!" Believe it or not, they were written to make RuneScape more enjoyable and perhaps a little easier. They were written to help out. They do what Jagex fails to do; Provide a customizable gameplay. For example, I don't like my F5 key opening my attack styles. I'd rather it open my friends list for quick chatting. Imagine that; there's functions for just that! Ask yourselves, administrators and mods, what is the difference between 1:1, 2:2 and 3:3? A few milliseconds, if any at all. Is that worth the hassle that you are causing over it? Which is exactly what you, and I mean the TIF staff in general, are doing to me. Saying that my work, which was designed for the sole purpose of helping out, are scripts and functions for botting.