Search / View

[MegaByte]

I suggest you add shooter_dynamite and shooter_moltov *just copy shooter_grenade and rename parts of it the default's and settings seem to be the same* ive used it to make a cannon that fires dynamite quite fun .

Definatly keep ctf stuff we will probably want it some day.
func_push seems to not work, i think its commented out in the source code. In a western style game i dont see much use. It would probably only be used in fun map's.

[Pardner]

if I am not mistaken, I think this would require modifications to our q3map2.exe as well. I felt bad enough asking to have shooter_grenade and shooter_plasma modified. It would be nice to have them named by their actual functionality. This is on my list of things to do when I get time, but unfortunately I am no coder .

[ReD NeCKersoN]

I suggest you add shooter_dynamite and shooter_moltov

I believe it's already implemented this way. Ask Tequila in IRC to be sure, if he doesn't respond here.

[Pardner]

OK, time to revive an old thread, seems like almost everything was decided on. I had a hard drive fail so I lost my previous work, and looking at the list these items were not clear (and some are new questions):

• info_camp
• info_notnull
• info_spectator_start
• item_botroam
• target_laser
• target_remove_powerups
• target_push
• target_teleporter
• team_CTF_blueflag
• team_CTF_redflag
• trigger_push
• trigger_teleport
• misc_portal_camera
• misc_teleporter_dest

Keep in mind, I don't think they are implemented in code but they could be. Also, we could remove them since they are not being used, and then add them again if/when they ever are re-enabled in code.

[Joe Kari]

We should keep:

info_notnull
item_botroam
target_push
trigger_push
misc_portal_camera

Some of them are not used, but may be in the future. I have no idea about others.

[MsH]

Where we would need teleports in future? I think you can remove them...

[Pardner]

Where we would need teleports in future? I think you can remove them...

I realize that teleports will probably never be used in SG, but this morning I had second thoughts.... if the entity is implemented in code, then there should be the option to have it in the maps.

So, here is the list (of course things can always change):


unknown
delete
keep

• _decal
• _skybox
• func_plat
• func_static
• holdable_medkit
• holdable_teleporter
• info_camp
• info_notnull
• info_null
• info_spectator_start (commented out, not used?)
• item_armor_body
• item_armor_shard
• item_botroam
• item_enviro
• item_flight
• item_haste
• item_health
• item_health_large
• item_health_mega
• item_health_small
• item_invis
• item_quad
• item_regen
• shooter_rocket
• target_laser (commented out, not used?)
• target_location
• target_push
• target_remove_powerups
• target_teleporter
• team_CTF_blueflag
• team_CTF_redflag
• trigger_push
• trigger_teleport
• weapon_bfg
• weapon_gauntlet
• weapon_grapplinghook
• weapon_grenadelauncher
• weapon_machinegun
• weapon_plasmagun
• weapon_railgun
• weapon_rocketlauncher
• Suspended spawnflags
• misc_portal_camera
• misc_portal_surface
• misc_teleporter_dest
• shooter_grenade
• shooter_plasma

Using this list of entities sure makes Radiant a lot cleaner and organized! OCD FTW!

[Joe Kari]

I have sent you an email with my entities.def, including SG's specific stuff (farclipping, rotating train, ...), please merge your stuff with mine