1. How do you use plugins with Firegraft? I can add it to the list but I don't know how to use it.

2. Making normally uncloakable units cloak: the Cloakable box in their dat entry is checked, the dat requirement for cloaking has been modified to allow them, they have enough energy, but I still can't cloak them. EDIT: DoA said the exe edit is broken.

3. Explosion grps change color when opened in GRP editors. When put into the mpq and run, they still have the weird colors (DA death to be specific). Any way to fix that? I figured it out. I replaced fusion cutter hit with DA death, but forgot to set the palette of the fusion cutter to ofire. DONE

4. I switched around everything for the vulture and firebat, but when I build them they have the other's icon (while building). Can you switch those around too? DONE

Post has been edited 4 time(s), last time on Jan 10 2009, 3:43 am by ForTheSwarm.

1) Which plugin? Different plugins are used in different ways.
2) Not fully sure, but i think there is an EXE edit to allow other units then the originals to cloak
3) Are you using the correct palette? You need to use the special palettes for explosions, which have been converted to normal palettes for editing by FaRTy (they can be found in the PalPack by FaRTy, or they come with PyMS in the Palettes folder)
4) There are three GRP's for wireframes, one for selecting the unit individually, one for when the unit is selected in groups, and one for when they are in transports, one of those holds the wireframe you want to change.

1. LocUnlock. I have the triggers in the .mpq, just need to use LocUnlock.

2. I'm not really sure what to do with that .exe edit.

3. None of them seem quite right. The closest one is ofire. Is that it?

4. I already changed wireframes. I'm talking about the icon that appears when a unit is building.

1) Just load LocUnlock as an MPQDraft plugin and compile your EXE. All you have to do after that is make the correct triggers. If you have more specific questions I'll be glad to answer.
2) Not fully sure either. Enable all or some of the entries about Personnel Cloaking
3) Im pretty sure its ofire for terran and bfire for protoss. What GRP are you viewing, what grp editor/viewer are you using, and what does it look like if its not correct?
4) Ah read the question wrong. I don't remember were these are stored.

1. I thought Firegraft and MPQDraft were incompatible...

2. I enabled all, it doesn't work.

3. Dark Archon death, I tried PyGRP and RetroGRP, it looks either green or blue when it's not correct.

1) The EXE's they create are not compatible, but FireGraft has support for MPQDraft plugins (thats why on the plugin tab it has an MPQDraft plugin list)
2) Well i guess you gotta wait for someone that has done it before
3) Viewing it in PyGRP with ofire palette works fine for me?

1. Well it doesn't seem to be working for me. It's added to the list but none of the triggers (they use "Anywhere") seem to fire.
3. When added to the .mpq and used it still looks funky.

4. they are in cmdbtns.grp i think, i would just save copy the firebat to vulture and vulture to firebat.

1) What triggers are you using. I found some conditions/actions might not work outside of UMS
3) Whats funky about it? And maybe post up to GRP?

Attached is the .trg file. Strangely, it PyTRG kept converting "set shields to 100%" into "set shields to 0%".

3. It's off-color. The .grp is directly extracted from the broodat.mpq.

Post has been edited 1 time(s), last time on Jan 9 2009, 10:31 pm by ForTheSwarm.

Try putting the EnableDebugMode() in the same trigger as the SetResources(), then to make sure its working create a unit at Anywhere to see if the location actually moved. So:

If thats working either your triggers arn't firing or you are out of luck and modifiying unit stats doesn't work outside of UMS To test if they are firing just create units at Anywhere and see if they are firing or not.

3) So you extract it, then place it in the MPQ without editing it, and its still off? Are you sure the images.dat entry hasn't been changed to a different palette or something?

Note: The PyTRG putting the 100% to 0% has been fixed (and it is compiled correctly, it only makes them 0% when it decompiles them)

2. Dont enable all. I dont think it makes sense to make both personnel and cloaking field the default (2 defaults). Pick either personnel cloaking or cloaking field. For example, enable Is Cloaked Requirement - Use Personnel Cloaking. If you have EXE edit linking on (default is on, there is a checkbox on EXE edit screen that lets u pick), all personnel cloaking ones should now be enabled.

3. Dark Archon death is ofire...Look at the images entry in DatEdit.

2. Didn't work.

3. Image.dat has not been touched.

The unit was not created.

Let me get this straight:
You add the plugin as a MPQDraft plugin under the plugin tab of Firegraft. You save, and that's it?

2. Well, Im just going off of what the EXE edits say. Ask DoA about them. I never had the need to enable cloaking on anything.

Yes, add as MPQDraft plugin.