[color=#b5b5ff]It occurs to me that there really isn't a place for this, but whatever. I wasn't kidding about MemCalc wherever I made that offhand comment - I intend to re-develop it for EUD actions. It is written in Java (Swing) so it is platform independent, as long as your computer is running the Java Virtual Machine. Right now it probably doesn't have quite the functionality of EUDTrig, but I am designing it to be extremely portable, with all version-specific data stored in a CFG file. See the developer notes and planned features for more. You can download [url=http://www.staredit.net/?file=403]MemCalc 6 in the DLDB[/url], so feel free to beta-test and make suggestions. Hopefully I won't lag in keeping with releases, but we'll see. [b][u]Planned Releases and Features[/b][/u] [b]6.1.0[/b] - Implement a trigger editor that will read config files' list of known offsets for data values, allowing you to trigger with better efficiency than EUD trig and giving the EUD Database a permanent home as a config file. [b]6.2.0[/b] - Add a config file editor so that you don't have to know how to hex edit to make config files. [b][u]Developer Notes[/b][/u] The following is the current format of the .cfg files. They will get longer when I add offset lists to the specification. STRING (varsize) - version title DELIMITER (byte) - always 00, this marks the end of the string TABLE START (long) - eight bytes marking the start of the deaths table. Right now the lowest byte is last (numerical order), this might change. I will probably also shorten this to an int, I wasn't thinking very much when I wrote the file reader.[/color]

It occurs to me that there really isn't a place for this, but whatever.

I wasn't kidding about MemCalc wherever I made that offhand comment - I intend to re-develop it for EUD actions. It is written in Java (Swing) so it is platform independent, as long as your computer is running the Java Virtual Machine. Right now it probably doesn't have quite the functionality of EUDTrig, but I am designing it to be extremely portable, with all version-specific data stored in a CFG file. See the developer notes and planned features for more. You can download MemCalc 6 in the DLDB, so feel free to beta-test and make suggestions. Hopefully I won't lag in keeping with releases, but we'll see.

Planned Releases and Features
6.1.0 - Implement a trigger editor that will read config files' list of known offsets for data values, allowing you to trigger with better efficiency than EUD trig and giving the EUD Database a permanent home as a config file.
6.2.0 - Add a config file editor so that you don't have to know how to hex edit to make config files.

Developer Notes
The following is the current format of the .cfg files. They will get longer when I add offset lists to the specification.

STRING (varsize) - version title
DELIMITER (byte) - always 00, this marks the end of the string
TABLE START (long) - eight bytes marking the start of the deaths table. Right now the lowest byte is last (numerical order), this might change. I will probably also shorten this to an int, I wasn't thinking very much when I wrote the file reader.

You should set it up to make EUD conditions easier at the same time, while you're at it.

You should set it up to make EUD conditions easier at the same time, while you're at it.

[color=#b5b5ff]The trigger-making interface will be equally suitable to EUD Actions and Conditions. Right now memory-to-deaths correlation is also perfectly functional for both.[/color]

The trigger-making interface will be equally suitable to EUD Actions and Conditions. Right now memory-to-deaths correlation is also perfectly functional for both.

I say that you make one thats just like "Ubecalc2" Make it so that it contains a lot or most of the known conditions/actions and that its as simple as the one on the Clan (U) website. Also making a trigger would be nice. If it could also just tell you what to multiply it by, that would be swell. :p Just highlighting a bunch of zero's is quite confusing for the beginner.

I say that you make one thats just like "Ubecalc2" Make it so that it contains a lot or most of the known conditions/actions and that its as simple as the one on the Clan (U) website. Also making a trigger would be nice. If it could also just tell you what to multiply it by, that would be swell. Just highlighting a bunch of zero's is quite confusing for the beginner.

[quote][b]6.1.0[/b] - Implement a [b]trigger editor that will read config files' list of known offsets for data values[/b], allowing you to trigger with better efficiency than EUD trig and giving the EUD Database a permanent home as a config file.[/quote] [color=#b5b5ff]Yes, I was planning to auto-correct for byte offsets as well. The trigger interface will be along the lines of "check that this value (offset and len) is x".[/color]

Quote

6.1.0 - Implement a trigger editor that will read config files' list of known offsets for data values, allowing you to trigger with better efficiency than EUD trig and giving the EUD Database a permanent home as a config file.

Yes, I was planning to auto-correct for byte offsets as well. The trigger interface will be along the lines of "check that this value (offset and len) is x".

[color=#b5b5ff]6.1.0 is nearing completion; I hope to finish it by the end of the three-day weekend, subject to postponement due to sudden lapses of motivation. Currently Coded: -Load offsets of known data items from the config file -Switch between Conditions and Actions To be Done: -Write Starforge text outputs and .trg file outputs. I attached a production screenshot so you get an idea of what it looks like. The GUI is a bit cluttered, but I can't say I pride myself on interface design.[/color]

6.1.0 is nearing completion; I hope to finish it by the end of the three-day weekend, subject to postponement due to sudden lapses of motivation.

Currently Coded:
-Load offsets of known data items from the config file
-Switch between Conditions and Actions

To be Done:
-Write Starforge text outputs and .trg file outputs.

I attached a production screenshot so you get an idea of what it looks like. The GUI is a bit cluttered, but I can't say I pride myself on interface design.

I assume the editing is for older versions of SC only, correct?

I assume the editing is for older versions of SC only, correct?

Maybe we should request a new subforum "Tool Development". It could go inside the "Staredit General" section....

Maybe we should request a new subforum "Tool Development". It could go inside the "Staredit General" section....

[quote=name:Kow]I assume the editing is for older versions of SC only, correct?[/quote] [color=#b5b5ff]Correct. The config file contains a flag that specifies whether EUD Actions can be written. From the point of view of MemCalc, it doesn't really matter, because it can write EUD Actions for any version of Starcraft. They just won't actually do anything if you execute them in post-1.13a patches. [quote=name:Clokr_]Maybe we should request a new subforum "Tool Development". It could go inside the "Staredit General" section....[/quote] That's probably a good idea.[/color]

Quote from Kow

I assume the editing is for older versions of SC only, correct?

Correct. The config file contains a flag that specifies whether EUD Actions can be written. From the point of view of MemCalc, it doesn't really matter, because it can write EUD Actions for any version of Starcraft. They just won't actually do anything if you execute them in post-1.13a patches.

Quote from Clokr_

Maybe we should request a new subforum "Tool Development". It could go inside the "Staredit General" section....

That's probably a good idea.

So is this like the same as EUDTrig? But with some offset pre-loaded?

So is this like the same as EUDTrig? But with some offset pre-loaded?