This topic:This is the official topic of the accomplishments with triggers of god. Many communities and users are complaining they can’t find any information about this technique, and I don't blame them. So, below, please post LINKS to lists of information, being descriptive of what they are. PLEASE post maps and screenshots whenever possible.
DON'T ask questions. DON'T post hypothetical things. This is for the facts. Refer to the 40 page topic for whatever your questions may be. Be very descriptive on how to do everything, and I'll slowly add it to this topic. THANK YOU!
------------------------------------------------------------
Introduction:All programs use RAM (Random Access Memory) to store information that they can quickly call up. Each piece of data can be organized in any way, is called quickly, and is declared in programming as "Variables". Starcraft uses "Variables" to store just about every piece of dynamic data (meaning, data that can change from game to game or from one second in time to the next). Your memory is constantly changing, even now as you are reading this.
What are Triggers of God? They are also known as "Extended Unit Death triggers" (short form EUD).
It was a glitch discovered by
Deathknight which Starcraft accidentally takes triggers with memory values inputted by changing certain Starforge settings and allowing it to execute viewing and modification of memory locations.
Thus far, the technique seems restricted to map memory only, and it is thus far not considered for this method to be a way of transferring viruses or messing up your computer. The worst it can do, is crash starcraft. Since this technique only applies to MEMORY, it writes all variables back into memory upon starting starcraft again. In short, it currently isn't known to do any damage. Blizzard has been made aware of this technique, and they will likely be investigating it.
It is a revolution of map making, because it allows mod-like actions to be taken, whenever you want in the map. It is all dynamic, which means these things can be changed whenever the map maker wants. The real challenge, is finding new ways to add creativity and innovation into our maps by identifying memory values and modifying them to make different events and changes occur in our maps.
However, Mac users will instantly crash upon attempting to play these maps. We forsee that this may not be a problem, as this technique is somewhat complex and not all mappers will use it. Although, we still ask that you include a warning in one of your force names or mission breifing, that they will crash upon playing the map.
------------------------------------------------------------
Currently Known Capabilities:• Modify any aspect of Units.dat(Max unit HP, unit weapon, supply used, size, attributes, etc.)
• Modify any aspect of Weapons.dat(Weapon cooldown rate, weapon splash damage, alter spells, weapon graphics, weapon range, etc.)
• Modify any aspect of Techdata.dat(Label/Icon, Time/Mineral/Gas/Energy costs, etc.)
• Modify any aspect of Upgrades.dat(Label/Icon, Time/Mineral/Gas Costs, Time/Mineral/Gas Factors, etc.)
• Modify any aspect of orders.dat(Order emulated, whatever unknowns are in there, etc.)
• Modify any aspect of flingy.dat(Sprite, speed, turn style, acceleration, turn radius, etc.)
• Modify any aspect of images.dat(Palette, IScript pointer, etc.)
• Modify any aspect of sprites.dat(Images pointer, HP Bar length, Selection circle graphic, etc.)
• Modify Players' Technology availability, technologies researched, upgrades max, current upgrades.
• Modify Location sizes, move locations based on pixels, and modify location flags.
• Modify specific units' HP values, shield values, energy values, owner, attributes, unit type, etc.
• Move sprites.
• Change line colours.
• Change player names.
• Make triggers state a player's name.
• Detect specific unit HP amount, shield amount, status, etc.
• Force orders on units.
• Change unit names(make them move while having the unit selected--flashyO_O).
• Enable/Disable cheat codes in multiplayer.
• Detect number of pauses a player has left.
• Change map unit boundary.
• Change game speed.
------------------------------------------------------------
Links to useful places:Tutorial on EUDsA nice read on all about memory and EUD stuff. Don't read it unless you got an IQ of over 110 and a good attention span. It's meant for the more intellectual map makers.
Memory CalculatorOnce again, you'll have to have a big attention span and a lot of time on your hands to figure out how to use this in your maps. A very useful tool for finding out memory locations of unit data.
------------------------------------------------------------
Example Maps:Here are some examples of the EUD triggers already in use. Download them and try them. They are not mods, and they do not require other executables. They act like mods, but are modded by triggers. Enjoy.
Interceptor Warz (alpha)An example madness map where Jim Raynors are flying, cloaked, and detector. Extremely good example.
Example Defense MapA quick defense map to play with your friends using EUDs.
------------------------------------------------------------
What is coming:As map makers further expose this glitch for creative means, programs are already underway to make these triggers far easier to use. If you don't understand a blessed word any of the hardcore map makers are talking about, don't worry, as easier to understand programs will be released soon. Stay tuned on the Staredit Network news page, as you will hear about it there first.