yea something that would alert on goblin or champ pack would be nice ;p, doesnt have to show them on map or anything just a little warning would be cool^^
yea something that would alert on goblin or champ pack would be nice ;p, doesnt have to show them on map or anything just a little warning would be cool^^
We have to start to talk about the legitimity of this HUD in Blizzard's eye. Somewhere I see a post where people linked a support private message telling him that the tools (maybe DPS display or Loot Alerts was that?).
What do you think? Monster readout, warning on some types (elites, goblins) can trigger Blizzard to consider this as a maphack and ban it?
Or I'm naive and they will ban this to the deep hell instantly, simply because it's reading D3's memory?
Last edited by KillerJohn; 12-14-2012 at 02:40 AM.
First post updated with:
- automatic config reload when the config.xml is changed
- complete monster readout (location, name, maximum/current hp, etc)
now I'm working on a kill-counter (it's a tricky one...) and a DPS graph and a path-saver/drawer...
Last edited by KillerJohn; 12-14-2012 at 03:52 AM.
I liked this one: http://www.ownedcore.com/forums/atta...bohud_test.jpg
It's like radar style circles ^^ I think it could be something like that with highlighted circles we want to see.
From what I remember maphacks in D2 were safe until point where sting allowed to read everything from memory including monster positions and showing them on minimap.
I don't think they'll ban it only because it reads memory If they find it dangerous they'll ban it ^^
New feature: kill counter and stats on the GainPanel. Monster detection is not 100 accurate because of some D3 specific "tricks"...
New feature: if you press F8 ingame, then the HUD is adding a new line into a path file (.\saved_paths\A1_trOUT_NewTristram.path for example) with the current coordinate.
With notepad you can name every point like in the following example.
The path files are auto-reload too, like the main config.xml. Every change is reflected realtime in the HUD.Code:2966.39, 2814.12, 28.3, start 2993.51, 2813.67, 28.3, noname 3005.14, 2837.17, 28.3, noname 2989.72, 2862.30, 28.3, checkpoint 2957.75, 2856.56, 28.2, noname
You can define any number of those circles manually, so you can make that radar feeling for yourself. Every circle can have different colors, transparency and line width.
Just look the OP's config example XML.
Last edited by KillerJohn; 12-14-2012 at 05:24 AM.
This is hot as hell!
Just wanan know if its detactable before i start using it ? Or only client side?
If you can add possibility to add straight lines for each world direction - north - south, west - east it'd be looking insane But it's rather optional It's anyway gonna make playing, optimizing routes so much easier, yay!
new features:
- curved path drawing http://i48.tinypic.com/sm9eli.png
- minimap ping on legendary/set items
DPS meter is done.
I'm starting to think that nobody is interested in this, except 4 people
It's probably because D3 sections in forums I know ( bh, this one, d2jsp, d2trade.pl ) are nearly dead. I think too much people already dropped game.
As for the drawing you already posted it way I would like it
I mean the 2 lines crossing x and y
And another question - how do you save waypoints? Will we be able to name checkpoints instantly when making them ( like in the external window ) ?
Last edited by Huggarn; 12-14-2012 at 11:51 AM.
Oh please add a debuff window and proc notices
Like when you get Revenge proc and it gives you a sort of warning on the screen which can be configured.
And some cooldown notices would be also great
Are you kidding, I'm sure a lot of people are silently waiting for your tool.
As for suggestions, it's hard to find good ideas since it seems you already implemented a lot of functionalities.
Could you simulate how much gold we could have picked up with extra pickup range?
Could be intersting to break xp/h by zone, that way it would be easier to detect if a specific zone/level is a waste of time
Last edited by neF4ST; 12-14-2012 at 02:16 PM.
Reading active buffs (on/off) is easy. Determining WHEN will it gone, it's a hard one... I'll look into that. But warming the window? Really ?
Reading cooldown (cd active or not) is easy too. But its already there on the screen
The pickup range simulation is the winner of todays ideas ))) It's f*cking hard to implement, but not impossible.
Now I'm focusing other things, but already noted your idea
Cool, what do I win?