It’s not the steps on how to make it that’s the problem, it’s that my install of GtkRadiant 1.4 lacks a trigger_push and target_position option.
Here is a picture for clarification.
Further info is in the picture.
Tried a fresh install of Radiant from that site and still missing those 2 things. Bizarre that I can’t find anywhere on the internet anyone else having this issue. Does anyone know how to add trigger_push and target_position to GtkRadiant 1.4?
Use 1.6 or find the modified et_entities.def (I have no idea where). You can also modify it yourself and add the two entities there.
I installed GtkRadiant-1.6.4-20131213 and trigger_push and target_position are still missing from the entities menu.
I did a quick google search for “et_entities.def” found this thread:
http://forums.warchest.com/showthread.php/31647-Most-recent-and-complete-et_entities-def
And downloaded this: http://www.4shared.com/zip/deBFkCbZ/entities.html?
The download was 4 files to add to the script folder, I did that and this is the result: http://i.imgur.com/EO6Btir.jpg
Guess I should clean up some duplicates, and for whatever reason still no sign of trigger_push or target_position
Does anyone know what to add to the scripts folder for those 2 entites to work?
UPDATE:
After more google searching, I found this thread:
http://www.quake3world.com/forum/viewtopic.php?f=10&t=49034
Someone posted their et_entities.def here:
https://dl.dropboxusercontent.com/u/20123341/et_entities-MODIFIED.def
I removed my et_entities.def and used theirs. Now I have a trigger_push, but still no target_position.
UPDATE 2:
The guy in this thread: http://www.quake3world.com/forum/viewtopic.php?f=10&t=49034
seemed to have the same problem as me and he replaced target_position with an info_notnull which I have and for that guy it worked. Right now I’m compiling (taking much longer than usual) hopefully this will work.
UPDATE 3:
Did not work. How should I compile the map? Does it matter how I compile when testing a trigger_push and info_notnull?
Hi,
Do you need to use trigger_push? You could use target_push with trigger_multiple instead. Info_notnull is enough for the targeting, you don’t need target_position. Here’s an example .map with a working trigger_multiple -> target_push -> info_notnull setup.
Zero
Thank you!
trigger_multiple > target_push > info_notnull
that worked
Thanks again, what a relief to get that working. Now time to have some fun with it.
EDIT: does it matter where the target_push is located? Right now I have it about 64 units above and centered over the trigger_multiple. The info_notnull seems to be the only part that determines flight path.
