A Disabled Unit Sprite Goliath?

He mentioned All sprite-units, not disabled ones.

Man this is fantastic!
I haven't looked into many of the EUD triggers, had no idea this was possible!

Next storm the fort version will hopefully use this for vehicle enter/exit

Its not shared memory so it can't be used in multiplayer for any actions that effect gameplay. Actions that don't effect gameplay would be display text or leaderboards or something.

Awsome map , thnx

This map has an error that prevented the Numpad + key from being read correctly. The memory address should read 16777216 instead of 65536. I have attached a fixed version of the map below.



Attachments:

Nobody cared to figure out why the mouse buttons weren't working on the map.

I started some research into this. It is possible to detect mouse presses when you read the right address, but every time I re-initialize SC, the address is changed. However, if you edit the map without re-initializing SC, then you can put in the correct memory address and detect that the key is being pressed.

I've compiled a list of ten addresses for mouse's right click.



I've already separated out the pattern. They seem to always be allocated to an address ending in 09EC. What this means I have no idea since I'm not a programmer.

Those are all dynamic memory addresses and are not going to be stable per instance and per machine and per map. It's the same problem we run into when trying to detect hacks.

Attempting to check all these addresses will lead to false positives or the game crashing (if the memory has not been allocated before we check the address). While I appreciate the research, this doesn't give us anything to work with.

Addresses should start at 0x00401000 or 0x150?????

Addresses should be between 0x401000 and 0x6DD694.

0x150xxxxx addresses are in storm, and are pretty reliable (but I've been told not necessarily so, but I've never seen a time when they weren't).