HOTS SC2MapPro

I have tried to look around the forum first but did not find anything...

With HOTS coming out in a month is there going to be a SC2MapPro for it?

I am also curious, because I have the Beta for hots and I'd really like to use MapPro with it but sadly it gives me the wrong version error.. Admin, is there anything you can do in the short term to make mappro usable for HotS? Doesn't even really have to be for the new units really.

Hello everyone, i'm also interested in that sc2mappro for hots =)

Everyone is interested.....

I know , i know.......

I am working on something new, something that permits users to develop bots/hacks for sc2 and other games.

About hots, what i have to do is finding the new mem offsets and write down some code for the new units.

If someone is interesetd, i am thinking about putting sc2mappro and sc2simplehack sourcecodes as GPL projects.

Admin wrote:

I know , i know.......

I am working on something new, something that permits users to develop bots/hacks for sc2 and other games.

About hots, what i have to do is finding the new mem offsets and write down some code for the new units.

If someone is interesetd, i am thinking about putting sc2mappro and sc2simplehack sourcecodes as GPL projects.

Really dont think thats a good idea

The second you do that someone will nick it, claim its theres, put it on d3s where everyone uses it, will work for a couple of weeks then we will all be banned

agreed. personally i'm studying at Epitech, french informatics school at high level, and i am very curious how basically people make interaction between their code and external software.

Cheers

Zergsensation wrote:

Admin wrote:

I know , i know.......

I am working on something new, something that permits users to develop bots/hacks for sc2 and other games.

About hots, what i have to do is finding the new mem offsets and write down some code for the new units.

If someone is interesetd, i am thinking about putting sc2mappro and sc2simplehack sourcecodes as GPL projects.

Really dont think thats a good idea

The second you do that someone will nick it, claim its theres, put it on d3s where everyone uses it, will work for a couple of weeks then we will all be banned

Yeah that is one possibility.
Look what happened to qazzy's code when it went public. No disrespect to the guy that handles that project now but its a complete mess and hardly functions anymore. I fear the same could happen to mapPro.

I understand the Admin though coding takes a huge amount of time and keeping things updated is hard work especially if you have a life and family outside to juggle around.

So far it hasn't been discussed but I think perhaps its time? I mean mapPro users have had a good run for their initial donation. If its a question of funding maybe we could donate to the Hots version of mapPro for the same price as the regular mapPro project to make it worth the Admins time.?

Better that than see it all die off.



.

I think out of all the donations given, about 50% of community would purchase it for HoTS, just like HotS is an expansion we can give like a expansion type price? Instead of 30, 20? But I would not like to see the code go GPL as that depreciates the value mappro has ascertained.

Takino wrote:

Look what happened to qazzy's code when it went public. No disrespect to the guy that handles that project now but its a complete mess and hardly functions anymore. I fear the same could happen to mapPro.

I understand the Admin though coding takes a huge amount of time and keeping things updated is hard work especially if you have a life and family outside to juggle around.

So far it hasn't been discussed but I think perhaps its time? I mean mapPro users have had a good run for their initial donation. If its a question of funding maybe we could donate to the Hots version of mapPro for the same price as the regular mapPro project to make it worth the Admins time.?

Better that than see it all die off.

Qazzies code wasn't released to public directly.
When he left, his hack was reserved.
And since he used to code in C# and didn't use any protection you can build the entire project in a few seconds.
However, with reserved code, you don't have comments which explain a lot.

Therfore we have a huge spaghetti- like code in the Qazzy legacy.
But it doesn't matter since nobody gives contribute to this project.


I'd like to add that a public SC2mapPro would lead into nothing.
As we can see at Nuke's project, nobody contributes to this.
It's extremely good for learning but that's not important since you can find 100'000 code examples for problem x.

Looking forward to HOTS update

I don't see a reason not to make it a separate project, I feel I've gotten much more than what I paid for initially. HotS is close enough to a new game, so it should be a separate project that we must donate more for.

I think that all would agree or comply with making HOTS a new project and re-paying for it... Admin, just tell us what to do.

I believe that Patch 2.04 is going to have almost the exact offsets as HOTS since the client tomorrow will be the same client for HOTS.

Admin wrote:

I know , i know.......

I am working on something new, something that permits users to develop bots/hacks for sc2 and other games.

About hots, what i have to do is finding the new mem offsets and write down some code for the new units.

If someone is interesetd, i am thinking about putting sc2mappro and sc2simplehack sourcecodes as GPL projects.

Please do not make the Source code public, for our safety. Plz don't do it. A humble request. Thanks in advance.

I agree:

• We can pay for HOTS version
  
• Do not make the Source code public, for our safety.

skillcoder wrote:

I agree:

• We can pay for HOTS version
  
• Do not make the Source code public, for our safety.

Making the source code public is actually a great idea I believe. There is absolutely no security issue etc with doing this. Warden, StarCraft II's anti-cheat, actually scans for game changes. SC2MapPro makes no such change. Therefore, this is undetectable. In fact, making this public and allowing people to make changes/modifications which actually make it more beneficial for all the standard users! Not only that, but believe it or not, it will make it more secure! Different MD5 EXE's and different signatures. If Warden searched for memory scans then I believe 90% of the population would of been banned because of anti-virus scanning.

I personally would love to see the source code and be able to actually update it myself without relying on other people to do it for me.

Quote :

Making the source code public is actually a great idea I believe. There is absolutely no security issue etc with doing this. Warden, StarCraft II's anti-cheat, actually scans for game changes. SC2MapPro makes no such change. Therefore, this is undetectable. In fact, making this public and allowing people to make changes/modifications which actually make it more beneficial for all the standard users! Not only that, but believe it or not, it will make it more secure! Different MD5 EXE's and different signatures. If Warden searched for memory scans then I believe 90% of the population would of been banned because of anti-virus scanning.

I personally would love to see the source code and be able to actually update it myself without relying on other people to do it for me.

+1

xPloit wrote:

skillcoder wrote:

I agree:

• We can pay for HOTS version
  
• Do not make the Source code public, for our safety.

Making the source code public is actually a great idea I believe. There is absolutely no security issue etc with doing this. Warden, StarCraft II's anti-cheat, actually scans for game changes. SC2MapPro makes no such change. Therefore, this is undetectable. In fact, making this public and allowing people to make changes/modifications which actually make it more beneficial for all the standard users! Not only that, but believe it or not, it will make it more secure! Different MD5 EXE's and different signatures. If Warden searched for memory scans then I believe 90% of the population would of been banned because of anti-virus scanning.

I personally would love to see the source code and be able to actually update it myself without relying on other people to do it for me.

What does that mean for those who can't update the source code by ourselves? Did you ever think about people changing the source code a little and claiming it theirs. Selling or restributing the hack? There will be a larger access and spread of this hack.... I think it would do more damage then good to make the source code public.

I will be first one to stay away from it, if it goes public. I dont wanna fcukup my precious account.

Please do not release the source code to the public, blizzard will be FORCED to take action if everyone were to start using this.

I would be more than happy to pay a little for the trouble of updating it from WoL to HoTS.

Legionary wrote:

Please do not release the source code to the public, blizzard will be FORCED to take action if everyone were to start using this.

I would be more than happy to pay a little for the trouble of updating it from WoL to HoTS.

This.

stickyfingerz11 wrote:

xPloit wrote:

skillcoder wrote:

I agree:

• We can pay for HOTS version
  
• Do not make the Source code public, for our safety.

Making the source code public is actually a great idea I believe. There is absolutely no security issue etc with doing this. Warden, StarCraft II's anti-cheat, actually scans for game changes. SC2MapPro makes no such change. Therefore, this is undetectable. In fact, making this public and allowing people to make changes/modifications which actually make it more beneficial for all the standard users! Not only that, but believe it or not, it will make it more secure! Different MD5 EXE's and different signatures. If Warden searched for memory scans then I believe 90% of the population would of been banned because of anti-virus scanning.

I personally would love to see the source code and be able to actually update it myself without relying on other people to do it for me.

What does that mean for those who can't update the source code by ourselves? Did you ever think about people changing the source code a little and claiming it theirs. Selling or restributing the hack? There will be a larger access and spread of this hack.... I think it would do more damage then good to make the source code public.

Exactly. If enough people use this blizzard will find a way to detect it. Staying small and staying under the radar is the best way to keep safe.