Campaign Creations

For the first, the error window originally popped up because of left over debug output from right clicking, pressing contact however was bugged. Both those have been fixed, thanks!
For the preview bug, that was a bug choosing special palettes, this has been fixed as well, thanks again!

So far you are the only one that downloaded it so just redownload and it never happened

My next project for PyMS:
[imgwh 563x321]http://i40.tinypic.com/juv5dx.png[/imgwh]

If you didn't notice it is based heavily on HawTiles by FaRTy1billion (layout/labels).

Also, i was wondering if i could get a sticky?

Consider it done.

Thanks a lot!

The TileEditor is looking awesome! =oD

---

Problem 1: In PyDAT, default Units.dat, all units have the Independent Group Flag checked.

Problem 2: In PyDAT, default Weapons.dat, all weapons show as the Independent Type. If you select the dropbox, Normal is highlighted, and without selecting anything, just clicking elsewhere, it becomes normal. Browsing through all other weapons also shows them to be normal. Closing and reopening PyDAT shows all weapons as Independent again.

Problem 3: If I open PyTBL, and then, without doing anything, try to close it, I get an error message.
Clicking OK, PyTBL remains open. Trying to close again results in the same error, making the program unquitable.

---

Idea 1: In PyDAT, Units.dat, having a preview window for the Placement box, like how we're able to preview Unit Dimensions.

Idea 2: In PyDAT, Weapons.dat, having a preview window for the Splash Radius. Three differently colored circles overlayed on something like a Marine or somesuch.

Idea 3: In PyDAT, Weapons.dat, having a Seconds output for the Cooldown, like the one for Build Time in Units.dat.

Idea 4: In PyDAT, Flingy.dat, having an acceleration/top speed simulation window. Might be overly complicated, though.

Idea 5: In PyDAT, Flingy.dat, having a Pixels output box for Halt Distance, and an output box for the Top Speed equation.

Idea 6: In PyDAT, Sfxdata, having a Sound Preview button.

Idea 7: In PyDAT, Portdata, having a Portrait preview. May be overly complicated, though, given PyDAT would need the ability to interpret and display SMK files.

Idea 8: PyGRP controls in the Iscript Editor's GRP Previewer.

Thanks, the problems have been fixed for the next version.

Idea 1: Good idea, i'll probably add this.
Idea 2: Possibly, but I'll have to find out what the values correspond to.
Idea 3: Yeah sure i'll do that.
Idea 4: Sorry, this will not be implemented
Idea 5: Yeah i'll do that.
Idea 6: Sure, will do.
Idea 7: Not going to happen unless I make a SMK editor (i've thought about it, maybe in later versions)
Idea 8: Will do also.

Thanks for the bug reports and especially the great ideas!

PyGRP, when pushing the play button on a certain GRP:
Idea: PyDAT Omni tab. When opening an MPQ, this tab would have everything all rolled into one. For instance:

Marine folder
--> Stats (Units.dat)
--> Gauss Rifle (Weapons.dat)
--> Flingy (Flingy.dat)
--> Infantry Armor (Upgrades.dat)
--> Infantry Weapons (Upgrades.dat)
--> Etc.
--> If cross-application jumps become a reality, then additional things could be filed under here, like the Iscript, LO*s, and TBL entries.

Siege Tank folder
--> Tank Stats
--> Tank Turret Stats
--> Siege Stats
--> Siege Turret Stats
--> Arclite Cannon
--> Arclite Shock Cannon
--> Flingy
--> Vehicle Armor
--> Vehicle Weapons
--> Sprite
--> Image
--> Portrait

So it'd let you quickly alter everything related to each unit. Since it's dealing with the MPQ, it could save a custom TXT file, like FireGraft, with custom sorting and naming for the most streamlined modding possible.

If the folders contain things that you don't need to worry about in your mod, or prefer going to the manually in exchange for a more concise list, an Options menu with view checkboxes for each item could be made available. So, if you don't need the armor and weapon upgrades, uncheck those, and they'll hide from view.

Can I please have the GRP?

The idea MIGHT be implemented later down the line, but I dont now.

Thanks!

It actually happened on a couple:

http://www.staredit.net/files/1065/

http://www.staredit.net/files/1070/

http://www.staredit.net/files/596/ (In Weapons --> recolor- super phase dis.grp)

---

Oh, also my GRPs are no longer associated to PyGRP. In a previous version, I clicked the association button, and it worked great. Since I've replaced that with the latest release, the association is broken, and clicking the association button does not work. It gives the error:

"Registry Error: Could not remove pre-existing file association"

Oh, and when you go to open a GRP in PyGRP, the title of the dialogue box says: "Open aiscript.bin"

Lol, ok. Thanks I'll check it out asap.

Idea: PyDAT, Weapons.dat, output field for range as pixels. Other applications use pixel range, like iscript, so it'd be handy. 1 range = 16 pixels.

PyMS v1.1.0 has now been released! This includes the much needed PyTBL closing fix, and the new PyTILE, along with other new features/bug fixes. I recommend updating ASAP! One big change you should be aware of is the source version (what the Mac users and some Windows users use), now requires PIL to run. If your program isn't opening from the source version, that might be why. Check out the docs for a link to the download if you use the source version.

Your idea missed this version Hercanic, but I can do it for the next. Are you sure 1 range = 16 pixels?

Yep, definately sure. I've been working with the factor of 16 per range unit within iscript successfully (iscript uses pixels).

v1.1.1 has been released, get it on the main PyMS page! This version fixes many bugs, adds new features, and adds the new program PyPCX. Enjoy!