The making of a new/updated .def for 1.4 and .ent for 1.5

(Shaderman) #41

LOL

(SCDS_reyalP) #42

FWIW, just because existing maps (ET or RTCW) use a particular spawnflag or key/value doesn’t mean it actually does anything. The ‘invulnerable’ spawnflag in player spawns is a good example of one that doesn’t do anything at all, as is the objflags key that is set in various places.

Some of these were planned or partly implemented at some point in development, and not removed from the maps when they were discarded, while others were just copy/pasted to the Nth generation. The only accurate source is the source :moo:

Quite a few of the project bugfix bugs are fixed in etpro (some using Chrukers fixes, other independently.)

(EB) #43

Just to spread some more information on this project:

-The explanations that I\we will edit into the entity definitions will have a clear & concise explanation of most known or ‘popular’ uses, maybe all uses (we can find) objectively.
-I will also be extending other portions of the program to contain links to certain websites, for topics/areas of knowledge, respectively.
-We will not be removing entities that are problematic…they will simply be re-grouped as “not recommended” in the 2d menu listing.
I am sure that these plans are going to branch out some more…so I will keep this thread up to date as much as possible.

P.S. I think Chruker meant April fool’s about the Bani thing…not an XML editor. hehehehe

(Shaderman) #44

:bash:

Edit:

Let me post something useful :slight_smile:

Here’s a list of changes we have so far (changes to the Radiant 1.5 beta et_entities.ent):[ul]
[li]Removed the following entities because they need RTCW models/textures: props_chair_chat, props_chair_chatarm, props_crate_32, props_crate_64, props_box_32, props_box_48, props_box_64, props_flamebarrel, item_health_breadandmeat, item_health_small, item_health_wall
[/li][li]Cleaned up the .ent file (entities grouped, sorted alphabetically and unified)
[/li][li]Added the following entities: func_secret, func_button, misc_spotlight, props_snowGenerator, target_location (ETPeo > 3.1.8 only)
[/li][li]Shard type for props_chairs* fixed (wood/glass were swapped, removed ceramic - not working)
[/li][li]Added atmosphere key with RAIN + SNOW (editable) and a FIRE example to worldspawn
[/li][/ul]

(Chruker) #45

Does the ‘original’ et_entities.ent file contain all of the entities that Erit-FTN found? His post: http://www.splashdamage.com/index.php?name=pnphpbb2&file=viewtopic&t=6243

(Shaderman) #46

func_secret and func_button are not included.

(DerSaidin) #47

Another question with 1.5, where did all the plugins go?

Or did I just get the wrong 1.5?

(Shaderman) #48

Ask the developers :moo: IMO there are lots of useful things missing from 1.4 (makes 1.5 unusable for me at the moment). I wonder if they will ever reappear…

(DerSaidin) #49

Yeah :frowning:

Like middle-mouse-texture-copy

I LOVE YOU MIDDLE MOUSE TEXTURE COPY THINGY!

(EB) #50

There aren’t many people helping with the coding of radiant these days. —1.5 is pretty decent though…it just needs help to be all that it can be.

Note*
1.5’s .ent file has been checked, re-touched & slightly filtered.( I refuse to remove anything that is default to the file…so I re-worded some twisted jargon.)

This project should be done relatively soon…somethings have been switched around but it essentially remains the same. - A missing “key” and “key explanation” I discovered was “allowteams” for func_door & f_d_rotating. They were not mentioned anywhere in the .ent file . [I find it odd that was overlooked.]

…too tired to type more now :zzz:

(DerSaidin) #51

Would it be possible to make certain keys required by certain entity types?

For example, a team_WOLF_checkpoint requires a scriptname, but it compiles fine, and you dont realize it’s missing until you’ve waste a few hours compiling and load it up.

If the entities editor didn’t allow you to not have a scriptname it’d certainly save some time.

(SCDS_reyalP) #52

Spog has started porting the plugins, but AFAIK this has not been released yet.

For example, a team_WOLF_checkpoint requires a scriptname, but it compiles fine, and you dont realize it’s missing until you’ve waste a few hours compiling and load it up.

If the entities editor didn’t allow you to not have a scriptname it’d certainly save some time.

That would require code support. You should use bsp only, or bsp + vis -fast for your test compiles.

(EB) #53

Well, I have thought about this…so it is nice that you brought this topic up.

Without changing the hard-code of radiant…the best that I can do with the menu re-arrangement list is to place the “KEY” & “VALUE” together for a quick&easy to use setting.
I have an example image below for the “script_multiplayer” where you would just click on the script name line and hit ENTER to add “game_manager” as the scriptname for the entity.
(I have also done this to “mapcoordsmins” and “mapcoordsmaxs” for the “Worldspawn” (because I hate typing those out all of the time)…they are set @ -1000 1000 , 1000 -1000 for an easy “click” and “hit enter” use. [needless to say that those #'s would only be used for testings.]

So I am sorry to say that with what we are doing, that is out of reach. You can change and then compile the radiant code for yourself but that seems a bit drastic for such a request.

If you guys have any requests for this file, plz, plz get them in soon as we are nearing the project’s end.
-Thanks

I Sent a bug-report to radiant about curry not working.

EDIT oh, Reyal posted while my internet took a coffee break.

(Chruker) #54

EDIT oh, Reyal posted while my internet took a coffee break.

He has also done that to me a couple of times… perhaps we need to type faster :slight_smile:

(EB) #55

Daily update…

More changes:

  1. compiled default models (some grouped) for the ammo_* entities and added them to the

.ENT file with flags and descriptions(more of a decoration use as we all know)

  1. most entity color values were set with “colour” causing sporadic color values for

bounding boxes, changed the mis-spelled to “color” for the fix

  1. Added countless entities, keys, values…etc
    [file size has doubled]

—I am also adding an extra md3 into the package: a framed picture of a tapir.
:moo:

I E-mailed SPOG about the future of the XML coding with radiant 1.5…let’s hope he gets back to me soon so that I can get this package out to you guys with error free compatibility regarding the next radiant versions to come.

!was that english! ???

(Chruker) #56

—I am also adding an extra md3 into the package: a framed picture of a tapir.

Your pet?

(psyco_mario) #57

his mother :stuck_out_tongue:

(EB) #58

I have a TEST package ready for use in 1.5

Any takers ? PM me(experienced mappers only please, for technical reasons)

…note* some changes may not be noted above.

(Jaquboss) #59

1.5? No Way! 1.3.8 is best one!
Also to talk more about entities
there is a “flamethrower” entity, however, problem in ET flamethrower code is that you need to use it all the time ( draw that blue thing as well ) if you don’t do so you get wrong direction of flame, haven’t looked into code, but it should be fixable…
moving crates seems to be ok for me, maybe add md3 to package?
Also it may be cool to create lightning preset for dlight entity…
EDIT: also noticed that music parameter is semi working, easy to fix to work on 100%

(EB) #60

I like 1.4+ the best so far…but 1.5 has ALOT of potential.

just to add:
if no one ever works on 1.5…how could 1.5 ever be worth using ? hehehe