|
Hello all,
I just had a quick look at your code - I thought about forking or branching it so I could help with the development.
One thing I would like to point out is that **I** think that the way you attach and read in-process memory from the SC2 process could somewhat get the users into trouble. Don't get me wrong, this is a very clever idea - and as far as I'm concerned, totally harmless - , but this jumped out the code when I was reading it.
You could change it so you have a few predefined build orders for each match-up, and map it to a few hotkeys and show the overlay with the BO you select... I don't know, just thinking here.
PM me if you want to talk more about this.
Cheers!
|
perfect timing.
I had a friend of mine give me his account today to play on, I wanted to play random and use it for practice and new builds (not to mess up my main account by offracing). Long story short, after 8 games as Random i realized it will take me too long to learn all the match ups, and gave up on the random thing. And now i bump into this thread, looks like precisely what I needed! Should make off-racing a lot easier and more enjoyable, thank you
|
Intense! keep up the BO updates please =)
|
On November 22 2011 02:15 FMStyles wrote:
First those race timers and now a ingame buildorder manager, are you guys serious?
The core part of the application is a build order manager. The in game options are entirely that. Options. Not mandatory.
On November 22 2011 02:15 rasers wrote:
holy fuck... actually start learning the game and dont let some programs or the game itself do everything for u guys...
now go make a bot that makes the build order for u so u can go afk the first 5minutes or what? ... rofl
Unfortunately we're not all blessed with photographic memory like you evidently are.
[/QUOTE]
Its not about a photographic memory, its about sitting down and grinding games to learn your build inside and out. Personally i dont think what you have made is a bad thing at all. There are alot of people who could benefit from it and if that is possible then why not let them, but to give you perspective ive sat down working on making/practicing Build orders in games verse easy ai for hours and hours just to get it down completely and see how it feels in the most ideal situations.
The reason people are mad that this exists means that alot of people will skip the process so many of us had to burn though to get to where we are today on the ladder..
Again personally i think this is cool and helpful for lower level people so thank you for your contribution.
Crash
|
Nice to see people are juast as devided as last time. Personally, I honestly don't see what the problem is. You want people to suffer by alt-tabbing when learning a new build causing their game to be ruined? Obviously nobody is going to rely on this after nailing down a build (well, maybe in the lower leagues). As for the people bringing up tournaments... r u srs? You think pros turn up to tournaments with a notepad file to alt-tab to ingame?
To address some other points:
1. To use the overlay, YOU MUST USE WINDOWED MODE. The way this overlay works is the same way there is absolutely no reason to get banned for using it. It's an invisible window, not a DirectX overlay injection.
2. People still having issues not mentioned above should post here or message me.
3. Mac users can use Mono, but it's doubtful that the overlays will work.
On November 22 2011 12:43 FeelinGood wrote:
Hello all,
I just had a quick look at your code - I thought about forking or branching it so I could help with the development.
One thing I would like to point out is that **I** think that the way you attach and read in-process memory from the SC2 process could somewhat get the users into trouble. Don't get me wrong, this is a very clever idea - and as far as I'm concerned, totally harmless - , but this jumped out the code when I was reading it.
You could change it so you have a few predefined build orders for each match-up, and map it to a few hotkeys and show the overlay with the BO you select... I don't know, just thinking here.
PM me if you want to talk more about this.
Cheers!
The memory attachment options are optional, disabled by default and come with a huge warning when you enable them. However, they read only the same information that StarInfo and XSplit Scene Switcher read, and the users of those have been absolutely fine after many months.
|
great stuff indeed, I've looked at this thing on reddit like 7 times already and never clicked on it cuz i thought it was a stupid thing, but I'm glad I finally did =D
|
On November 22 2011 13:41 Veritas. wrote:Nice to see people are juast as devided as last time. Personally, I honestly don't see what the problem is. You want people to suffer by alt-tabbing when learning a new build causing their game to be ruined? Obviously nobody is going to rely on this after nailing down a build (well, maybe in the lower leagues). As for the people bringing up tournaments... r u srs? You think pros turn up to tournaments with a notepad file to alt-tab to ingame? To address some other points: 1. To use the overlay, YOU MUST USE WINDOWED MODE. The way this overlay works is the same way there is absolutely no reason to get banned for using it. It's an invisible window, not a DirectX overlay injection. 2. People still having issues not mentioned above should post here or message me. Show nested quote +On November 22 2011 12:43 FeelinGood wrote:
Hello all,
I just had a quick look at your code - I thought about forking or branching it so I could help with the development.
One thing I would like to point out is that **I** think that the way you attach and read in-process memory from the SC2 process could somewhat get the users into trouble. Don't get me wrong, this is a very clever idea - and as far as I'm concerned, totally harmless - , but this jumped out the code when I was reading it.
You could change it so you have a few predefined build orders for each match-up, and map it to a few hotkeys and show the overlay with the BO you select... I don't know, just thinking here.
PM me if you want to talk more about this.
Cheers! The memory attachment options are optional, disabled by default and come with a huge warning when you enable them. However, they read only the same information that StarInfo and XSplit Scene Switcher read, and the users of those have been absolutely fine after many months.
I've already posted about it, but I'm having the same problem as many are having on page 4. The overlay works, but after I close SC2 or exit a game I can't interact with the actual interface where I choose options/edit build orders/etc. etc.. I end the process and try to restart the application, but it won't work. It loads to where it will do the overlay during the game, but the actual interface simply refuses to work.
Thanks for any help you can give!
|
Fantastic.
Will definitely use for practice games. Seems kind of cheap to use in Ladder or anything, but definitely a great tool for practicing. Sure as hell could use anything I can get.
|
On November 22 2011 13:46 Mauldo wrote:Show nested quote +On November 22 2011 13:41 Veritas. wrote:Nice to see people are juast as devided as last time. Personally, I honestly don't see what the problem is. You want people to suffer by alt-tabbing when learning a new build causing their game to be ruined? Obviously nobody is going to rely on this after nailing down a build (well, maybe in the lower leagues). As for the people bringing up tournaments... r u srs? You think pros turn up to tournaments with a notepad file to alt-tab to ingame? To address some other points: 1. To use the overlay, YOU MUST USE WINDOWED MODE. The way this overlay works is the same way there is absolutely no reason to get banned for using it. It's an invisible window, not a DirectX overlay injection. 2. People still having issues not mentioned above should post here or message me. On November 22 2011 12:43 FeelinGood wrote:
Hello all,
I just had a quick look at your code - I thought about forking or branching it so I could help with the development.
One thing I would like to point out is that **I** think that the way you attach and read in-process memory from the SC2 process could somewhat get the users into trouble. Don't get me wrong, this is a very clever idea - and as far as I'm concerned, totally harmless - , but this jumped out the code when I was reading it.
You could change it so you have a few predefined build orders for each match-up, and map it to a few hotkeys and show the overlay with the BO you select... I don't know, just thinking here.
PM me if you want to talk more about this.
Cheers! The memory attachment options are optional, disabled by default and come with a huge warning when you enable them. However, they read only the same information that StarInfo and XSplit Scene Switcher read, and the users of those have been absolutely fine after many months. I've already posted about it, but I'm having the same problem as many are having on page 4. The overlay works, but after I close SC2 or exit a game I can't interact with the actual interface where I choose options/edit build orders/etc. etc.. I end the process and try to restart the application, but it won't work. It loads to where it will do the overlay during the game, but the actual interface simply refuses to work. Thanks for any help you can give!
So, you can load an overlay in-game. But when finished can't interact with the main window? Can you interact with the main window after end processing and restarting?
Are you using the ingame build selection option?
|
On November 22 2011 13:56 Veritas. wrote:Show nested quote +On November 22 2011 13:46 Mauldo wrote:On November 22 2011 13:41 Veritas. wrote:Nice to see people are juast as devided as last time. Personally, I honestly don't see what the problem is. You want people to suffer by alt-tabbing when learning a new build causing their game to be ruined? Obviously nobody is going to rely on this after nailing down a build (well, maybe in the lower leagues). As for the people bringing up tournaments... r u srs? You think pros turn up to tournaments with a notepad file to alt-tab to ingame? To address some other points: 1. To use the overlay, YOU MUST USE WINDOWED MODE. The way this overlay works is the same way there is absolutely no reason to get banned for using it. It's an invisible window, not a DirectX overlay injection. 2. People still having issues not mentioned above should post here or message me. On November 22 2011 12:43 FeelinGood wrote:
Hello all,
I just had a quick look at your code - I thought about forking or branching it so I could help with the development.
One thing I would like to point out is that **I** think that the way you attach and read in-process memory from the SC2 process could somewhat get the users into trouble. Don't get me wrong, this is a very clever idea - and as far as I'm concerned, totally harmless - , but this jumped out the code when I was reading it.
You could change it so you have a few predefined build orders for each match-up, and map it to a few hotkeys and show the overlay with the BO you select... I don't know, just thinking here.
PM me if you want to talk more about this.
Cheers! The memory attachment options are optional, disabled by default and come with a huge warning when you enable them. However, they read only the same information that StarInfo and XSplit Scene Switcher read, and the users of those have been absolutely fine after many months. I've already posted about it, but I'm having the same problem as many are having on page 4. The overlay works, but after I close SC2 or exit a game I can't interact with the actual interface where I choose options/edit build orders/etc. etc.. I end the process and try to restart the application, but it won't work. It loads to where it will do the overlay during the game, but the actual interface simply refuses to work. Thanks for any help you can give! So, you can load an overlay in-game. But when finished can't interact with the main window? Can you interact with the main window after end processing and restarting? Are you using the ingame build selection option?
Yes, that's the exact issue. I can load the overlay in game and I'm using the ingame build selection option. But when I'm finished with the game I can't interact with the main window even after end the process and restarting the application.
I'm playing a game against the AI and I have the advanced options that grab info from battle.net activated. I'd reference them specifically, but they're the ones that you give a warning about in the program.
|
On November 22 2011 13:59 Mauldo wrote:Show nested quote +On November 22 2011 13:56 Veritas. wrote:On November 22 2011 13:46 Mauldo wrote:On November 22 2011 13:41 Veritas. wrote:Nice to see people are juast as devided as last time. Personally, I honestly don't see what the problem is. You want people to suffer by alt-tabbing when learning a new build causing their game to be ruined? Obviously nobody is going to rely on this after nailing down a build (well, maybe in the lower leagues). As for the people bringing up tournaments... r u srs? You think pros turn up to tournaments with a notepad file to alt-tab to ingame? To address some other points: 1. To use the overlay, YOU MUST USE WINDOWED MODE. The way this overlay works is the same way there is absolutely no reason to get banned for using it. It's an invisible window, not a DirectX overlay injection. 2. People still having issues not mentioned above should post here or message me. On November 22 2011 12:43 FeelinGood wrote:
Hello all,
I just had a quick look at your code - I thought about forking or branching it so I could help with the development.
One thing I would like to point out is that **I** think that the way you attach and read in-process memory from the SC2 process could somewhat get the users into trouble. Don't get me wrong, this is a very clever idea - and as far as I'm concerned, totally harmless - , but this jumped out the code when I was reading it.
You could change it so you have a few predefined build orders for each match-up, and map it to a few hotkeys and show the overlay with the BO you select... I don't know, just thinking here.
PM me if you want to talk more about this.
Cheers! The memory attachment options are optional, disabled by default and come with a huge warning when you enable them. However, they read only the same information that StarInfo and XSplit Scene Switcher read, and the users of those have been absolutely fine after many months. I've already posted about it, but I'm having the same problem as many are having on page 4. The overlay works, but after I close SC2 or exit a game I can't interact with the actual interface where I choose options/edit build orders/etc. etc.. I end the process and try to restart the application, but it won't work. It loads to where it will do the overlay during the game, but the actual interface simply refuses to work. Thanks for any help you can give! So, you can load an overlay in-game. But when finished can't interact with the main window? Can you interact with the main window after end processing and restarting? Are you using the ingame build selection option? Yes, that's the exact issue. I can load the overlay in game and I'm using the ingame build selection option. But when I'm finished with the game I can't interact with the main window even after end the process and restarting the application. I'm playing a game against the AI and I have the advanced options that grab info from battle.net activated. I'd reference them specifically, but they're the ones that you give a warning about in the program.
What happens after you end process and restart? Does the window even show? Can you delete the BuildOrderNotebook folder in My Document/StarCraft II and try again without enabling advanced options?
|
wait, why are people complaining?
isn't it just an on-screen build order? my fd would put up some stickers with BO next to the monitor, not that different?
|
Show nested quote +On November 22 2011 13:28 CrashD wrote:On November 22 2011 02:15 FMStyles wrote:
First those race timers and now a ingame buildorder manager, are you guys serious? The core part of the application is a build order manager. The in game options are entirely that. Options. Not mandatory. On November 22 2011 02:15 rasers wrote:
holy fuck... actually start learning the game and dont let some programs or the game itself do everything for u guys...
now go make a bot that makes the build order for u so u can go afk the first 5minutes or what? ... rofl Unfortunately we're not all blessed with photographic memory like you evidently are. Its not about a photographic memory, its about sitting down and grinding games to learn your build inside and out. Personally i dont think what you have made is a bad thing at all. There are alot of people who could benefit from it and if that is possible then why not let them, but to give you perspective ive sat down working on making/practicing Build orders in games verse easy ai for hours and hours just to get it down completely and see how it feels in the most ideal situations. The reason people are mad that this exists means that alot of people will skip the process so many of us had to burn though to get to where we are today on the ladder.. Again personally i think this is cool and helpful for lower level people so thank you for your contribution. Crash
No one 'had' to grind through practice games, that's a choice you make and it sounds like it paid off for you. This tool does not replicate knowing the build by heart; having to constantly glace at a BO is inefficient and reduces the amount of attention you have to spend on other things.
|
On November 22 2011 14:06 Veritas. wrote:Show nested quote +On November 22 2011 13:59 Mauldo wrote:On November 22 2011 13:56 Veritas. wrote:On November 22 2011 13:46 Mauldo wrote:On November 22 2011 13:41 Veritas. wrote:Nice to see people are juast as devided as last time. Personally, I honestly don't see what the problem is. You want people to suffer by alt-tabbing when learning a new build causing their game to be ruined? Obviously nobody is going to rely on this after nailing down a build (well, maybe in the lower leagues). As for the people bringing up tournaments... r u srs? You think pros turn up to tournaments with a notepad file to alt-tab to ingame? To address some other points: 1. To use the overlay, YOU MUST USE WINDOWED MODE. The way this overlay works is the same way there is absolutely no reason to get banned for using it. It's an invisible window, not a DirectX overlay injection. 2. People still having issues not mentioned above should post here or message me. On November 22 2011 12:43 FeelinGood wrote:
Hello all,
I just had a quick look at your code - I thought about forking or branching it so I could help with the development.
One thing I would like to point out is that **I** think that the way you attach and read in-process memory from the SC2 process could somewhat get the users into trouble. Don't get me wrong, this is a very clever idea - and as far as I'm concerned, totally harmless - , but this jumped out the code when I was reading it.
You could change it so you have a few predefined build orders for each match-up, and map it to a few hotkeys and show the overlay with the BO you select... I don't know, just thinking here.
PM me if you want to talk more about this.
Cheers! The memory attachment options are optional, disabled by default and come with a huge warning when you enable them. However, they read only the same information that StarInfo and XSplit Scene Switcher read, and the users of those have been absolutely fine after many months. I've already posted about it, but I'm having the same problem as many are having on page 4. The overlay works, but after I close SC2 or exit a game I can't interact with the actual interface where I choose options/edit build orders/etc. etc.. I end the process and try to restart the application, but it won't work. It loads to where it will do the overlay during the game, but the actual interface simply refuses to work. Thanks for any help you can give! So, you can load an overlay in-game. But when finished can't interact with the main window? Can you interact with the main window after end processing and restarting? Are you using the ingame build selection option? Yes, that's the exact issue. I can load the overlay in game and I'm using the ingame build selection option. But when I'm finished with the game I can't interact with the main window even after end the process and restarting the application. I'm playing a game against the AI and I have the advanced options that grab info from battle.net activated. I'd reference them specifically, but they're the ones that you give a warning about in the program. What happens after you end process and restart? Does the window even show? Can you delete the BuildOrderNotebook folder in My Document/StarCraft II and try again without enabling advanced options?
That worked! I completely ended the process and deleted the BuildOrderNotebook folder. When I restarted the interface popped up and everything is going smooth. Thanks!
|
On November 22 2011 14:39 Mauldo wrote:Show nested quote +On November 22 2011 14:06 Veritas. wrote:On November 22 2011 13:59 Mauldo wrote:On November 22 2011 13:56 Veritas. wrote:On November 22 2011 13:46 Mauldo wrote:On November 22 2011 13:41 Veritas. wrote:Nice to see people are juast as devided as last time. Personally, I honestly don't see what the problem is. You want people to suffer by alt-tabbing when learning a new build causing their game to be ruined? Obviously nobody is going to rely on this after nailing down a build (well, maybe in the lower leagues). As for the people bringing up tournaments... r u srs? You think pros turn up to tournaments with a notepad file to alt-tab to ingame? To address some other points: 1. To use the overlay, YOU MUST USE WINDOWED MODE. The way this overlay works is the same way there is absolutely no reason to get banned for using it. It's an invisible window, not a DirectX overlay injection. 2. People still having issues not mentioned above should post here or message me. On November 22 2011 12:43 FeelinGood wrote:
Hello all,
I just had a quick look at your code - I thought about forking or branching it so I could help with the development.
One thing I would like to point out is that **I** think that the way you attach and read in-process memory from the SC2 process could somewhat get the users into trouble. Don't get me wrong, this is a very clever idea - and as far as I'm concerned, totally harmless - , but this jumped out the code when I was reading it.
You could change it so you have a few predefined build orders for each match-up, and map it to a few hotkeys and show the overlay with the BO you select... I don't know, just thinking here.
PM me if you want to talk more about this.
Cheers! The memory attachment options are optional, disabled by default and come with a huge warning when you enable them. However, they read only the same information that StarInfo and XSplit Scene Switcher read, and the users of those have been absolutely fine after many months. I've already posted about it, but I'm having the same problem as many are having on page 4. The overlay works, but after I close SC2 or exit a game I can't interact with the actual interface where I choose options/edit build orders/etc. etc.. I end the process and try to restart the application, but it won't work. It loads to where it will do the overlay during the game, but the actual interface simply refuses to work. Thanks for any help you can give! So, you can load an overlay in-game. But when finished can't interact with the main window? Can you interact with the main window after end processing and restarting? Are you using the ingame build selection option? Yes, that's the exact issue. I can load the overlay in game and I'm using the ingame build selection option. But when I'm finished with the game I can't interact with the main window even after end the process and restarting the application. I'm playing a game against the AI and I have the advanced options that grab info from battle.net activated. I'd reference them specifically, but they're the ones that you give a warning about in the program. What happens after you end process and restart? Does the window even show? Can you delete the BuildOrderNotebook folder in My Document/StarCraft II and try again without enabling advanced options? That worked! I completely ended the process and deleted the BuildOrderNotebook folder. When I restarted the interface popped up and everything is going smooth. Thanks!
Does it break again when you enable the advanced ingame build selector?
|
Looks sexy, may give it a try ;D
|
I've released an update. It should alleviate the interface issues some people have having.
|
I tihnk theneww update caused problems for me. Pmed you about it
Nvm, deleting the folder fixed it!
|
Awesome,
i thought about this myself but never got it working in C++.
Thanks for this man !
|
Fortunately I have a second monitor, but I'd definitely try this out for when I off race if I didn't have an extra monitor ;D
|
|
|
|
|
|
EPT
