Staredit Network

hmm

If you can come up with a better one, but still short and informative, then please do. Seriously, no irony here.

Reference properties - whatever. I like them as they are, and the fact that they don't do anything doesn't mean all of the sudden that we're right in our assumptions of them being actually just designer's hints.

Splitting the Orders tab - forget it. Too much in DatEdit depend on the currently selected tab's ID. Moreover, I don't like the idea and evenmoreover- I do not do things for one person's request.No offense, but there are different people using DatEd, and I want to keep it as versatile as possible, without fitting it into one person's (or even a few persons') needs without a good reason for it.

Reaload Tab - I considered doing this, but eventually I did not, the reason being - YOU ARE SO LAZY!!!!!


I must admit that with this release, DatEd is pretty much complete in my eyes. Only some serious events will make me do another update to it. Apart from that, there are other modding areas that await 'fresh blood', right?

hmm... maybe "It is related to rendering exceptions, for example if unchecked on a unit, it will not be drawn at all when cloaked, but will have overlays of effects and spells" and if you want, you can add a classic "not completely understood" at the end I also recommend renaming it as "floats" is ... well weird Considering the effect it has in-game. Maybe rename to something like "Rendering handling" or "Drawing exception" or maybe even simpler, "Draw if cloaked"


Actually, DoA kinda confirmed that some of them are used by the code internally and don't have any easy-to-see in-game results to me some time ago. He said he doesn't remember which for sure, but I am stalking him to give him my notes and maybe we can get to the bottom of them


None taken. I just thought it'd be easier for a lot of people since more than half of the orders there are more confusing than explanatory, and some might not even tell the difference between "Initialize Arbiter" and "Cloak nearby units" (to those that don't, Init Arbiter is the actual "Cloak nearby units" behavior, while the mislabeled "cloak nearby units" (maybe mislabeled is harsh) is the script itself that handles the fun stuff). This wasn't just for me, but as I said, modifying scripts could make modding even better since all I see on 34857874697 sites are "download my mod, among other things, marines have shields" (which is as original as giving every terran unit shields, double damage and 99999 hp with all abilities researched) and no other new features. Come to think of it, I can think of a few additions (that might even improve unit AI) just by editing the Unit tabs, including the AI scripts. And although I (and a few others) know which is a script, which is an order and which is a behavior, most have no clue and to me it seems to kinda limit modding. As for complicating it, I admit it is a bit ... (maybe more ) complicating it, but on the long run, it might be a hell of a lot easier for some. Or at least that is what I think
And to make things more attractive for some, it might also help some know where to look for things (e.g. which one of the many Build orders is for a nydus canal, which is for Protoss buildings, which is for Healing units normally etc.) and modify some stuff. And to show off, I made the vulture plant marines instead of mines (yes the marines work normally and can move and attack and stim ). OK, you gotta admit THAT is original


ROFL... touché


Agreed

For floats, I would've just said "Draw if cloaked" or "draw when cloaked" personally like TheNomad said, that's how I understand it.

The overlays appearing and not appearing seem like a separate thing to me, since they've got their own "draw if cloaked" checkbox, so I don't think that needs to be mentioned. I think "draw if cloaked" sums it up completely.

I agree. I havent found any other behaviors to it. And floats doesnt describe it.

But the overlays are important imo. Imagine creating a new unit by sacrificing, say the ursadon, adding shadows, overlays etc etc and then realising the shadows and effects don't appear. The reason is because they can't be rendered due to this flag's behavior.

But true, "Draw if cloaked" sounds simple enough, but the description should include both cases (for units and effects).

i might think about uninstalling A3... i still think DE 1.1d is easier to use >< anyways good release, BK, YOUR MY HERO!!!

Bug found! Rather bad too.

When you click a checkbox so you get a little "selection outline", but do not actually toggle the checkbox's status, and then select another unit / editor and go back, the status of the checkbox HAS changed. This seem to apply to most Units.dat and Weapons.dat checkboxes.

Speaking about Weapons.dat checkboxes, it's called "non-Robotic" and "non-Building", unless I'm completely mistaken

[edit=1]Ojan fails.[/edit]

Continuing in orders.dat... Shouldn't the "Group (?)" really be 16 flags? I'll try to see if the property does something when I get time... If it isn't unused, perhaps it's necessary to turn it into flags... If not, it really doesn't matter

In Images.dat: The "Shield Gfx" dropdown box doesn't seem to update according to the number at all.

I still think you should add the unused StarEdit availability flags back

"Can Be Interrupted" means that the worder can't be stopped in the middle of its action to do another. As in, if you want to storm an area but tell the templar to move before he storms, he will move and ignore the storm order, while if you try to turn to a siege tank, you can't interrupt it by moving or pressing stop

Never mind... I realized that I didn't read the description as properly as I should had. Disregard what I said. I fail.

We forgive you
BK don't forget about the other bugs (sounds and units) that I posted on WB pls.

I got two things to report. One bad one well interesting.

1)When loading mpqs, for dats that are not there the corrisponding tabs will not load. So say theres no orders dat the tab wont load for it or atleast something along those lines.

2)Ok keep in mind I have found this only for spells. When tinkering with Orders.dat I found that emulate does nothing, so long as its a spell thats in it. But to change a spells function you must change the weapon that it uses for targetings explosion. And if you do not use the targeting checkbox it will appear ontop/under the caster unless previesly like that in the dat.

I think I got it all in there but I checked it several times with different types of spells for different races.

So heres an exaple.
I select Maelstrom in weapons.dat I change the explosion to lockdown, it now does lockdown. If i go into the orders dat for maelstrom and change the emulate to lockdown it doesnt change anything. If I change the targeting weapon to lockdown it does lockdown instead.

Got any questions? Please someone go confirm this time Im not mad I swear

Yeah, i asked that on WB some time ago and I think DoA told me that it doesn't do anything. I think it is a label, like the unused ones (example: the "tech" one, now labeled "unused" from weapons.dat)

Must have been someone else that told me that Emulate isn't used then. Sorry DoA
Perhaps mislabeled.

Speaking of "not doing anything", what does the "Researched" flag in the Tech tab actually do ? According to the name, logic and the hints, if it's checked, then the spell is already available, otherwise e can research it somewhere (or use a grafter to make this command). I'd say YES, except for the fact I gave it on Irradiate and removed it on DMatrix and nothing changed. Is it really used or is this yet another Blizzard label used just for reference ?

Speaking of "Label", seems the one from Orders is put there for laughs as well (according to BK).

Yeah I noticed that the researched check box does nothing too. So what I do is i just change the requirements for the spell to only the unit casting it and get rid of the research button.

Question does anyone know of anyway to edit a spell? Like I wanted to make EMP shockwave do lockdown to everything it hits from splash. Basicly making lockdown do what maelstrom does but to mechanicle stuff only.

I think the "splash" is hardcoded.

Once again I say it. All the fun stuff is in the exe darn it

IIRC the researched flag affected the defauly value for a tech in StarEdit, and not in-game...

Welcome back
So I was close

I know for a fact that "researched" has nothing to do with in-game: the exe tells it if a research is needed or not. So I think we can safely assume that it only affects Staredit.

Hmm...It's been some time since I visited this thread, and I lost track of what was hapenning - anyone mind reminding me of what needs to be updated in DatEd?

Basically everything from here and below.

I found a bug that needs to be addressed, so no sitting back and relaxing just yet - at least one more update is required :)


Please re-implement the unused StarEdit flags in units.dat :( :( :(