Legacy:Actor Class Hierarchy
This is the class tree extending from Actor in UT2003 and UT2004. For a class tree of the GUI components see GUI Class Hierarchy.
Contents
Adding new class pages
Any UT2003 class page should begin with the text:
If you want to add information on a UT2003 class:
- Put a link here to the class you want to describe.
- If the link is taken by a Unreal Tournament class then, in that class:
- # Put a link to "{classname} (UT)", substituting the current classname
- # Move all the text from the page to this new page.
- # Change the box at the top of the UT class to start with "
UT ::" for clarity.
Use the Class Wikifier to create the basics of a wiki page from an UnrealScript class.
Class Tree
You won't see all of these classes in the Actor Classes Browser unless you uncheck "Placeable Classes Only". And then you'll also only see the classes of the packages which are loaded. You can manually load *.u packages to add them to the class heirarchy
Key:
- ">>" means that class' subtree is expanded on the class page.
- Classes that exist only in UT2004 are labelled as such
Actor +- AimedAttachment +- Brush | +- Volume >> +- Controller | +- AIController | | +- ScriptedController | | +- Bot | | +- xBot | +- PlayerController | +- Camera | +- MessagingSpectator | | +- DemoRecSpectator | | +- UTServerAdminSpectator | +- UnrealPlayer | +- CinematicPlayer | +- xPlayer +- DamageType >> +- Effects +- Emitter | +- NetworkEmitter (UT2004 only) +- Gib +- HUD >> +- Info | +- Combo | +- FluidSurfaceInfo | +- GameInfo | | +- CinematicGame | | +- UnrealMPGameInfo | | +- DeathMatch | | +- TeamGame | | | +- CTFGame | | | | +- xCTFGame | | | +- xBombingRun | | | +- xDoubleDom | | | +- xTeamGame | | | +- ASGameInfo (UT2004 only) | | | +- Invasion (UT2004 only) | | | +- ONSOnslaughtGame (UT2004 only) | | +- xDeathMatch | | +- BossDM | +- Mutator +- Inventory | +- Ammunition | | +- BallAmmo | | +- BioAmmo | | +- FlakAmmo | | +- GrenadeAmmo | | +- LinkAmmo | | +- MinigunAmmo | | +- RedeemerAmmo | | +- RocketAmmo | | +- ShieldAmmo | | +- ShockAmmo | | | +- SuperShockAmmo | | +- SniperAmmo | | +- TransAmmo | +- KeyInventory | +- Powerups | | +- Armor | +- Weapon | +- AssaultRifle | +- BallLauncher | +- BioRifle | +- FlakCannon | +- LinkGun | +- Minigun | +- Painter | +- Redeemer | +- RocketLauncher | +- ShieldGun | +- ShockRifle | | +- SuperShockRifle | | +- ZoomSuperShockRifle | +- SniperRifle | +- TransLauncher
+- InventoryAttachment | +- WeaponAttachment +- KActor | +- KConstraint | | +- KBSJoint | | +- KCarWheelJoint | | +- KConeLimit | | +- KHinge | +- KTire | +- BulldogTire +- KVehicleFactory | +- BulldogFactory +- Keypoint | +- AIScript | | +- ScriptedSequence | | +- ScriptedTrigger | | +- UnrealScriptedSequence | +- AmbientSound +- Light >> +- MeshEffect +- NavigationPoint >> +- NetworkTrigger (UT2004 only) +- Pawn | +- KVehicle (UT2003 only, in UT2004 it is under Vehicle) | | +- KCar | | +- Bulldog | +- RedeemerWarhead | +- Scout | +- UnrealPawn | | +- xIntroPawn | | +- xPawn | | +- Monster | +- Vehicle (UT2004 only) | +-ASVehicle | | +-ASTurret | | | +-ASTurret_BallTurret | | | +-ASTurret_IonCannon | | | +-ASTurret_LinkTurret | | | +-ASTurret_Minigun | | +-ASVehicle_Sentinel | | +-ASVehicle_Sentinel_Ceiling | | +-ASVehicle_Sentinel_Floor | +-ASVehicle_SpaceFighter | | +-ASVehicle_SpaceFighter_Human | | +-ASVehicle_SpaceFighter_Skaarj | +-KVehicle | | +-KCar | | +-Bulldog | +-ONSWeaponPawn | | +-ONSArtillerySideGunPawn | | +-ONSDualACGatlingGunPawn | | +-ONSMASSideGunPawn | | +-ONSPRVRearGunPawn | | +-ONSPRVSideGunPawn | | +-ONSStationaryWeaponPawn | | +-ONSManualGunPawn | | +-ONSTankSecondaryTurretPawn | | +-ONSTankSecondaryTurretPawn_IonPlasma | +-SVehicle | +-ONSVehicle | +-ONSChopperCraft | | +-ONSAttackCraft | | +-ONSDualAttackCraft (UT2004 Bonus Pack) | +-ONSHoverCraft | | +-ONSHoverBike | +-ONSPlaneCraft | | +-ONSBomber | +-ONSTreadCraft | | +-ONSHoverTank | | +-ONSHoverTank_IonPlasma | +-ONSWheeledCraft | +-ONSArtillery (UT2004 Bonus Pack) | +-ONSGenericSD | +-ONSMobileAssaultStation | +-ONSPRV | +-ONSRV | +-ONSShockTank (UT2004 Bonus Pack) +- Pickup | +- Ammo | | +- UTAmmoPickup | | +- AssaultAmmoPickup | | +- BioAmmoPickup | | +- FlakAmmoPickup | | +- LinkAmmoPickup | | +- MinigunAmmoPickup | | +- RocketAmmoPickup | | +- ShockAmmoPickup | | +- SniperAmmoPickup | +- ArmorPickup | +- KeyPickup | +- TournamentPickup | | +- AdrenalinePickup | | +- ShieldPickup | | | +- ShieldPack | | +- TournamentHealth | | | +- HealthPack | | | +- MiniHealthPack | | +- UDamagePack | +- WeaponPickup +- Projectile (not expanded) +- Projector | +-DynamicProjector | | +-BulldogHeadlight | +-ShadowProjector | +-XScorch (not expanded) +- Triggers (UT2003) >> +- Vignette +- WeaponFire (UT2003) >> +- xEmitter | +- ShockBeamEffect | +- SuperShockBeamEffect | +- BlueSuperShockBeam +- xPickUpBase | +- HealthCharger | +- ShieldCharger | +- SuperHealthCharger | +- SuperShieldCharger | +- UDamageCharger | +- WildcardBase | +- xWeaponBase +- xProcMesh +- xWeatherEffect
Construction Discussion
For comments during construction. This is intended as temporary.
Aphelion This is my start on the class tree. Please add to it, water it and help it grow :) As you can see, I'm focused on the GameInfo actors. I hope other people intent on other parts come along soon...
EntropicLqd: There was talk about using namespaces for the different game types. If this was so you'd use a prefix of UT2003: rather than a suffix. We need Mychaeel or Tarquin in here to comment really.
Tarquin: Namespaces are not here yet. We more or less decided on the solution I've put above. Mych said he might work on something but I think he's very busy at the moment.
Aphelion Ta muchly...
JoeDark: Is this going to be the class tree for UT2003 or just UT? On a side note, have they decided what to do with the UT content yet?
EntropicLqd: Since Tarquin's comments seem to have vanished ... If you find you need to replace an existingly linked page containing UT content with UT2003 content then create a new page called "Page Name" (UT) and copy the original UT content into it. You can then replace the UT content with the UT2003 content on the original page. Would also be worth including a link to the UT content on the page as well.
Aphelion Praise be to the Epic people... Thanks to them, at last I can run UnrealEd and look at code in tree view... :) I'll update this tree a little bit more sensibly now. Updated the instruction up top, because I think they're a little unclear.
G-LiTe: It looks a little messy with certain entries expanded and others not. It'd be cool if we could get an actual JavaScript to make a large tree and have one big page pointing to all classes, making it easy to navigate at the same time. (so you can browse the tree just as in UEd) I don't know if this is possible, however, and even if it is, it might not be very cross platform.
Wormbo: JavaScript isn't possible or even desireable, because it would require people to actually not disable it. Partially expanded entries should be fully expanded if they don't have too many subclasses or moved to the class page if there are enough subclasses for making a class tree on that page. (Inventory, NavigationPoint and WeaponFire (UT2003) are such candidates IMHO)
[3] Expanded on Pawn... will start to go into more detail as i get my head around it...same with pickup
Lilguy: This is going to start getting really complicated with the new 2004 structure. Weaponfire doesn't subclass actor anymore for instance, so there are going to be branches that don't exist in one game but do in the other, etc. Is there (should there be) a seperate class tree for 2004? It almost seems like they'd be better off in one tree (or at least on one page) since it's unlikely that someone will bother to edit both pages. Perhaps we could color code sections as 2003-only, 2004-only, or both?
I just added a branch for "vehicle" subclasses in 2004, but one of the subclasses, KVehicle, was originally a pawn subclass in 2003...
Tarquin: Well.... you could make a copy of this tree for just UT2003 before you start major work on it – in case a joint page doesn't work out – but have a go at a joint page.
Lilguy: Ok, since I didn't find anything on how to use arbitrary text coloring, I decided to try it with bold meaning ut2004 only Perhaps we could make a little icon for 2004 instead and put that just to the right of all the ut2004 classes. Now that I think about it, there won't be any classes that are ut2003 only, but a few classes (such as weapon fires, which now subclass object) moved around.
Oh, if someone's reading this, can you tell me why the wiki text editing box extends itself past the right side of my IE window? it's getting annoying...
SHilrobot: All of the subclasses of Pickup (Ammo, TournamentPickup, etc.) were incorrectly displayed as siblings, I've changed it so it's not that way anymore. Tell me if I'm wrong.
EntropicLqd: Looks good to me. Thanks for fixing it :)
Wormbo: Actually, it was the Pickup class itself that was incorrectly listed as a subclass of Pawn, the Pickup subclasses already had the correct position compared to Pickup's real position in the class tree.
SHilrobot: Ahh, I see. That makes much more sense.
General Discussion
x classes
Why do some classes begin with an "x"? what does it mean? Does it mean anything? This snippet from the head comment of xEmitter:
renamed to avoid conflict with Emitter
Copyright 2001 Digital Extremes
Mychaeel: I suspect all classes prefixed with an "x" are content added by Digital Extremes to the basic Unreal engine created by Epic. More or less. Of course it's not consistently used.
Classes extending object
OlympusMons: Well I was trying to get something happening with an object class tree as there is many pages on the wiki that contain information relating to these classes but this page seems to have dissapeared maybe it got renamed. Anyway Ive found alot of these pages arnt linked from many if any other pages, since there is no object tree, so maybe its worth extending the actor class tree to include the document classes or something. I think its probably a better idea to get this stuff sorted before adding stuff on ut2007 that way when it does come it'll be easier to know what classes belong to what game.
Tarquin: There was a complete text list of classes... I deleted that yesterday because it's been marked as 'Delete me' for over a year. What do you mean by 'document classes'?
OlympusMons: Yeah I saw the text list and I agree that that one should have been deleted. By documented I mean classes which have pages on the wiki, I was adding some to the ut2004 class tree page that I found. I think I found them on the object page, Im thinking to clean the object page up a bit these documented and undocumented classes could go in an object class hierarchy similar to this page. Personally I just find it easier to navigate through a tree view that way you get a better understanding of the inheritance.
Tarquin: I agree, tree views are useful. There's no reason to not have an Object Class Hierarchy page :)
SuperApe: Filled in Vehicle Class tree.
OlympusMons: Bold makes the (ut2k?) stand out a bit better.
