You can either overwrite the existing entities.def or configure GtkRadiant 1.4 or ZeroRadiant 1.6 to use the entityplus folder as working folder

That's what I call a milestone. Thanks a lot for all the time and effort you put into this! The example map was fun to play, although I had to set the skill level down to 1. I think the damage could still be scaled down a bit, because the damage done to the player on skill level 1 feels almost fair, but the bots are by far too stupid on this difficulty to be fun. On the second difficulty, they behave alreay like I would SP bots expect to behave, but the damage they do is a too high for my taste.
But I'll test that out in some testing areas I'll prepare for myself and give you more detailed feedback later.

The PDF looks really nice. But there's one thing I would change in the install instructions in the readme. You wrote



I never used a mod folder for mapping and thus had to find out what to do now. After uninstalling Radiant multiple times (errors, crashes and so on - things that happen when you do something very wrong) I figured out I only had to go to Project Settings, leave the basepath as it was (that was the mistake - I changed it to Quake 3\EntityPlus) and choose Custom Quake III Modification in the Select Mod field. Then, the only thing one has to do, is to type "EntityPlus" in the fs_game field. I think that is a mistake other people can do too, so you could add this information to the readme.

When I took a look at the map you made, I couldn't figure out how you trigger the lava drain when Klesk is dead. How did you do that?

//EDIT: Forget about that. Found it it was done by the trigger_death with the count set to 23.

//EDIT: Is there already a possibility to let bots drop (multiple) items on their death? Or trigger things when they die another way than with a trigger_death (to make things only happen when a certain bot dies, and not when a total amount of enemies is killed)? Could this be implemented by adding a key (for example "ondeath") and a value (targetname of the target_botspawn) in the trigger_death?

This evening I'll upload new models for wooden debris and modified old ones for stone (they'll be more angled and not as smooth as before - and have fewer polys).

Nice. However, the stone models seem to refer to a shader located at models\entityplus\debris\debris_stone and there's no such thing included in your package.

Also, could you put the models in a "models\debris" folder, without the "entityplus" in there, because right now the paths to the textures are incorrect.

I just want to say I love all of you who are contributing to this mod.

Nice. Sorry to nag about this, but the model's paths to the shader seem to use backward slashes (\) instead of forward slashes (/) so it can't find the shader.

You can spawn an enemy with multiple weapons but it's up to the bot AI to pick whichever he wants to use and I think the AI is pretty straightforward in that it just picks the weapon the bot prefers and sticks to that.

- func_rotatingtrain, a combination of a func_train and a func_rotating. Mostly aesthetic, though it could be good for rotating elevators. Don`t think it would be terribly difficult to code either, just put the code for func_rotating and func_train together,

- target_difficulty. You know how in Quake 1 you had to select your difficulty from a series of hallways, rather than a by-menu system? I always thought that was so neat, and it would be cool to have an entity in Q3 which does the exact same thing. You mentioned that EntityPlus has difficulty levels which determines the difficulty of the bots. Have four spawnflags, Easy, Medium, Hard, and of course Nightmare - or you could use the Q3 system and have five spawnflags, for I Can Win, Bring it On, Hurt Me Plenty, Hardcore, and Nightmare. Attach the target_difficulty to a trigger_once / trigger_multiple and the difficulty will be changed the next time a map loads.

I had the same issue as ET, in not being able to escape the master key room. The console reported all player slots full, I wondered if there was a bot unable to spawn?

Ahh, just had some thoughts (and bugs to report):

The bugs:

- In the room where you grab the master key and fight off the monsters, there is a chance that you can kill them all off but the alarm still rings, and you can`t get out. I`m not sure if it`s just a bug with the particular map, but if it`s not it could be a serious problem in other potential maps, so you might want to look into this.

This mod is simply brilliant.
Couple of things to report:
I had the same issue as ET, in not being able to escape the master key room. The console reported all player slots full, I wondered if there was a bot unable to spawn?

- The lava, when it drains - you can drop down early and you`ll go right through it like it wasn`t there.

Thoughts / Ideas:

- The backpack system is a very nice idea. But what about if someone has to take a break during their journey? (eat dinner, bedtime, etc.) They`d have to quit and start all over again when they got back. Personally, I think that when you quit the game it is automatically saved, and you can load it back up when you come back. For right now you can do it through a new console command, (/loadgame ep_example) but hopefully, if someone is willing to do so and has the experience, you could have a redesigned graphical interface / main menu, with one of the options being to load a game from a list.

- target_difficulty. You know how in Quake 1 you had to select your difficulty from a series of hallways, rather than a by-menu system? I always thought that was so neat, and it would be cool to have an entity in Q3 which does the exact same thing. You mentioned that EntityPlus has difficulty levels which determines the difficulty of the bots. Have four spawnflags, Easy, Medium, Hard, and of course Nightmare - or you could use the Q3 system and have five spawnflags, for I Can Win, Bring it On, Hurt Me Plenty, Hardcore, and Nightmare. Attach the target_difficulty to a trigger_once / trigger_multiple and the difficulty will be changed the next time a map loads.

- On a similar note, have spawnflags so that entities only spawn in certain difficulties. That way, perhaps you can have a weak guy on lower difficulties but a rough and tough tank dude in higher ones.

- func_rotatingtrain, a combination of a func_train and a func_rotating. Mostly aesthetic, though it could be good for rotating elevators. Don`t think it would be terribly difficult to code either, just put the code for func_rotating and func_train together.

Keep up the good work man!

Secondly, the entity def doesn't show any details in the entity editor in zeroradiant. The new mod entities are on my right click menu, but no details. I'm running as a project in radiant. Do I need to remove the original def file from q3 scripts folder?

I'm thinking about making trains that turns to point every path_corner they are about to go to. Kinda like Half-Life, kinda like an actual train.

Also, a way to trigger the func_train.

Much like the camera movement in the q3mme mod.

lol this made me think. Wouldn't it be great if we could have in-game cutscenes?

One thing: I hope the terrain lvls will be huge, so we can strafe through them. I can't play a quake game without strafing! I think that will be a big problem anyway: If I play a single player game in the idtech3 engine I want to strafe... maybe a lot of gamers want this.

One thing: I hope the terrain lvls will be huge, so we can strafe through them. I can't play a quake game without strafing! I think that will be a big problem anyway: If I play a single player game in the idtech3 engine I want to strafe... maybe a lot of gamers want this.

Make the cutscenes skippable, please.

I'd make them so that they are skippable unless your name is obsidian. Then if you try to skip your entire pc freezes.

I'd make them so that they are skippable unless your name is obsidian. Then if you try to skip your entire pc freezes.

Thanks for the input. I actually remember playing this mod once. I've downloaded the source and I'll have a look at it some time.