Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Loading…

Enemy Territory - Entities missing #91

Closed
repere opened this Issue · 12 comments

4 participants

@repere

Dear,

I would like, first of all, to thank you and to congratulate you on your project ! Continue like that.

I would like to know if it is possible to add (manually or via an update) entities present in the versions 1.4 and 1.5 as, for example :

Misc_teleporter_dest
trigger_teleporter
target_teleporter
func_button

I have to try to add them thanks to the file et_entities.def (in installs/ETPack/install/etmain/scripts folder) but it did not work.

Thank you for indicating to me if it is possible to correct it,

Sincerely.

@TTimo
Owner

Looks like this is specific to ET .. can you point us to a more up to date ET entities file to use?

@repere

Hum ok, that's completely true but target_teleporter and others ones work on ET game and as you probably know, a lot of mapper use it (for a more funny map).

Is it possible to add them in extra entities or maybe in a plugin to show : "Ok, this is not include in original ET game but is still work" ?

And file can maybe look like this (or look like gtkRadiant 1.4 or 1.5 file, I cannot find them) :

/*QUAKED target_teleporter (1 0 0) (-8 -8 -8) (8 8 8)
-------- KEYS --------
(none)
-------- SPAWNFLAGS --------
(none)
-------- NOTES --------
The activator will be teleported away.
*/

/*QUAKED trigger_teleport (.5 .5 .5)
-------- KEYS --------
(none)
-------- SPAWNFLAGS --------
(none)
-------- NOTES --------
Touching this will teleport players to the location of the targeted misc_teleporter_dest entity.
*/

/*QUAKED misc_teleporter_dest (1 0 0) (-32 -32 -24) (32 32 -16)
-------- KEYS --------
(none)
-------- SPAWNFLAGS --------
(none)
-------- NOTES --------
Point teleporters at these
*/

But you certainly know better than me how do it could be programming...

This is just my point of view but I think a lot of mappers use it.

Thank,

Sincerely.

N.B : I am not sure about "mappers" term (it's maybe an only french word) but as you can understand, this means "a person who's creating a map".

@repere

And an other point, completely different I know, maybe should be usefull to add "allowteams" key in func_door_rotating and func_door entities :

-------- KEYS --------
"allowteams" axis for axis teams, allies for allies teams and cvops for coverops player.

And this key is include in original ET map (fueldump, oasis, battery).

@0bsidian

It sounds like these are remnants of Quake 3 entities that are still operational in ET. I could just append them to the ET .def files. I don't have ET installed, so will you be able to test these entities in a test map to verify that they work?

@0bsidian

Download the following:
https://dl.dropbox.com/u/20123341/et_entities-MODIFIED.def

Back up your existing "et_entities.def" by changing the extension to something like "et_entities.bak", then drop the new file into your "etmain\scripts\" directory.

Build a simple test map that uses all of the entities that you listed above to verify that they work for W:ET. Compile the map to test functionality. If you can verify that they work, I'll commit the changes.

@merlin1991

I have a quite complete def file from long ago here: http://merlin1991.me.funpic.de/DDCustom.def
Might contain a few TC:Elite specific entities though.

I'll be going over the ET source in the next weeks and will create a new, hopefully complete def file for the gamepack.

@repere

Firstly, with a misc_teleporter_dest we can set direction in which player will look when teleported whereas with target_teleporter we cannot.

NB : I think misc_teleporter_desc should have model but I do not have it (Q3 model certainly but is not very important...)

I have made 6 different situations :

  1. trigger_teleport + misc_teleporter_desc : work !

  2. trigger_multiple + target_teleporter + misc_teleporter_desc : work !

  3. trigger_teleport + target_teleporter + misc_teleporter_desc : work but we are teleported at target_teleporter position not misc_teleporter_desc position...

  4. trigger_multiple + misc_teleporter_desc : nothing happen !

  5. trigger_teleport + target_teleporter : work !

  6. trigger_multiple + target_teleporter : nothing happen !

So, in my mind, we should set 2 different solutions :

A. : trigger_teleport + misc_teleporter_desc (target_teleporter works too but we cannot set angle when he's teleported) => it's for a simple teleporter !

B. : trigger_multiple + target_teleporter + misc_teleporter_desc => it's for a customizable (axis, allies only,..) and complex (one or more target + misc) teleporter.

Thus to initialize a target_teleporter you have to enter 2 values : target (name of misc_teleporter_desc) and targetname (name of trigger_teleport to link with) OR select trigger_multiple then target_teleporter then CTRL + K AND select target_teleporter then select misc_teleporter_desc then CTRL + K.

So to conclude, yes teleporter works perfectly, we just owe to add a correct description how do we can make it and write as you wrote : "Not used for Enemy Territory, but should still be functional."

PS : Do I open an other issue for adding this one ? : "allowteams" key in func_door_rotating and func_door entities :

-------- KEYS --------
"allowteams" axis for axis teams, allies for allies teams and cvops for coverops player.

@0bsidian

I already added the func_door "allowteams" key.

@repere

Opps sorry, I didn't see entirely your modified.def file's, it's ok.

Issue completed for me.

@repere

And the last one :

target_print !

I've tested it and it works perfectly. This is what I add in my entities.def :

"
/*QUAKED target_print (0 .5 0) (-8 -8 -8) (8 8 8) AXIS_ONLY ALLIED_ONLY PRIVATE
Not used for Enemy Territory, but should still be functional. This will print a message on the center of the screen when triggered. By default, all the clients will see the message.
-------- KEYS --------
message : Text string to print on screen.
targetname : The activating trigger points to this.
-------- SPAWNFLAGS --------
AXIS_ONLY : Only the axis players will see the message.
ALLIED_ONLY : Only allied team players will see the message.
PRIVATE : Only the player that activates the target will see the message.
*/
"

Now my entities.def looks like this in agreement with the conditions tested previously :
"
//---------------------------------------
// Obsidian 2012-07-19
// Unofficial entities added. These are remenants from Quake 3, but should still be functional.
// #91
//---------------------------------------
/*QUAKED misc_teleporter_dest (1 .5 .25) (-32 -32 -24) (32 32 -16)
Not used for Enemy Territory, but should still be functional. Teleport destination location point for trigger_teleporter entities.
-------- KEYS --------
angle : Direction in which player will look when teleported.
targetname : Make the trigger_teleporter point to this.
*/

/*QUAKED target_teleporter (0 .5 0) (-8 -8 -8) (8 8 8)
Not used for Enemy Territory, but should still be functional. Activating this will teleport players to the location of the targeted misc_teleporter_dest entity. Unlike trigger_teleport, this entity must be activated by a trigger and does NOT allow client prediction of events.
-------- KEYS --------
target : This must point to a misc_teleporter_dest entity.
targetname : Activating trigger points to this.
-------- NOTES --------
Common usage is : trigger_multiple -> target_teleporter -> misc_teleporter_desc. You must use trigger_multiple instead of trigger_teleport. It is use for a customizable (axis, allies only, toggleable,...) and complex (one or more target + misc) teleporter.
*/

/*QUAKED trigger_teleport (.5 .5 .5) ?
Not used for Enemy Territory, but should still be functional. Touching this will teleport players to the location of the targeted misc_teleporter_dest entity. This entity allows client prediction of events.
-------- KEYS --------
target : This must point to a misc_teleporter_dest entity.
-------- NOTES --------
Common usage is : trigger_teleport -> misc_teleporter_desc. Also works with target_teleporter but you can't set direction in which player will look when teleported.
*/

/*QUAKED target_print (0 .5 0) (-8 -8 -8) (8 8 8) AXIS_ONLY ALLIED_ONLY PRIVATE
Not used for Enemy Territory, but should still be functional. This will print a message on the center of the screen when triggered. By default, all the clients will see the message.
-------- KEYS --------
message : Text string to print on screen.
targetname : The activating trigger points to this.
-------- SPAWNFLAGS --------
AXIS_ONLY : Only the axis players will see the message.
ALLIED_ONLY : Only allied team players will see the message.
PRIVATE : Only the player that activates the target will see the message.
*/
"

@0bsidian

Done. I just have to commit the changes, I'll do that when I'm done with the Q3, QL and UrT .def files.

@TTimo
Owner

Closing per Obsidian

@TTimo TTimo closed this
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.