Report, edit, etc...Posted by Corbo(MM) on 2006-11-18 at 11:49:10
Ok, during my mapping era I didn't get to explore the world of EUDs, So I'd appreciate all the help provided.
Ok, so we all know that you could be able to have cheats online with EUDs, I need to know what exactly did that, the trigger, explanation, everything.
I need to know also in what version the EUDs became Dead, and until what version the trigger I'm asking for works.
Ok, so we all know that you could be able to have cheats online with EUDs, I need to know what exactly did that, the trigger, explanation, everything.
I need to know also in what version the EUDs became Dead, and until what version the trigger I'm asking for works.
Report, edit, etc...Posted by SomeIdiotNerd on 2006-11-18 at 12:58:17
well, Tux used a very good method for his, try checking out his unprotected Rush on his site...
Report, edit, etc...Posted by DT_Battlekruser on 2006-11-18 at 13:10:52
EUD Actions used the unit deaths of units that did not exist in order to directly edit the RAM of Starcraft, therefore allowing you to change absolutely any aspect of Starcraft, as long as it was in the range of RAM accessed by the SetDeaths() action.
EUD Actions were discovered in patch 1.13a, but work in any patch before that too. It was discovered that you could cause a buffer overflow, and therefor crash people's computers, but accessing memory outside the buffer limit for Starcraft. In patch 1.13b, Blizzard added a parameter that ignored the SetDeaths() action if the Unit ID was greater than 228.
Current in even 1.14 are EUD Conditions, which allowed you to directly read the RAM of Starcraft based on the same principle.
In order to edit or read something, you need to know its hex memory address, which can sometime be found in pre-formulated tables, or you can use a memory searcher such as ArtMoney to find it. You can then use MemCalc 5's Advanced Mode to change the hex offset into a trigger.
Here's the old tutorial, too: http://www.staredit.net/index.php?tutorial=240
EUD Actions were discovered in patch 1.13a, but work in any patch before that too. It was discovered that you could cause a buffer overflow, and therefor crash people's computers, but accessing memory outside the buffer limit for Starcraft. In patch 1.13b, Blizzard added a parameter that ignored the SetDeaths() action if the Unit ID was greater than 228.
Current in even 1.14 are EUD Conditions, which allowed you to directly read the RAM of Starcraft based on the same principle.
In order to edit or read something, you need to know its hex memory address, which can sometime be found in pre-formulated tables, or you can use a memory searcher such as ArtMoney to find it. You can then use MemCalc 5's Advanced Mode to change the hex offset into a trigger.
Here's the old tutorial, too: http://www.staredit.net/index.php?tutorial=240
Report, edit, etc...Posted by spinesheath on 2006-11-18 at 13:14:50
QUOTE(DT_Battlekruser @ Nov 18 2006, 02:10 PM)
Blizzard added a parameter that ignored the SetDeaths() action if the Unit ID was greater than 228.
[right][snapback]591057[/snapback][/right]
[right][snapback]591057[/snapback][/right]
Wait, deaths of extended players are still accessible? I guess it either never worked or you forgot to mention
Report, edit, etc...Posted by DT_Battlekruser on 2006-11-18 at 16:32:08
Deaths of extended players makes little difference because of the minuscule distance which it would extend beyond the deaths table.
You never could use a SetDeaths() action on player 9 and above though.
You never could use a SetDeaths() action on player 9 and above though.
Report, edit, etc...Posted by spinesheath on 2006-11-18 at 16:37:31
Well, it would still be something 
But who cares, it does not work 
But who cares, it does not work Report, edit, etc...Posted by Heimdal on 2006-11-19 at 14:03:57
But if you use the SetResources/Accumulate method (which I describe here: http://www.staredit.net/index.php?showtopic=35410), you're able to access a larger range of values and won't have the same limitations on players that SetDeaths does.
Report, edit, etc...Posted by DT_Battlekruser on 2006-11-19 at 14:05:02
Yeah, but there just aren't many interesting things in the memory there
Report, edit, etc...Posted by Heimdal on 2006-11-19 at 14:09:48
QUOTE(DT_Battlekruser @ Nov 19 2006, 02:05 PM)
Yeah, but there just aren't many interesting things in the memory there
[right][snapback]591572[/snapback][/right]
But it also encompasses everything you can do with the SetDeaths/Deaths triggers too. So, the extended resources triggers have a few small advantages. The only disadvantage I can think of is that there aren't any ready-made tools to find the numbers you need. But the math is easier, since all you have to do is subtract the offset of the resources table and divide by 48.[right][snapback]591572[/snapback][/right]
Report, edit, etc...Posted by Doodle77(MM) on 2006-11-19 at 14:21:06
So someone write a little piece of javascript or php to do that math for you
Report, edit, etc...Posted by yoni45 on 2006-11-19 at 15:21:54
QUOTE(Heimdal @ Nov 19 2006, 01:03 PM)
But if you use the SetResources/Accumulate method (which I describe here: http://www.staredit.net/index.php?showtopic=35410), you're able to access a larger range of values and won't have the same limitations on players that SetDeaths does.
[right][snapback]591571[/snapback][/right]
[right][snapback]591571[/snapback][/right]
Wait, but SetResources and such *was* killed off just as SetDeaths for higher indeces, correct?
Report, edit, etc...Posted by DT_Battlekruser on 2006-11-19 at 22:01:02
Wait, how do you go so far into the memory with a Resources() conditon, or does it have some obscenely high upper bound for the player number?
Report, edit, etc...Posted by DemonicDragon on 2006-11-20 at 01:53:50
Wait... we might be able to get our EUDs back through Set Resources?
Score!
Score!
Report, edit, etc...Posted by spinesheath on 2006-11-20 at 05:34:44
doubt that. Blizzard is not that stupid, they probably fixed all the functions that allowed writing where you shouldn't.
Report, edit, etc...Posted by Corbo(MM) on 2006-11-20 at 12:24:38
So... how do I enable cheats again?
Report, edit, etc...Posted by Tuxedo Templar on 2006-11-20 at 13:30:57
QUOTE(SomeIdiotNerd @ Nov 18 2006, 12:58 PM)
well, Tux used a very good method for his, try checking out his unprotected Rush on his site...
[right][snapback]591047[/snapback][/right]
[right][snapback]591047[/snapback][/right]
I didn't use EUDs for Rush.
Report, edit, etc...Posted by spinesheath on 2006-11-20 at 13:44:27
I guess he referred to your "cheat codes" that were selected at the beginning with the overlord and A/B/C/D...
Report, edit, etc...Posted by Heimdal on 2006-11-20 at 18:54:02
QUOTE(DT_Battlekruser @ Nov 19 2006, 10:01 PM)
Wait, how do you go so far into the memory with a Resources() conditon, or does it have some obscenely high upper bound for the player number?
[right][snapback]591871[/snapback][/right]
Yeah, the player index is a 4-byte long.[right][snapback]591871[/snapback][/right]
QUOTE(DemonicDragon @ Nov 20 2006, 01:53 AM)
Wait... we might be able to get our EUDs back through Set Resources?
Score!
[right][snapback]591972[/snapback][/right]
Nope. As of the current version, SetResources is guarded just like SetDeaths. I haven't looked at 1.13a recently, but SetResources might have worked in that version.Score!
[right][snapback]591972[/snapback][/right]
Report, edit, etc...Posted by Corbo(MM) on 2006-11-26 at 21:51:21
What about Text detection? Can anyone guide me through it?