ENT: Difference between revisions
Jump to navigation
Jump to search
Confirm:Do any other games or notable mods implement ENT file loading?
SirYodaJedi (talk | contribs) m (→See also) |
SirYodaJedi (talk | contribs) No edit summary |
||
| Line 6: | Line 6: | ||
{{Gcfscape|2}} can extract an ENT file from the entity lump of a standard GoldSrc [[BSP30]], as well as most Source 1 [[BSP (Source)|BSPs]]. | {{Gcfscape|2}} can extract an ENT file from the entity lump of a standard GoldSrc [[BSP30]], as well as most Source 1 [[BSP (Source)|BSPs]]. | ||
Any map editor which supports [[MAP (file format)|MAP]] files also supports loading ENT files. | |||
== See also == | == See also == | ||
Revision as of 15:21, 18 November 2024
ENT is a plain text file format which represents the contents of the entity lump of a compiled BSP. It is almost identical to the lump, only lacking the lump header.
Valve engines do not natively support loading ENT files automatically, but they can be parsed via game DLL code. 
Day of Defeat: Source does this to allow func_team_wall entities (and no other entity) to be loaded this way.
Confirm:Do any other games or notable mods implement ENT file loading?
GCFScape can extract an ENT file from the entity lump of a standard GoldSrc BSP30, as well as most Source 1 BSPs.
Any map editor which supports MAP files also supports loading ENT files.
See also
- MAP (file format), which stores entities in a very similar fashion, along with brush data.