Report, edit, etc...Posted by TheNomad on 2006-12-07 at 14:34:42
Err... correctumondo...
SF, is there a way to reallign the sfxdata table in Ice IDE ? This is a bit confusing if left like this
Maybe -1 should be considered None (since neg numbers can't be compiled by the IceCC compiler and it'd be silly do do PlaySnd 0 aka PlaySound(Null) 
)
SF, is there a way to reallign the sfxdata table in Ice IDE ? This is a bit confusing if left like this
Maybe -1 should be considered None (since neg numbers can't be compiled by the IceCC compiler and it'd be silly do do PlaySnd 0 aka PlaySound(Null) )Report, edit, etc...Posted by BroodKiller on 2006-12-07 at 15:31:12
Hmm...having reflected about the "Missile" property, I come to a conclusion that it should be called "Death","Termination","End" or something like this because that's what I think it is about:
-'Homing' means "Die on hit"
-'Normal' means "Die on max. range"
-'Bouncing' means "Die on 3rd hit"
I have doubts only about my interpretation of "Bouncing", and I think some Iscript testing should be done to verify it, but the others are pretty much straightforward and I think they are ok?
ADDITION:
I think that the "Flies to Target" and "Seeks Target" behaviours would be better described as "Static Lock-on" and "Dynamic Lock-on", with description in the hint, what do everyone think?
-'Homing' means "Die on hit"
-'Normal' means "Die on max. range"
-'Bouncing' means "Die on 3rd hit"
I have doubts only about my interpretation of "Bouncing", and I think some Iscript testing should be done to verify it, but the others are pretty much straightforward and I think they are ok?
ADDITION:
I think that the "Flies to Target" and "Seeks Target" behaviours would be better described as "Static Lock-on" and "Dynamic Lock-on", with description in the hint, what do everyone think?
Report, edit, etc...Posted by DiscipleOfAdun on 2006-12-07 at 15:35:32
It's only 3 hits because the exe tell it that it is 3. 
Report, edit, etc...Posted by BroodKiller on 2006-12-07 at 18:07:10
QUOTE(DiscipleOfAdun @ Dec 7 2006, 10:35 PM)
It's only 3 hits because the exe tell it that it is 3.
[right][snapback]600808[/snapback][/right]
[right][snapback]600808[/snapback][/right]
Yeah, right. It should be "Die on last hit" then
u nerd
Report, edit, etc...Posted by Ojan on 2006-12-07 at 18:11:04
Will FG be able to edit this? :D
Report, edit, etc...Posted by BroodKiller on 2006-12-08 at 04:21:55
Don't ask...do you really want to know the answer before THE day?
ADDITION:
Hmm...The "Bouncing" Missile option is not "Die on 3rd/last hit". I tested it and Glave Wurm run its death animation on the last hit no matter which option I set here (I added a sprol to its death aniamation to see when it occured).Anyone, ideas? We know what this property may be about, let's finish it off
ADDITION:
Here's the new version of the Weapon Behaviours list (with the old names as well, for reference)
Flies to target - Fly to Target(Don't Follow)
Seeks Target - Fly to Target(Follow)
Appears on Target - Appear on Target Unit
Psionic Storm - Psionic Storm
Persistant Explosion - Appear on Target Site
Normal hit - Appear on Attacker
Suicide - Attack & Self-Destruct
Bounce - Bounce
Halo (Spin) - Attack Target 3x3 Site(Follow)
Go to Max. Range - Go to Max. Range
Comments, other ideas?
ADDITION:
Hmm...The "Bouncing" Missile option is not "Die on 3rd/last hit". I tested it and Glave Wurm run its death animation on the last hit no matter which option I set here (I added a sprol to its death aniamation to see when it occured).Anyone, ideas? We know what this property may be about, let's finish it off
ADDITION:
Here's the new version of the Weapon Behaviours list (with the old names as well, for reference)
Flies to target - Fly to Target(Don't Follow)
Seeks Target - Fly to Target(Follow)
Appears on Target - Appear on Target Unit
Psionic Storm - Psionic Storm
Persistant Explosion - Appear on Target Site
Normal hit - Appear on Attacker
Suicide - Attack & Self-Destruct
Bounce - Bounce
Halo (Spin) - Attack Target 3x3 Site(Follow)
Go to Max. Range - Go to Max. Range
Comments, other ideas?
Report, edit, etc...Posted by DiscipleOfAdun on 2006-12-08 at 12:15:28
BK, I have something for you. Morph From Unit? has been solved. It should be called - Ignore Supply Check, or something like that. Basically, if you turn it on, it's a mini food for thought cheat on that unit. Meaning even if you don't have the supply available to build the unit, it will still build it and add that to your supply. I believe(I didn't have time to test) that it stops at 200 supply just like normal. The reason the morph units have it selected is because they don't take up more supply, but they have a supply cost equal to the existing one. There's something up with lurkers when you check it too, but I didn't have time to decode the asm for that one either.
Also, the Single Entity or whatever you are calling it is also the flag that is checked by SG/MG/FG on the Is Powerup opcode. Just so you know.
Yay for me, I can still solve these things.
Report, edit, etc...Posted by BroodKiller on 2006-12-08 at 13:25:16
Yay, another cool find, and it works!
Good job DoA
Good job DoA
Report, edit, etc...Posted by Voyager7456(MM) on 2006-12-08 at 14:13:36
Great find DoA... this explains some of the weird behavior I was getting with morphs...
Report, edit, etc...Posted by BroodKiller on 2006-12-08 at 14:48:34
QUOTE(DiscipleOfAdun @ Dec 8 2006, 07:15 PM)
Also, the Single Entity or whatever you are calling it is also the flag that is checked by SG/MG/FG on the Is Powerup opcode. Just so you know.
[right][snapback]601174[/snapback][/right]
This is understandable, given the fact that you cannot select multiple powerups at once.
Report, edit, etc...Posted by TheNomad on 2006-12-08 at 15:05:39
Nice job on that, DoA 
Hmm... didn't think of checking the supply
Hmm... didn't think of checking the supply
Report, edit, etc...Posted by DiscipleOfAdun on 2006-12-08 at 15:14:37
I don't blame you. I was lucky enough to find that it was actually used. The only reason I knew to even consider supply was that I saw it being checked in the button actions.
BTW, BK, I was driven crazy this morning trying to figure out the bit that I needed to search for to check that value, since DatEdit doesn't order the Adv check boxes like A3 did. Just so you know. Eh, it's not like I wasn't able to open the source to figure it out though....
BTW, BK, I was driven crazy this morning trying to figure out the bit that I needed to search for to check that value, since DatEdit doesn't order the Adv check boxes like A3 did. Just so you know.
Eh, it's not like I wasn't able to open the source to figure it out though....Report, edit, etc...Posted by BroodKiller on 2006-12-08 at 15:57:03
Well, this can be an issue of some sort, but I decided to group the flags because I think the users have the functionality in mind rather than staying true to the format. Also, if someone is looking for a particular bit for some purpose, then he definitely know what code means and can look for it himself, as you did
This reminds me however that I need to put up the updated DAT specs.
This reminds me however that I need to put up the updated DAT specs.
Report, edit, etc...Posted by TheNomad on 2006-12-08 at 16:03:32
Well, Subunit is kinda close to Detector and once I misclicked it resulting in a crash
I guess the ideal way would be to have an options dialogue (or INI entries) specifying which checkbox goes in what pos But I am not making hints, just making a comment... DatEd is fine as it is, but maybe lesser used stuff (like Subunit) should go to the end.
I guess the ideal way would be to have an options dialogue (or INI entries) specifying which checkbox goes in what pos
But I am not making hints, just making a comment... DatEd is fine as it is, but maybe lesser used stuff (like Subunit) should go to the end.Report, edit, etc...Posted by BroodKiller on 2006-12-08 at 16:21:21
To be honest, this was also an idea at some point (from PCM I think) - to make the GUI customizable through an INI interface or something like this. I don't oppose, but I can't see an usefulnes in this, really.
Report, edit, etc...Posted by fatimid08 on 2006-12-08 at 16:36:58
QUOTE(BroodKiller)
This reminds me however that I need to put up the updated DAT specs.
That would be greatly appreciated, at least by me and at least one person that I know of. It seems that the old camsys ones are now very outdated by what I can see by looking at DatEdit itself. Making specs from your source is easy enough, but it seems that a lot has changed since the 1.3 release, and looking through a lot of pages of forum, old spec sheets, and source code, AND comparing it all to see what goes where and what has to be modified is somewhat more work than what your work will be making the spec files.
Making spec files isn't long, I've updated the terrain specs myself, took me 15-20 minutes to add a lot more descriptiveness on the link between different files and on how it all works. (Posted on BlizzForums)
QUOTE(BroodKiller)
then he definitely know what code means and can look for it himself, as you did
But do you really want to browse code with Notepad (for those who have no editor) or with some IDE just to look for some code that you have to write the actual part of spec you need after finding it? Especially that the offsets and names are in two separate files in your source.
Report, edit, etc...Posted by TheNomad on 2006-12-08 at 17:24:53
QUOTE(BroodKiller @ Dec 9 2006, 12:21 AM)
To be honest, this was also an idea at some point (from PCM I think) - to make the GUI customizable through an INI interface or something like this. I don't oppose, but I can't see an usefulnes in this, really.
[right][snapback]601229[/snapback][/right]
[right][snapback]601229[/snapback][/right]
Let's say I only adjust flag A, B, C, D, and X and I want those to be on the first column... ok dumb example, but you get the idea
I am not all for it, if it gets added, I'd love it, otherwise, I'm not against it....
I can already see flaming posts saying the method sux because someone put the same slot for 2 flags... still, the uses are quite limitless. TBH I'd rather have postionable flags than sorting by trees. I mean I am not calling sorting by origin useless (so no attacks pls
), just saying I, for one, would rather customize the flag positions than use trees to navigate through items, that's all Sort of like, "just add it, and leave the usefulness to us"
still, as I said, I don't have a problem with how they are set up now (as long as Subunit gets a bit more obscurity, maybe to the same pos but on the second column, since I'm pretty sure people would rather make the zealot a miner or to require creep or to make the zealot burrowable than to make a new tank ).Report, edit, etc...Posted by DiscipleOfAdun on 2006-12-08 at 22:22:44
Heh, if it really bothers me, I'll just get the source and make my own customized version. That's the beauty of open source.
That's the beauty of open source. Report, edit, etc...Posted by BroodKiller on 2006-12-09 at 05:11:19
##########DATEDIT v1.4 UPDATE##########
I originally thought this would be just a small fixup, but in the end it turned out that I put in more than I expected so I decided it to be a full-fledged update. Many thanks for what is in this release flies to DiscipleOfAdun and TheNomad - your help is invaluable guys! Still, not much hapennig here, simply carry on
Fixed/Changed:
-The "Restricts" property renamed to "Unknown"
-The "Floats(?) property renamed to "Draw If Cloaked"
-The "Missile" property renamed to "Projectile"
-The "Shadow Turns" property renamed to "Clickable"
-The "Morph from other unit(?)" flag renamed to "Ignore Supply Check"
-The "Placeable" StarEdit Availability flag renamed to "Listing & Palette"
-The "Owned" StarEdit Availability flag renamed to "Non-Neutral"
-The "Part of Terrain" StarEdit Availability flag renamed to "Set Doodad State"
-The "Unit (Men)" flag renamed to "Men"
-The Units Editor Sound subtab "Start" properties names changed to "First", and "End" to "Last"
-The "Owned" weapon targeting flag renamed to "Own"
-The "Missile" property renamed to "Follow", and its items:"Homing" to "Within range", "Normal" to "Until hit", "Bouncing" to "Bounce(?) (this one needs further examination)
-The "Behaviour" property items renamed to:
Flies to target - Fly to Target(Don't Follow)
Seeks Target - Fly to Target(Follow)
Appears on Target - Appear on Target Unit
Persistant Explosion - Appear on Target Site
Normal hit - Appear on Attacker
Suicide - Attack & Self-Destruct
Bounce - Bounce(Follow)
Halo (Spin) - Attack Target 3x3 Area
-The "Group(?)" property renamed to "Highlight"
-Changed the layout of the Orders Editor, put all but the flags into one panel (there are no 'options' in orders.dat but the flags)
-The unused bytes from the "StarEdit Availability" flagset are back in the editor.With Firegraft coming, some people may find them of use, hence you can see them again.
-Fixed the "Player Settings" StarEdit flag hint problem
-Fixed the update problem with the "Shield Gfx" property
-Fixed several TAB order issues
-Fixed a bug in the Tech and Upgrade Editors' with the "Label" property, hapenning if you input an ID larger than the number of strings in the list. It now gives the "no item" list selection properly
-Fixed the "click-and-run" issue with the flagset-type properties
-Fixed a bug that will not display the correct entry data in editors other than the Units Editor with the "Sort by Origin" view selected.
-Updated the orders.dat Iscript animations listing (IceCC v1.3 compatible)
-Updated several hints
-Now allowed loading DAT and MPQ files via a command-line parameter
-Now using v1.11 of the ShadowFlare's GRPAPI
New in v1.4:
-DAT Association
Added "Associate DATs" button to the Options screen. It associates the ".dat" extension to the currently running DatEdit executable, and allows for files to be loaded into DatEd by double-clicking on them.
-Drag-and-Drop
You can now drop DAT and MPQ files onto the DatEdit window to load them into the program, yay!
-Multiple-entry Selection
Yup, you heard the man:) From now you can select multiple entries in DatEd and set their properties simultaneously. Both the CTRL- and SHIFT-aided selection works fine. This feature is still experimental so it has a few restrictions on it:(READ PLEASE)
#1-It works only when using the "Sort by ID" viewing method
#2-The editor will show only the last-selected entry's data
#3-There is no feedback about the variety of the properties amongst the selected entries (yet?)
Download:
http://www.staredit.net/index.php?download=4668
Source:
http://www.staredit.net/index.php?download=4978
As usual - any feedback and reports are most welcome
-Uncle Broody
PS:I am leaving for a couple of days, so I won't be able to respond.
I originally thought this would be just a small fixup, but in the end it turned out that I put in more than I expected so I decided it to be a full-fledged update. Many thanks for what is in this release flies to DiscipleOfAdun and TheNomad - your help is invaluable guys! Still, not much hapennig here, simply carry on
Fixed/Changed:
-The "Restricts" property renamed to "Unknown"
-The "Floats(?) property renamed to "Draw If Cloaked"
-The "Missile" property renamed to "Projectile"
-The "Shadow Turns" property renamed to "Clickable"
-The "Morph from other unit(?)" flag renamed to "Ignore Supply Check"
-The "Placeable" StarEdit Availability flag renamed to "Listing & Palette"
-The "Owned" StarEdit Availability flag renamed to "Non-Neutral"
-The "Part of Terrain" StarEdit Availability flag renamed to "Set Doodad State"
-The "Unit (Men)" flag renamed to "Men"
-The Units Editor Sound subtab "Start" properties names changed to "First", and "End" to "Last"
-The "Owned" weapon targeting flag renamed to "Own"
-The "Missile" property renamed to "Follow", and its items:"Homing" to "Within range", "Normal" to "Until hit", "Bouncing" to "Bounce(?) (this one needs further examination)
-The "Behaviour" property items renamed to:
Flies to target - Fly to Target(Don't Follow)
Seeks Target - Fly to Target(Follow)
Appears on Target - Appear on Target Unit
Persistant Explosion - Appear on Target Site
Normal hit - Appear on Attacker
Suicide - Attack & Self-Destruct
Bounce - Bounce(Follow)
Halo (Spin) - Attack Target 3x3 Area
-The "Group(?)" property renamed to "Highlight"
-Changed the layout of the Orders Editor, put all but the flags into one panel (there are no 'options' in orders.dat but the flags
)-The unused bytes from the "StarEdit Availability" flagset are back in the editor.With Firegraft coming, some people may find them of use, hence you can see them again.
-Fixed the "Player Settings" StarEdit flag hint problem
-Fixed the update problem with the "Shield Gfx" property
-Fixed several TAB order issues
-Fixed a bug in the Tech and Upgrade Editors' with the "Label" property, hapenning if you input an ID larger than the number of strings in the list. It now gives the "no item" list selection properly
-Fixed the "click-and-run" issue with the flagset-type properties
-Fixed a bug that will not display the correct entry data in editors other than the Units Editor with the "Sort by Origin" view selected.
-Updated the orders.dat Iscript animations listing (IceCC v1.3 compatible)
-Updated several hints
-Now allowed loading DAT and MPQ files via a command-line parameter
-Now using v1.11 of the ShadowFlare's GRPAPI
New in v1.4:
-DAT Association
Added "Associate DATs" button to the Options screen. It associates the ".dat" extension to the currently running DatEdit executable, and allows for files to be loaded into DatEd by double-clicking on them.
-Drag-and-Drop
You can now drop DAT and MPQ files onto the DatEdit window to load them into the program, yay!
-Multiple-entry Selection
Yup, you heard the man:) From now you can select multiple entries in DatEd and set their properties simultaneously. Both the CTRL- and SHIFT-aided selection works fine. This feature is still experimental so it has a few restrictions on it:(READ PLEASE)
#1-It works only when using the "Sort by ID" viewing method
#2-The editor will show only the last-selected entry's data
#3-There is no feedback about the variety of the properties amongst the selected entries (yet?)
Download:
http://www.staredit.net/index.php?download=4668
Source:
http://www.staredit.net/index.php?download=4978
As usual - any feedback and reports are most welcome
-Uncle Broody
PS:I am leaving for a couple of days, so I won't be able to respond.
Report, edit, etc...Posted by Kookster on 2006-12-09 at 05:39:42
Glitch Report:
If you load up a mpq, then try to load a directory Datedit freezes(in that order)
If you ever check any of the properties under the units tab in the sub tab advanced in other properties, you will not be able to uncheck them again!!
Thats all Ive found so far hopefully I wont find anything else.
If you load up a mpq, then try to load a directory Datedit freezes(in that order)
If you ever check any of the properties under the units tab in the sub tab advanced in other properties, you will not be able to uncheck them again!!
Thats all Ive found so far hopefully I wont find anything else.
Report, edit, etc...Posted by BroodKiller on 2006-12-09 at 06:23:12
Thanks Kooks, fixed it (it was because of a terrible and stupid typo I made). I also added an info on succesful DAT association. I don't change the version since it's just minor things.
I don't know about that freezeing problem however - I don't have it and I can't repeat it.Would you mind to say precisely what files do you have in the MPQ and the step-by-step reproduction of this error?
I don't know about that freezeing problem however - I don't have it and I can't repeat it.Would you mind to say precisely what files do you have in the MPQ and the step-by-step reproduction of this error?
Report, edit, etc...Posted by Kookster on 2006-12-09 at 06:56:56
Honestly that bug isnt so important, but Ill see what I can do. It happens when ever I open my mpq, then open my folder, same files everytime.
The Mpq contains: orders.dat, techdata.dat, upgrades.dat, images.dat, sprites.dat, flingy.dat, weapons.dat, units.dat, cmdicons.grp, stat_txt.tbl.
The Folder contains: units.dat, weapons.dat, flingy.dat, sprites.dat, images.dat, upgrades.dat, techdata.dat, orders.dat.
Those are the order in which the pop up lists them.
Ok I reproduced the freeze and found when I removed my custom stat_txt.tbl that it would work just fine. So maby you could just make it so it doesnt load stat_txt.tbl from mpq's????
So did you upload those changes????
The Mpq contains: orders.dat, techdata.dat, upgrades.dat, images.dat, sprites.dat, flingy.dat, weapons.dat, units.dat, cmdicons.grp, stat_txt.tbl.
The Folder contains: units.dat, weapons.dat, flingy.dat, sprites.dat, images.dat, upgrades.dat, techdata.dat, orders.dat.
Those are the order in which the pop up lists them.
Ok I reproduced the freeze and found when I removed my custom stat_txt.tbl that it would work just fine. So maby you could just make it so it doesnt load stat_txt.tbl from mpq's????
So did you upload those changes????
Report, edit, etc...Posted by BroodKiller on 2006-12-09 at 07:34:37
Yeah, I uploaded the quick fix already (for the "Other" flags and the infobox on association)
ADDITION:
Hmm...if it's your stat_txt that causes the freeze, it may be that it is corrupted. DatEd its very fragile in this regard, and even if TBLPad is ok with it, it won't. Have you checked it?
ADDITION:
Hmm...if it's your stat_txt that causes the freeze, it may be that it is corrupted. DatEd its very fragile in this regard, and even if TBLPad is ok with it, it won't. Have you checked it?
Report, edit, etc...Posted by Kookster on 2006-12-09 at 07:40:11
o my tbl is fine, its just that it has more lines new stuff added into it. If I recall correctly Datedit doesnt like that when you were talking about importing custom tbl's
Report, edit, etc...Posted by BroodKiller on 2006-12-09 at 07:44:27
Well, if the entry table at the beginning of the file is OK, then DatEd should handle it just fine. Could you PM me the mpq, so I can look at the issue myself?