Thanks, this has been fixed for the next version.

There is currently no way for the programs to access MPQ's. It has very high priority on things I want in PyMS, but I need to learn how to do it first. One thing you can do though is use the file associations (On the toolbar the RegEdit icon, or cube made of small cubes). Then when using WinMPQ or viewing a folder of your files, if you double click a file it will open it with the PyMS program to edit it. Cross-application jump buttons are also planned.

Thanks for the bug report and ideas, keep em coming (only ideas i hope )!

Edit: After I replied I decided to look into getting MPQ editing to work again and have successfully been able to use SFmpq to create an new MPQ+add a file to it, and open an existing MPQ+access a file in it! Expect to see MPQ's being integrated into PyMS in the next or next next version!

Post has been edited 1 time(s), last time on Nov 9 2008, 4:40 pm by poiuy_qwert.

Well, now one of the next versions main new features is added support for MPQ's! This means PyDAT will now show previews of grp's, and more things to come! Here is a preview:

looks sexy!

Idea for PyGRP:

Quick and Dirty Ground Shadows!

Program would run through the GRP, offsetting and skewing each frame by either a preset or custom set value, applying the shadow palette, then occluding the original images from the newly created shadows (as they are in SC). The entire operation would run as a batch, completing with only the skew value and a button press from the user. You could also potentially preview how the shadow would look, maybe even a terrain backdrop with a few other units/buildings in view to compare your shadow against.

Sorry but that will not be implemented. PyGRP is only a GRP to BMP (and vice-versa) converter, with a few extra features. Your image editor should be used to offset and skew the GRP's, and can easily be used to compare against other shadows too.

And for some more cool stuff. I have now added an Insert/Previewer window to PyICE for easy GRP previewing and easy frame/image/sprite/flingy command and id editing and inserting:

Yes, we could manually edit each frame, but the idea here was an automatic batch to handle all frames. The feature was more in mind with all the mods using graphics constructed from existing SC images (or pulled from another game), and the countless mods that use them and have no ground shadows whatsoever.

Recently, I picked up my old AI chat project again. However, I cant get it to compile anymore. It tells me that the target of my external jump doesnt exist. The problem is, it does exist!

In one text file, I have multirun(CHAT:Chat Loops). The other text file has ID "CHAT" and has a block called "Chat Loops". But its not working...

EDIT: Clarification: Yes, I have them imported in the same aiscript.bin, I imported the "CHAT" script first.

Also, I cant seem to figure out how to use the command line version anymore...I know it worked on that version...(How do you specify txt files to compile?)

Post has been edited 1 time(s), last time on Nov 27 2008, 8:43 pm by modmaster50.

You have to import them at the same time by either combining the scripts or using the list import to import both files. The reason is once you import the CHAT script it is compiled so there is no way to know what "CHAT:Chat loops" is when you import the other script.

Using the command line only allows you to import one txt file at a time, but to do it you would navigate to your PyMS directory with the 'cd' command, then do this if you have the source version of PyMS:

Or this for windows EXE version:

If you are trying to add your scripts onto the origional scripts and not make a new file with just your scripts, use the -a switch like so:

If you need a reference just use the -h switch to see the parameters and options:

Thanks man, list import works fine. I will be releasing the first version of the chat script soon.

Also, I found a few spelling issues in the GUI. Although rather insignificant, you could fix them with the next release. At the bottom of the AI script editor, "Original" is spelled "Origional". The "debuggerizer" button is labelled as "debugerizer" (either way, its not a word ).

I think its coming along great. No need to open up a ton of different modding programs now .

np, glad to see you back and doing some modding.

Thanks, those spelling errors are fixed for next version.

Thanks again, im glad you like it

Well, what can I say? Im glad to be back.

Suggestions:
-PyMPQ? (yes, I have one from an early version of PyAI , but, a public release)
-PyDraft (MPQDraft kinda thing in python, loads MPQs. Hmmm...may cause issues on different OSs though...)
-some sort of overall "loader" program that helps arrange mod files?

Btw, I also have that balance.py thing. Unfortunately, I think I lost PyAI v0.1 - 0.3 while cleaning my external hard-drive, so I dont have the version that displays "WTF" and some numbers to the end user (cant find the post where I reported that on broodwarai.com...)

Looking back at some of the posts I made there, they were rather obnoxious Oh well, thats all distant history now.

It's good to see that your suite is coming along quite well, my own projects are desperately lagging behind (I'm having massive trouble debugging adding files to Mpqs, motivation went downhill big time because of that)

fatimid08: Thanks, its easier making frameworks for these other file types I just ended up cheating and using SFmpq for my MPQ related functions (the problem with this being no Mac support, but I have it set up to easily change that later). You might already know, but ShadowFlare released the source of SFmpq, maybe that can help you out. I hope you can keep your motivation, a cross-platform MPQ framework would be amazing!

modmaster: PyMPQ will probably be added down the road when I have cross-platform support for MPQ's.
I will most likely never make a PyDraft, though the next version does support "creation" of SEMPQ's like DatEdit (currently implemented in PyDAT and PyAI, might add it to some other ones).
If you meant "loader" as in like a mod database that SCD4 will be doing, then probably not. But if you meant a program that you could use to layout your mod and other things to organize the creation of mods, then I have been mulling over the idea in my head for quite a while now, and it will probably happen down the line.
Haha, funny you still have that stuff I've stopped doing that since the GUI's were made, was fun while it lasted though
I'm gunna talk to baja about the bwai thing, i'm sure he'll let you come back

Ack, I just realized that the "Order" action in PyTRG doesn't work. It gives a syntax error no matter what you type in for the order; whether it be "Move," "Attack," or "Patrol" or "Patroll." That really dissapointed me .

I figured as much. I am currently using the StormLib source as basis. I'll check out the SFmpq source, see if I find it easier to work from there.

Reading .dat files is really easy, yes, and tbls too. grps and pcx files are a bit harder, but they're not the hardest around either. I really don't know about iscript or aiscript, I never could find proper specs for those.

It's starting to come back now (took it a few months). And I got in Software Engineering at McGill University this fall, so that's helping me for motivation too.

By the loader thing, I meant a mod layout helper basically. I remember there was one for Diablo II mods.

Possibly it could load up all of the mod files to help with cross-file references and debugging of the mod as a whole (instead of part by part). For example, it can check if the iscript selected for a particular GRP will play frames that dont exist. I remember there is a Diablo II modding tool that checks your whole mod for known errors. Maybe one for starcraft would be useful too.

Stop pushing back my genuine problem .

fatimid08: Nice. And great job getting accepted
modmaster: Yeah, thats what I said i'll probably do later on.
A_of_s_t: Heh, stupid mistake on my part. Thanks, fixed for next version.
If anyone has the source version and would like to fix it theirself, open Libs\TRG.py, search for the line starting with "def action_order", you should find this:

Add "return" before the "raise" line, like so:

Yay! Thank you for the fix.