Hmmmm..... Since some of your code uses uppercase, and some uses lower case, anyone on linux (mac too I think) is unable to use your mod, because unlike windows, POSIX is case-sensitive. Is there an easy fix for this you think? maybe some sed magic, but that would be one crazy expression, maybe listing through all the directories, and for each bmp & wav do a sed of all the .ini files to make them compatible. It shouldn't affect windows, windows won't give two bothers what case they are.

The easiest long-term fix would be - I think - to correct it all on a windows system, and that should be a walk in the park. Use a batch file renamer (such as Bulk Rename Utility) for the extensions, then use any text editor that can do case-sensitive find-in-files and replace-in-open-files (such as Notepad++) to ensure the extensions match up.

Easy, no sed usage involved.

Another bug

When attempting to use Zealots in the CC 1.0 campaign the game crashes out when a battle is started.

but then you have to do it for every single .bmp and .wav in every single directory by hand, which could take forever. I've already got a script going which finds all the .bmp and .wav files in a given directory, creates a list of them, renames them all, and then goes through all the ini files using sed with a generated sed file to replace every occurence

Mods generally crash the campaign anyway. Though it will be less likely to crash if you turn auto base-building off from your team.

To everyone with errors:
Everything worked fine in B27. I have no idea what is causing the errors but I get the idea that data managed to screw up my work for me.
I am pretty pissed off about this '1.0' anyway, so I doubt any errors will get fixing (even if I knew how to). I am deeply sorry.
Maybe my interest in UniTec returns if data manages to redeem himself and finish the game in a normal fashion, unlike slapping a big '1.0' on a bugged beta product.

I've been finding that plenty of mods (the newer ones at any rate) work fine in the campaign, with auto-base building off. Unitech and Shield both work quite well for eg. Unitech is awesome in the campaign, although possibly quite OP.

As it is, Unitec works perfectly for me in 1.0, so it's interesting there are so many issues.

I definitely understand your feelings, Gotcha, I'm quite disappointed by how little has changed. Especially that the 'First Signs' and 'Control Chip' missions never actually went anywhere.

Woot! We can drop anything anywhere now! Any chance we can get the Drop Pod back?

Hmm. I've crashed a lot down to mods in the campaign but in this update the crashes with UniTec have actually lessened for me.

[unrelated to my last post]

Hey, Gotcha! I was up for most of the night last night tweaking the "Zombie Slaughter" activity to be a sort of "Left 4 Deadish" take on Cortex Command. It's fully playable at the moment and I'm wondering if I can have the OK to post it along side my other mod, Body Harvest. You'll get full credit for your code, assets and whatever else I used, in case you're worried about that.

also, you should totally re-add the drop pods. i don't really feel that passionately about it but it feels weird to have two unrelated posts so close to each other so this is the loose thread tying them together.

If you just created a new activity, go right ahead. No credit needed.
If you plundered my mod for its resources to create a separate mod, nope.

I'll sure be adding that pod again if CC's development will change course so that the game can entertain me again.
Aka, fat chance, sorry. Though you can just copy the droppod bits from a version that had it. Should work.

Hi Gotcha!,

I was trying to make the Taurus Raging Bull scope-less by erasing a bit of the sprite through windows paint, but after I've done that, the gun does not look as it is supposed to be (a big negative-imaged square is formed around the gun). Do you have any suggestions on how I can wield the Raging Bull without such problem?

Thanks!

Microsoft Paint screws up transparency,which means it removes the "transparent color" sections of the image because it doesn't recognize the "color".To maintain transparency,edit it with photoshop or something.

...no, not quite, though you're sort of on the right track. You should be fine if you're using Paint from any version of Windows prior to 7 or 8, but the newer versions don't save into the Cortex Command palette properly, which is why it breaks. Newer versions of the GIMP have a similar problem, though they make the files flat-out unreadable for CC.