Since this is your first actor, we begin with a simplest Moving Actor class called...

AHuman

____________________________________________________________________________________________
Recently, there has been tutorial requests, Actors, are often wanted, this is the reason for writing this.
Remember, these noobies fuel the modders of the next generation, we need people to fill the spots where others have left.
I hope you find this useful.

So, you want to make a Actor is it?
You feel confident to mod your first actor?
Then read this.
____________________________________________________________________________________________
First things first, lets get things straight with a small FAQ.

Q: Can I make an AHuman with 3 or more arms and/or legs?
A: No, not without hacky Lua magic.

Q: Does my actor have to have attachable armor?
A: No, they do not require attachable armor, however this tutorial will cover it.

Q: Does my actor need a head?
A:


Q: Can my AHuman have one leg and one arm?
A: Yes, a jumper is an actor with only one leg and no arms.

____________________________________________________________________________________________
If you are ready to continue, download the simple dummy template from the following link:
http://forums.datarealms.com/viewtopic.php?f=1&t=10247&hilit=Template
____________________________________________________________________________________________
Index:
----------------------------------
Section 1: The Sprites.
- 1.0 Head
- 1.1 Torso
- 1.2 Legs and Arms
- 1.3 Gibs
- 1.4 Extras, [Jetpacks and such]
----------------------------------
Section 2: The Actor Basics
- 2.0 Head Script
- 2.05 AddGib
- 2.1 Gib Offsets
- 2.15 Velocities
- 2.2 Legs and arms
- 2.3 Attachables
----------------------------------
Section 3: Putting it all together.
- 3.0 AddActor = AHuman
- 3.1 Positioning Offsets
- 3.2 Walkpaths
----------------------------------
Section 4: Fixing Errors
- 4.0 Basic Errors
- 4.1 Could Not Match Property!
- 4.2 Property Name wasn't Followed!
----------------------------------
____________________________________________________________________________________________
---Section 1: The Sprites---

As all good things in the world, aesthetics play a large role in the attraction of customers and gamers.
Read the following topics:
How to Pixel: The Basics, CrazyMLC - http://forums.datarealms.com/viewtopic.php?f=1&t=18005
Sprite Problems, Ultric - http://forums.datarealms.com/viewtopic.php?f=1&t=12442
Sprite Critique and Help, Contrary and CrazyMLC - http://forums.datarealms.com/viewtopic.php?f=1&t=18195

---1.0 The Head---

I'm going to simply recolour the dummy head, but feel free to create something more complex,
just make sure it fits in a 11X11 pixel square.

Notes:
- No, your sprites don't have to be the same size as the dummy.
- However if it isn't, you will have to muck around the offsets.


So:


Save the Head as HeadA.bmp in the images folder.

---1.1 The Torso---

When creating the torso, remember to make sure it matches the style of the head.
Make sure it fits the theme or style of the head. [Remember same size as the Dummy Torso! (9X18)]

So:


---1.3 The Arms and Legs---

Here is when it gets slightly harder.
Not only do you have 5 frames, you also have to have smooth transition.
How you do this, will effect how bad your walking looks.

A easy way to do this, is the twin line Method, whereas you take the longest leg frame and put a vertical line on one end, and another on the other end.
So it looks like this:
The way it works is it easily tells you how long your sprite is in comparison to the maximum extension, each frame should move around 1-3 pixels back per frame.

[Top leg Frame is 004 and bottom leg frame is 000]

Then Re-sprite it!
[Top leg Frame is 004 and bottom leg frame is 000]

The Frames also have a specific order.
The lower the frame number, the more bent the arm/leg should be.
The higher the frame number, the straighter it is.

So:
LegA000.bmp should be when the leg is at its most bent position.
Whilst,
LegA004.bmp should be when the leg reaches maximum extension.




Repeat everything for arms and Feet.

The Hands are a simple task, create a 5X5 pixel hand.

So:


As a last note, You don't need BG sprites.
You can use the FG sprites for the BG also.
However, it is a good idea when releasing a mod to make a set of BG sprites.

---1.3 The Gibs---

Gibs are what you call, debris, in the world of cortex command.

They are the parts of the particular object.
Anything that is not terrain can gib, which is the equivalent of 'destroyed into smaller pieces'.

All of the following files in the Dummy Template are Gibs:

- HeadGibA.bmp [Your head gibs into this]
- HeadGibB.bmp [Your head gibs into this]
- RibCageGibA.bmp [Your Torso gibs into this]
- RibCageGibB.bmp [Your Torso gibs into this]

Remember, when creating the gibs, they must look destroyed or ruined.
Change them to match the style of your Actor.

So:


Re-sprite the gibs!

---1.4 Extras---

Well, you have sprited everything for the most part, yes?
So now you want a custom jetpack/armor.

They must match the style of the actor, and must have a determined attach-spot.
Do not go and make an attachable sprite for the head, to find out, it doesn't fit.

Here I resprite the Jetpack.


_____________________
|------End of Section 1------|
|____________________|

____________________________________________________________________________________________

---Section 2: The Actor Basics---

Well, you've finished the sprites yes?
Now we get to the Nerdy/Geeky part, the coding.

The whole of Cortex Command relies on ini coding.
Now don't get mixed up here, but, Lua is a entirely different coding language, which is used to do things, ini can't.
In fact, Lua didn't get implemented into the CC Engine up until B23. [Current is B23]

Now, you can stop here, because, the Template already is coded to allow this to work, as long as you did not change the names
of the sprites. However, Continue if you want to have some more Uniqueness to your Actor.

---2.0 The Head Script---

Well, its time for the head, the cranium, THE HOUSING OF THE MIND.
Check the variables at the bottom of this tutorial.

So here is the basic code for a head:

PasteBin

Here are the things that would probably concern you:

GibImpulseLimit: How much pressure can be applied before the head explodes, or, how high it can fall from without exploding.
The higher this is, the higher the fall it can take.

GibWoundLimit: How many hits the head can take without exploding, however, does not affect how much hp is taken.
The higher this is, the more wounds it can take.

---2.05 AddGib---


Now, in your gibs.ini, you will find a bunch of addgibs, however, they will not be simply CopyOfs.
They will be the gib sprite you have sprited earlier.
Now you can rename the gib if you want to like, MyGib.
Then here, where it says CopyOf you can put MyGib there to make it gib the specific sprite.

CopyOfs are referring to things that were already defined, its used in guns a lot, people like to separate the magazine from the gun and the round from the magazine.
And the Projectile from the round. For instance, if I made a gib called, Giblet, I could later come and replace Gib Panel Orange Tiny A to giblet, that way, when the object with this script dies, it will gib a Giblet gib.



---2.1 Gib Offsets---

Now, the offset is where the gib will appear when a object dies. For instance, if you made a infrastructure for the head, where all the parts of the head are gibbed. It wouldn't make sense if the top of the scalp gibbed off the chin. So, you'll have to change it so that the scalp comes off the top of the head when the head gets gibbed.

Now for some reason, the y-axis is inverted, negative number make the object move up rather then down.
The x-axis works like it would in math, negatives go to the left and positives to the right.

The values are based on pixels, for instance, if the object had Y = 0 and then I made it Y = -3 the object would move 3 pixels up.
So lets say the chin of a head is 3 pixels off the center of the head, and the scalp gib is appearing where the chin is.
So at the moment, the scalp's offset is Y = 3 and X = 0. Well we want it three above the middle of the head, where the top of the head is.
So, we set the offsets to, Y = -3 and X = 0, this causes the scalp gib to appear 6 pixels higher then where it was before.

As an example, if Giblet was the scalp gib, I would change the offset to go up by doing this:



To:



This moves Giblet 6 Pixels up.

The Count is how many of the Gib you want to be Gibbed.
For example, i want two Giblets to gib when the head gibs i will change the script into this:


---2.15 Velocities---

The Velocities dictates whether or not a gib will fly away.
So if I wanted Giblet to randomly fly somewhere, I would set the Velocities according to how fast i want it to fly away.

Lets say i want it to more or less, fly slightly away, maybe 60 pixels away from the Gib origin.
I would write something like this:

(Pretty sure the velocities are in-game meters [8 Pixels [Px]] per second [Thanks for catching that Geti].)



Take note, if this is set too high it could kill a enemy.

---2.2 Legs and Arms Script---

Well, without a way to move about in cortex command, your actor could be merely a turret which can pick things up.
However, that purpose is better served by an ACrab, so we need arms and legs to allow a form of locomotion for your actor.

Inside your Dummy Template.rte folder Dummy Template.ini, you will find this script for your arm:

Variables will be explained within text: [the words after a //]

PasteBin

Take Note: Some of the variables listed in the previous section may not have been commented on.

The FG arm is most important, it is the one which holds the gun, the device, the EXPLOSIVES, however, you do not need arms.

Now if you do not have separate BG arm sprites, change this:


To This:


The Feet should be easy enough to figure out, since all it's variables has been explained.
But the code should look like this:


And for the BG Foot, same as above, if you don't have bg sprites.
Change this:



To this:



The Legs, have similar code to the arms, almost exactly the same in fact.
Now instead of me posting another chunk of code, try and figure this out by yourself.
It shouldn't be too hard!

---2.3 Attachables---

Since legs and arms are pretty much attachables, you will not see a huge difference in script.
These are used for armor or aesthetics.

Here is a sample Script:


Edit this as desired, remember, I no longer will elaborate on the variables.

Attachables are something that people like seeing, either as armor or aesthetics.
If your actor is missing Attachables people will think there is something left to be desired.

Attachables are for Helmets, Goggles, Leg Plates, Shoulder Pads, Chest plates, etc...

_____________________
|------End of Section 2------| [finally]
|____________________|


____________________________________________________________________________________________

---Section 3: Putting it All together---

Now, it may seem that I am overloading with you with information, however,
if this were elaborated by some of our more well-versed members, this could've been twice as long.

Well I guess, it's time to begin, bear with me a little longer!

---3.0 AddActor = AHuman?---

Yes, this is the basic class of Cortex Command, It will be the class or actor you'll make the most of often for your mods/faction.
So I guess we begin with elaborating on some more new variables.

PasteBin

Edit, as desired of course.
And now your done, if you want, you can continue to walkpaths and Offsets.

---3.1 Positioning Offsets---

I just realized, that I already explained the offsets pretty well in the 2.1 Gib Offsets, so I'll just repeat the basics.
Basically, offsets are what you will be using the place the attachables/ objects in the correct places as you see fit.

Now, we will be using the Cartesian Plane.
Now you probably had to boring graphs in math and such, but here is where it comes in handy.

The Coordinates position the attachables on the position relative to the position of the torso.
For Instance, the torso is the center of the Quad-Axis, and the objects your moving around are the coordinates.
Place the coordinates where you want them.
A Useful to tool to see if they are in the correct position is the Actor Viewer [Requires Purchased version of CC]
You can reload the actor's ini every time you make a change to it! Neat huh? Too bad i don't get this Luxury...

Now, if you do not have this luxury, like me, you can go into skirmish, and choose your actor, do not place him, screen shot him.
Then go and open the screen shot, Copy paste your attachable sprite onto it, and place it where it should go.
Now, zoom in all the way, find your attachable [the screen shotted one] and count the pixels to where it would fit.

For Instance, If i want a triangle positioned on his shoulder, but the offsets are bad, I would screen shot where it is on the actor.
Put the triangle on his shoulder in the screen shot, and count the vertical number of pixels of the tip of the triangle, to the super imposed
placed one, then count the x. Maybe a picture would be useful here.

Picture:

Super Imposed [Imaginary triangle]



Basically i would count the number of Px [Pixels] it takes to get the triangle to where it should be [super imposed triangle]

In this case i would have to change y by -22 and x by -27 to get the triangle to where it should be.

Remember!, -Y goes Up, +Y Goes down, -X goes left and +X Goes right.


---2.3 WalkPaths---

For this section, it's all offsets, also meet your master for this section, Roon3
http://forums.datarealms.com/viewtopic.php?f=1&t=13483&hilit=Walkpath+tutorial

Ok, the tutorial is over, enjoy your first actor.

_____________________
|------End of Section 3------|
|____________________|


____________________________________________________________________________________________

---Section 4: Error Fixing---

You may have followed the tutorial as best you can, but you get an error!
This is the basic thing modders fix every time, heck, I get an error every time I mod!
Why, because, it is easy to misspell, forget to capitalize letters, etc...
Here you will learn how to fix these common errors so that you don't have to go and post a thread.

---4.0 Basic Errors---

The most common error will be, RTE ABORTED (X_X)!
It will tell you error in line [number],
then the reason for the error in a really bland way.

Now the easiest way to find lines is to paste it on pastebin or any program similar to it.
Once you found the line you have to elaborate why there was an error.

For Instance, If the line i was getting errors on said

=> CopyOf = Bullet

Maybe I forgot to define Bullet, or the PresetName is misspelled!

So i go back a few lines and find this:

=> PresetName = bullet

Dope

Forgot to capitalize!
So now i have to change it to

=> PresetName = Bullet

It should work now!

CC Modding is about trial and Error, don't worry if the first time you tried playing your mod gives you an error.
I'm sure that even the most experienced modders still get errors.

---4.1 Could Not Match Property!---

This is common among all the CopyOfs.
Basically they couldn't find the predefined object you were referring to with CopyOf =.
This should mean that either you didn't define the object, didn't define it before this CopyOf, or Misspelled the CopyOf or PresetName.

All you have to do is fix it, the problem above is an example of this error.


---4.2 Property Name Wasn't Followed!---

This isn't very common, but once you see this, you may go into, What the Heck is this?!?!?!
The most common cause always happens in line 1, you may have accidentally put DataModule on the top.
Make sure DataModule is only on the top of the Index.ini.


---End of Tutorial---


____________________________________________________________________________________________
Further Reading:

Tutorials for Total Newbs!, StoneCrow - http://forums.datarealms.com/viewtopic.php?f=1&t=17914&hilit=Tutorial
Basic Mission Tutorial, weegee - http://forums.datarealms.com/viewtopic.php?f=8&t=16219&hilit=Tutorial
How to use and Implement Lua, mail2345 - http://lua-users.org/wiki/TutorialDirectory
Lua Tutorial, CaveCricket64 - http://forums.datarealms.com/viewtopic.php?f=73&t=17955
LordTim's Tutorials!, LordTim - http://forums.datarealms.com/viewtopic.php?f=1&t=13394

____________________________________________________________________________________________
Variables,
Stolen from the wiki:

[Take Notice, removed names, however, I list the contributed as written in the wiki here:]

- Grif
- numgun
- Geti





Updates:
-1.4 Fixed spelling mistakes, changed Quad-Axis to Cartesian Plane and made it a little easier to understand. [7/14/2010]
-1.3 Moved large blocks of code to Pastebin.com, Also error fixing.[4/12/2010]
-1.2 Changed the wiki to Geti's edit. [4/08/20120]
-1.1 Posted Error Section [3/31/2010]
-1.0 Posted the Tutorial [3/30/2010]

Editors and Contributions :

---LowestFormOfWit--- [Error Checking, Suggestions, Leg/arm frame contribution, FAQ Contribution]
---CrazyMLC--- [Error Checking]
---HyperKultra--- [Error Checking]
---DSMK2--- [Error Checking, Suggestions]
---Duh102--- [Error Checking, Suggestions]
---salt_1219--- [Error Checking]
---Grif--- [Error Checking, Suggestions]
---numgun--- [Error Checking]
---Geti--- [Wiki fix, Pastebin Suggestion, Error Checking.]

Please Contribute, or Help me correct any errors!

2.15, I always thought that it was 20px to a meter?

Aside from that though, the tutorial looks pretty great, the only other thing being that you almost suggest that you can't change the dimensions of each sprite. Might just be me on that last one though, so no worries.
Good job!

Loved it, very helpful. Bookmarked!

i know how to make one AHuman survive only with his torso.(with out lua )

woah then gotcha wants a children yours, PM him

very well done first-step tutorial!

Uhh... Care to explain this bit?

make arm/legs have non damaging wounds, make head a null.

you are wrong hahahahahahahahahahaha

Any actor without a head attachable (null or otherwise) is hard-coded to die. This is why when people want an actor to survive decapitation, they make a null head as the 'real' head, and then add a 'fake' head attachable on top that serves all visual purposes of the head, yet allows the actor to appear to walk around without one.

Correct me if I'm wrong, but I'm also pretty sure any actor without all arms/legs is also hard-coded to bleed out and eventually die. So unless you make the leg/arm BreakWounds do negative EmissionDamage, I'm skeptical of either of you knowing how to do what you claim.

A headless actor loses health very quickly, you can see this by making an actor have a lot of health and getting it decapitated. This does not happen when limbs are dismembered.

I'm 95% sure that when you have an armless/legless actor, they bleed out, regardless of wounds defined or even being present.

And you're probably right about the head, but the rate is so high, it is basically instantaneous death for any balanced actor.

If I remember correctly, the Data actor can survive headless for a good deal of time, if not effectively indefinitely.

exactly the old man is smart. 1000 put life and ready.

Lol, my way was better. I have a 100000 life man here somewhere...

Correct me if I'm wrong, but Breakwounds are not hard coded...