lmd_interface/target_interface
This has been done in some Quake 3 based games before.
Basically, it acts the same as lmd_terminal in most ways. Except instead of tedious /interacts, it has it's own structure, like buttons you can click. background shader. Basically, a more versitile and interactive lmd_terminal.
Personally, I wouldn't see the need for this. I was just running across ST:VOY:EF and found this entity. Not a bad addition for role-playing servers, either. This is simillar to the JA Single player Mission Selection screen. This also includes a 'Cancel' Button and a 'Confirm' Button by default.
This entity is a general entity (ET_GENERAL)
Spawnflags:
1. Can be used by multiple players
2. Can only be used once
4. Starts off inactive. Needs target_activate
Keys:
model: What model to draw for the button (Has a default, if not specified, it will fire f_con1, naturally)
Backimage: Background Image
Buttonimage: Immage/Shader for the buttons that the player interacts with
Soundset (1 to 6): Sound to toggle when each button is selected
Target (1 to 6): Fires a target when a button is used
cmd (1 to 6) Button Specifier and Discribes map line 1
cmdalt: Key not used in the origonal target_interface. Discrives mapline 2
peramiter1: Command to execute when target has NOT yet been fired (Origonal key)
peramiter2: Command to execute when target has ALREADY been fired (Origonal key)
targetname: Name the entity
Example: /place lmd_interface 0 Backimage,textures/doomgiver/hyper01,buttonimage,textures/test/test1,target,levelchange1,target2,levelchange2,cmd,Camelot,cmd2,High Noon,permamiter1,levelchangeparm,peramiter2,levelnull
Note: Raven Software made it possible for target_interface to be put in a .cfg file. a line would look like this
MAP1 "Hevil" "" "map t3_hevil" "sound sound/null"
MAP1 Being the main command line
"Hevil" Being the map name. Any command can be put here. /login, /bind, /use (/use is common) It can also be one big binder
"" Is used for alternate name
"Sound" Being the sound to use when the button is pressed.
- Any other command lines need be. The .cfg can accept 4, with the exception of 5, being either the Return or the Confirm button
- Login to post comments
Two words for ya:
1. Client
2. Plugin
I've been searching through the source. Was it called 'target_interface' in Elite Force?
If it was, then there's no mention of it in the cgame or ui folders of the SDK that I can find.
| Status: | Pending | » | Will not add |
Not in any of the game files, might have been added after the code was split from mainline q3, or it was specially added during the development of that game (much more likely).
- Login to post comments

Well Crazy Assassin, the sources for such an entity are already in the game files (As well as an NPC name munro) Because of Raven Software building JKA on the sources of that exact game. Plus the Multiplayer for that game was built on the same premissis. So a client plugin might not be nessassery
Anyway, I don't see the point of this entity. I'd just think it be nice for some roleplaying servers.