Movement classes

Movement classes

Discuss game development here, from a distinct game project to an accessible third-party mutator, down to the interaction and design of individual units if you like.

Moderator: Moderators

Post Reply
User avatar
PauloMorfeo
Posts: 2004
Joined: 15 Dec 2004, 20:53

Movement classes

Post by PauloMorfeo »

In the file Gamedata/moveinfo.tdf, we have the movement classes. As far as i see, they always have a title like this:
[CLASS*]
Having * taking a sequencial number starting from 0.

Do they need to be called like that?
If so, do they really need to have those exact same numbers, i mean, a sequential order and starting from 0? Or can i have:
[CLASS3]
{}
[CLASS7]
{}
Gnomre
Imperial Winter Developer
Posts: 1754
Joined: 06 Feb 2005, 13:42

Post by Gnomre »

I don't think it'll matter if it's non-sequential, but I've never tried.

Also, just for the sake of stating it: Hovercraft won't be treated as hovercraft unless their movementclass is named "TANKHOVER2" or "TANKHOVER3" (or was it just that you have to have "hover" in the name of the class... hrm).

Also, the number of movementclasses directly correlates to the loadtime of your mod during the path calculations--so less is better here.

I just like helping out people who actually use that mystical search function
User avatar
PauloMorfeo
Posts: 2004
Joined: 15 Dec 2004, 20:53

Post by PauloMorfeo »

Thanks!

The truth is that i found out that it doesn't really matters (i think). Because, in the units's definitions, they get related to the name inside the class

Code: Select all

[CLASS*]
{
    name=MoveClassX;
    ...
}
and not the the title of the movement class. So, my exporting routine can assign them whatever number without need to worry about which one was it.

Funny how inconsistent the TA mod rules are since, in some other things, the title is what matters and in others, the title is mostly meaningless using the internal "name" tag.
Post Reply

Return to “Game Development”