Are these entities still implemented/needed/wanted?

[Pardner]

This thread applies to both mappers and coders. I didn't know where to post this, but I think it applies mostly to coders. Mappers input needed as well.

Currently mapper's entities are defined in two ".def" files..... entities.def (old Q3 entities) and entities-sg.def (our entites). Smokin Guns uses its own definitions as well as some defined in the original Q3 definitions. For those who don't map, it is kinda confusing int the editor because it shows entites that may or may not still be used in Smokin' Guns. This was done (I think) so people could map for both Q3 and SG with out interference. I feel this is no longer needed and that the definitions could use some attention.

With that said, one of my side projects has been to clean up the entites-sg.def. The end goal is to have one, complete definition file. I have been re-writing some of the descriptions and adding the definitions from the original entitis.def.

I would like to open a discussion thread/question thread about the following entites. I was wondering a) are these entities are used in maps (mappers please answer)? b) are these entites implemented in the code (coders please answer)? or c) are these entites worth keeping in the entities definitions (all)?
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 (maybe replace our ".ai bot files and bake info into bsp?)
  
• 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)
  
• target_location
  
• target_push
  
• target_remove_powerups
  
• team_CTF_blueflag (keep for future gametype?)
  
• team_CTF_redflag (keep for future gametype?)
  
• trigger_push
  
• weapon_bfg
  
• weapon_gauntlet
  
• weapon_grapplinghook
  
• weapon_grenadelauncher
  
• weapon_machinegun
  
• weapon_plasmagun
  
• weapon_railgun
  
• weapon_rocketlauncher
  
• Suspended spawnflags

Note:I know this is a lot of looking up for the coders. I just wanted to start a thread about it. Maybe just keep this in mind when you are browsing the SG source

[Joe Kari]

_skybox : is usefull (it use it in one of my demo map)
_decal : I have never used that, but could be usefull
func_plat : can be usefull
func_static : very usefull !!! that's the entity to use for far-clipping !!!
info_null : I use that for light entity (to target a point that is removed after compiling)
info_notnull : I have never used that, but it is probably usefull in some way
info_spectator_start : I don't know if SG use that
item_botroam : I have tested that, but I didn't seen any effect on bot
target_laser : probably useless

We could probably remove all Q3 weapon and powerup.

We should probably keep target_* entity.

[Pardner]

[Tequila]

I checked the code for you

• holdable_*: none supported
  
• info_camp: implemented, does exactly the same than info_notnull & target_position
  
• info_notnull: implemented
  
• info_null: implemented, but do nothing
  
• info_spectator_start: NOT implemented
  
• item_*: only items from SG are supported in the code
  
• item_botroam: implemented, need "weight" attribut to be set
  
• shooter_rocket: NOT implemented
  
• target_laser: implemented
  
• target_location: implemented
  
• target_push: NOT implemented, but can be easily activated if needed
  
• target_remove_powerups: implemented but won't return the flag, I guess it was used essentially to return the flag when you fall in lava or similar situation. Actually it only reset the target own powerups: belt, scope, gold, gatling mode, dynamite/molotov lit state
  
• team_CTF_blueflag: NOT implemented
  
• team_CTF_blueplayer <-- I assume you mean "team_CTF_redflag": NOT implemented
  
• weapon_*: only SG ones are supported
  
• Suspended spawnflags: the code is removed, but can be re-enabled

[Tequila]

Just checked about "cg_drawteamoverlay", only the overlay output is disabled in the code.

I propose to enable it again for the next beta. Btw I propose to add a server cvar to disable it on the server side with 'disabled' as default.

[/dev/random]

[Pardner]

@Tequila: the cg_drawteamoverlay might be a nice feature to help out with BR mode accidental TKs. None of the maps use target_location, but those are very easily implemented.

The target_push and suspended spawnflags really work together. Jump pads in a western themed game seems kinda silly. If anybody see a reason to have these in the editor please speak up, otherwise they are just editor clutter.

[ReD NeCKersoN]

I'd like to see entities with possible future uses remain. CTF stuff could come in handy.

EDIT: Keep target_push please. This has possibilities beyond jumpads.

[Tequila]

[Joe Kari]

[ReD NeCKersoN]

[Tequila]

[Pardner]

[ReD NeCKersoN]

[Pardner]