Stev

I've fixed this issue. Just waiting on MageUK to push through the update. :P.

Edit: Resolved. Removed script.

There's been a lot of trouble with the map dragging. I assume it was the big map when it happened? For now, a temporary fix, go to My Documents\DGSweeper\resource.ini. Open it with Notepad. You should see something like: Note the _dgs.x and _dgs.y. Add those to yours. It doesn't matter where and you can change the values. Save it and reload. It should position there. That is just a quick fix until I write a fix for it myself. :P.

That is the complete opposite of what I would have thought... I forgot to remove a sleep (75) from when moving the big map - which is why you'll probably notice it doesn't move as smoothly. I figured that would have been the one that works of the two. Currently, DGSweeper monitors the following messages: WM_LBUTTONDOWN = 0x201 WM_LBUTTONDBLCLK = 0x203 WM_RBUTTONDOWN = 0x204 WM_RBUTTONDBLCLK = 0x206 At first I thought, "I'll just monitor WM_LBUTTONUP = 0x202 also, and have it stop the move." Sounds easy enough, right? Of course, nope. The WM_LBUTTONUP has to occur over top of the DGSweeper window for it to receive the message. So, if you clicked and quickly moved your mouse (talking under a millisecond here) and released the button before the window could catch up - it would continually follow the mouse. Now, any normal developer would say, "Use PostMessage,0xA1,2,,,A." That's the message to send to a window to tell it to move, I guess would be the easiest way to explain it. It's like telling it I've clicked it's title bar. In any other case, I'd use that. However, because the DGSweeper is set to a style of NoActivate, so the window won't take focus when clicked and yet not be Disabled (unable to interact with), 0xA1 has some really weird behavior. I'll keep thinking. :P.

Quick question: Does it do it with both map sizes?

Sounds like it's not receiving the button up message from your mouse. I've have a few people tell me this - I'll try and think of a solution and push it through. Thanks for letting me know. :).

I need the screenshot to be of your actual dungeoneering map, not DGSweeper. :P. You're lucky. I was actually going to delete the C++ (since I've already compiled it to machine code) that searches the map for markers earlier but didn't. :).

(On screen keyboard) Pretty sure I know the cause. Can you upload a full-size PNG image of your map? It's important that it's not compressed so I can get the exact values. I changed all the captures from being 32 bits per pixel to 16 to make things a bit faster, but it also changed the color values and quality. I figured, since everyone I sent it to had the same, that they were the same for everyone - however once I get yours I can add yours. The screenshot will just be to see if your 32bpp differ from mine. If they do, I'll send you quick script that'll snapshot a 16bpp of you map. :).

When the legend window is shown, how many players does it capture in a 5 member team? DOes it show them all on the legend window and just not on the map?

Especially when I'm not home, nor even in the same city at the moment. What exactly is happening when you try to run it?

Is it not possible to override application settings with the application name JagexLauncher? If not, I'll be able to figure out how when I get home, but I'm not in Windsor at the moment; travelling to see my surgeon.

Also, using Flurry? Furry? IDK, I can't log into RuneScape at the moment, but it has a chance of causing him to barricade and heal for a LOT.

What's the method used? I've never looked into why exactly it requires changing the process name.

Rename the process JagexLauncher dot exe (Tip.It forum censor >.<)

The DGSweeper page has a list of hotstrings and hotkeys - some of which for resizing the map. :P.

Ah, knew I'd overlooked something. When I get time I'll re-add it - it's a quick fix. It's already set up for it to be able to be set to transparent, only no option on the interface. Apologies.

Have you altered RuneScape to have bloom with DirectX and AA? If it's not a browser (SwiftKit counts as a browser since it simply embeds IE), the process has to be called JagexLauncher dot exe (Capitalization is important). On the highway ATM, so am limited to my responses, sorry. :P.

When opening the map, you'll get a tooltip that'll appear with a few random numbers. This is fixed and just waiting for MageUK to reupload. :).

Update 1.0.4.2 A complete rewrite from the ground up. Pushing through the update for this version was nerve wracking, to say the least... Quite literally everything was written from scratch. Not a single line was copied. Changes DGConnect is now classified under Share Maps. It has been completely restructured. It now takes a matter of milliseconds to retrieve and send maps between players! The way DGSweeper captures the map has been completely redone. Instead of always looking for the map, it'll only look for 2 seconds after you click the map button. This was to save resources and lower CPU usage. Relative positioning has been removed. Simply click and drag the borders of the DGSweeper to reposition it. The timer has now been placed on top of the map to save room. As always, click to start and stop it. The timer now starts when a map is retrieved from another player. The party details can now be displayed on a legend window as it used to in the past. The legend must be shown to tell DGSweeper to capture the party details. Hiding the legend will show the names on the map. All false positives from virus companies have been dealt with. Many of the tray options have been removed. Use the hotkeys for things like toggling the map and other features. The riddle and potion features have been placed on the main interface to make things more user friendly and easier to read. A hiscores feature has been added. It also comes with a hotstring! Check out all the hotstrings here. Sharing maps now has the hotstring !dgc. The main interface is no longer a standard classed GUI and a lot of DGSweeper functions are controlled by a web browser. DGSweeper has a Facebook page (facebook.com/dgsweeper)! Give us a like for the most up-to-date information! A donation button has been added to the main interface. Donations given from this interface do not go to Tip.It. They go to me, helping me be able to spend time developing DGSweeper and keeping it up-to-date. It'll also go to me setting up my life that I'm soon to be restarting. Aero can now be disabled for Windows lower then Window 8 that support it. The key utility can now place gatestones! I don't expect this to be entirely bug free. But, before posting a bug issue for not capturing the map, make sure you go to Options > Navigation Bar and make sure it's set correctly. Thanks guys!

If you're not far enough away from his orange orbs, say 4-5 squares away, you get hit a 1 but continue to get hit with a repeating attack for 200-500.

Player owned casinos.

I can probably guess what this was about. Glad you figured it out. :P.

Fixed the strange bug. It was an issue with the RuneScape width and height partnered with a SetFormat of 0.0. :? .

I'll still put some time into it here and there... But I keep running into a strange bug when ever I use it with Ben... And I can't seem to figure out what it is or what's causing it. The past week or two I've not been able to turn on my PC and sit at it for longer then a minute or two before I get pissed off and turn it back off... Have been trying to get it out for you guys just so I don't feel like a dick. Lol.

He can also heal a portion of the damage done to the players from his red/orange gas balls, as you put it. :P.