Heres a nice TA:S competition for you:
here: http://www.fileuniverse.com/?p=showitem&ID=1815 is a zip file containing two units and a gamedata file. This replaces the comms with an untextured (well, flatshaded) Psychasi Robotic Construction Lander (Psychasi "Commander" - CZTA) that is refusing to build stuff properly - the nanoframe comes up but the nanoboom won't aim thus preventing the nanolathe from lathing. You win if you can make the stubborn RCL build the Ore Refinery (Also included, flat shaded, and untested because I haven't built it ingame yet)
Bonus point for fixing the Ore Refinery if its broken (hopefully it won't be)
On your marks...
...Get set...
...Go!!!!!
(P.S. Winner gets free mention in CZTA credits)
builder competition
Moderator: Moderators
-
Tim Blokdijk
- Posts: 1242
- Joined: 29 May 2005, 11:18
-
Tim Blokdijk
- Posts: 1242
- Joined: 29 May 2005, 11:18
Yes, I know it's a joke, but people how are in the know about the stuff you need help with probably learned about it because they liked to get a project working them self.
So they are probably working on there own thing.
If you need there attention you need to get to the point and know you are lucky if someone actualy helps you with it.
It's not like you throw a unit at them and say "fix this, it it won't work".
And when it's not fixed within a day complain about it.
So they are probably working on there own thing.
If you need there attention you need to get to the point and know you are lucky if someone actualy helps you with it.
It's not like you throw a unit at them and say "fix this, it it won't work".
And when it's not fixed within a day complain about it.
-
Guessmyname
- Posts: 3301
- Joined: 28 Apr 2005, 21:07
-
Sean Mirrsen
- Posts: 578
- Joined: 19 Aug 2004, 17:38
-
Sean Mirrsen
- Posts: 578
- Joined: 19 Aug 2004, 17:38
Well... There's nothing wrong with your script... no, really.
Except that it didn't want to compile at first... but that was an include file problem. The actual problem I suspect your unit has is that the delay you put in the activatescr() is a tad too long. <20> isn't 20 milliseconds, it's more like several seconds. So you have to just wait a bit, and it'll start.
Except that it didn't want to compile at first... but that was an include file problem. The actual problem I suspect your unit has is that the delay you put in the activatescr() is a tad too long. <20> isn't 20 milliseconds, it's more like several seconds. So you have to just wait a bit, and it'll start.
-
Guessmyname
- Posts: 3301
- Joined: 28 Apr 2005, 21:07
Hmm. I've tried removing the delay entirely, I've tried reducing it, and I've even left it running for about 10 minutes at speed 3.
No build. Maybe its an fbi problem?
On a happier note, I've got the Infantry Training Centre semi-working: It builds, but the units inside can't get out (you have to do it manually using FPS mode) and the doors won't open and close.
Its also a tad (as in far, far) too small
The last too shouldn't take me long to fix, and I suspect the first to be a footprint issue
Oh and the infantry run like pansies too...
No build. Maybe its an fbi problem?
On a happier note, I've got the Infantry Training Centre semi-working: It builds, but the units inside can't get out (you have to do it manually using FPS mode) and the doors won't open and close.
Its also a tad (as in far, far) too small
The last too shouldn't take me long to fix, and I suspect the first to be a footprint issue
Oh and the infantry run like pansies too...
-
Sean Mirrsen
- Posts: 578
- Joined: 19 Aug 2004, 17:38
I don't know what's your problem then. It compiles and works perfectly for me. Make sure it does compile for you, then try to tamper with the statechg.h file in the Includes folder of the Scriptor, namely you need to remove the first part of the file before the "#ifdef TA". It solved my "doesn't compile" problem.