Please help me!!

First of all, what you are doing here is illegal if you decide to distribute this, distribution of other people's work isn't appreciated especially when you are doing it like this.

Static meshes are allowed to have links to other packages outside their own for certain things and probably in this case to a skin/texture. Thus a skin/texture exists in xEffects that is being used by the static mesh... hence the reason why it is requesting for it.

More to the point, why bother with Runtime? Just use UT2003 if you're going to do that.

There are a few textures in xEffects.U, although I'm not going to really say how to extract them.

The difference between UT2003 and RT is minimal. The main difference between the two is that UT2003 has a lot of code base lying underneath thus it is very quick to say write a mod for UT2003, since a lot of the code already exists, such as code that handles weapons, pickups, inventory, gameplay, bot AI and so forth.

RT is the Unreal engine as is, as it only comes with a few example maps and the core script classes such as Actor, Pawn and so forth. However you need to par take a lot of work on your side to get a project in that.

Mapping and other physical differences are vitually non-existent as the Unreal engine versions between the two don't differ by a lot (Comparing say UT99 - UE2, would be that there is a large difference).

The fact that Runtime has a lot less "junk" in it seems very convenient for studying the basic features of the engine, and testing new ideas without the confusion of a lot of other classes.

The fact that Runtime has a lot less "junk" in it seems very convenient for studying the basic features of the engine, and testing new ideas without the confusion of a lot of other classes.

Click to expand...

No, it doesn't have junk. How can you learn from nothing? You'll end up being very very frustrated because of the lack of examples. Most good coders here started by learning the base code of working titles to see how things *click* together. For example, there are loads of replication examples strewn all over UT2003, while UE2 may have very little or none at all. Replication understanding is one of the hardest areas to understand, and if you have to learn from the small amount that UE2 offers then you'll find it very difficult.

I always suggest to people when they start with UnrealScript is to learn what this script does, what does ShieldGun do exactly, and how does it do it? That is a far better learning environment.

UE2 is there for experienced people. Because you have to make a lot of base code or underlying code it can prove to be difficult, especially if you want some simply things to be setup. For example if you wanted a working weapon system going in UE2 you have to write it all yourself, whereas with UT2003 you can simply base it off xWeapon or Weapon.

[SAS]Solid Snake said:

For example, there are loads of replication examples strewn all over UT2003, while UE2 may have very little or none at all. Replication understanding is one of the hardest areas to understand, and if you have to learn from the small amount that UE2 offers then you'll find it very difficult.

I always suggest to people when they start with UnrealScript is to learn what this script does, what does ShieldGun do exactly, and how does it do it? That is a far better learning environment.

Click to expand...

Unfortunately, sometimes this can also be very confusing. Some of the script code in UT2003 is very convoluted and irritating, and makes a poor example for someone who's learning how to code!

[SAS]Solid Snake said:

UE2 is there for experienced people.

Click to expand...

This I would definitely agree with though. I guess ideally someone in the community (alas, I'm busy with my own project ) could make some examples, maybe just with placeholder art content, that demonstrate simple means of implementing skeletal characters, inventory, HUDs etc. Just a little extra tutorial content woudl go a long way towards making the runtime a fantastic learning tool for beginners and advanced alike.

Swooping in with only the slightest provocation and giving people a dire warning that doing something remotely game-like is ILLEGAL ILLEGAL ILLEGAL is not very helpful though. I'd rather give people the benefit of the doubt; if they end up distributing a game in a way that annoys Epic then the matter will be resolved anyway.