I understand what you mean. As far as I know, doors tend to close every time a new round starts, and they also have a "Fire on close" key. So in theory, if used with the "Toggle" flag enabled and "Delay before close" set to "-1" (And maybe also with "Start opened" flag enabled as well, not sure), you can trigger entities whenever a new round starts.
I've just tried to construct an entity setup that involves this func_door trick. What it's supposed to do is to disable a trigger_multiple when a player touches it, and then enable the trigger when a new round starts. I tried disabling the trigger itself with a multisource set as its master, also I used a trigger_auto to enable the multisource on map start but the multisource seems to stay disabled for some reason. Not sure if it's even possible. But it's most likely my fault as I've never been good at setting entities up.
However, if you somehow manage to find a workaround, feel free to share it.
Also, since you're new to goldsrc mapping, I suggest you to read through all or most of the tutorials if you haven't already. This could help you alot.
Forum posts
Posted 6 years ago2018-06-08 21:33:52 UTC
in Certain entities/functions not resetting their conditions. Post #339836
in Certain entities/functions not resetting their conditions. Post #339836
Looks alot like the original. In a good way.
Impressive. But I think you should try replacing the second light_environment (the lightning) with a light_spot with "Is Sky" flag checked. This may be able to remove the need of having an info_sunlight.
I guess it doesn't have a name set to it. It strips the player of their weapons automatically without one, as far as I know.
Surface Tension.
Unforeseen Consequences.
This post was made on a thread that has been deleted.
This post was made on a thread that has been deleted.
This post was made on a thread that has been deleted.
This post was made on a thread that has been deleted.
This post was made on a thread that has been deleted.
First go to the brush (find it by number), then delete it. Even though it takes you to a completely empty part of the map, the problem brush still gets selected. Just delete it and continue mapping.
This post was made on a thread that has been deleted.
Surface Tension.
In case with apache, you probably have your difficulty set to Easy so it dies so easily. Try using the following combination of console commands to change the difficulty while playing a custom map:
Skill * (* - The level of difficlty - 1(easy), 2(normal) or 3(hard));
autosave;
load autosave;
For bigmomma you have to manually create a grid of info_bigmomma entities which are basically info_nodes. But this entity has a parameter where you can specify a value which the bigmomma's health will be set to when the monster reaches the entity. Info_bigmomma also has some other parameters which you should try tinkering with if you want to set up a good fight.
Skill * (* - The level of difficlty - 1(easy), 2(normal) or 3(hard));
autosave;
load autosave;
For bigmomma you have to manually create a grid of info_bigmomma entities which are basically info_nodes. But this entity has a parameter where you can specify a value which the bigmomma's health will be set to when the monster reaches the entity. Info_bigmomma also has some other parameters which you should try tinkering with if you want to set up a good fight.
Unforeseen Consequences.
It's because that pitch-black face isn't getting any light. Try using the "Light origin target" parameter. Place an info_null with an offset of 4-16 units away from the door's center. The direction of the offset should be opposite to the pitch-black face's position. Then give a name to the info_null and enter that name into the door's "Light origin target" field. The door will be moved to the info_null's position during light calculations and then, after the calculations are complete, moved back to its initial position.
Black Mesa Inbound.
Ok, now I get it. Your env_fade has "Activator Only" enabled. But, when you press the button, it triggers a multimanager, which then triggers a trigger_relay, so the activator data is lost in the process. The env_fade can't determine the activator and crashes the game. Triggering it directly with a multimanager with the delay set to 8.01 helped.
Here's the fixed version: https://drive.google.com/open?id=1gW0izO4F0SBoCbxSDiruc7yEtfQETzyH
I deleted some stuff while experimenting with entities so just copy over what you need to the original map.
Here's the fixed version: https://drive.google.com/open?id=1gW0izO4F0SBoCbxSDiruc7yEtfQETzyH
I deleted some stuff while experimenting with entities so just copy over what you need to the original map.
Ah. Well, that wasn't clear enough actually:
"It had to do something with the flags, or properties of the entity.It's going to be fun if setting it back to 0 is going to work for him.
I think it was the fade duration which I set to 0."
On A Rail.
So I'm taking a look at it right now. What you should do that may help you to get rid of the error is, first of all, replace all 0 delays for every multi_manager with 0.01.
Also try doing what Admer said (setting the "fade duration" parameter to 0, probably the right solution since I have the duration on my map set to 0 as well).
Also, if the tweaks listed above help, you won't need a trigger_relay at all.
Also try doing what Admer said (setting the "fade duration" parameter to 0, probably the right solution since I have the duration on my map set to 0 as well).
Also, if the tweaks listed above help, you won't need a trigger_relay at all.
Play with the properties, the entity seems to be bugged then.
The button should have the "Delay before fire/trigger" keyvalue. If it does then it's what you're looking for.
Not sure if triggering an env_fade via a relay or mm can crash the game but I believe I've heard something like that somewhere. However, on one of my maps I have a mm that triggers several entities and env_fade is one of them. Had no crashes on the map so far.
Can you try uploading the map source file so people can have a look at it or at least sending it to someone?
Not sure if triggering an env_fade via a relay or mm can crash the game but I believe I've heard something like that somewhere. However, on one of my maps I have a mm that triggers several entities and env_fade is one of them. Had no crashes on the map so far.
Can you try uploading the map source file so people can have a look at it or at least sending it to someone?
Surface Tension.
We've Got Hostiles.
Black Mesa Inbound.
Questionable Ethics.
Power Up.
Residue Processing.
Lambda Core.
Blast Pit is rather tedious and frustrating, especially if you're low on HP.
On A Rail was not only extremely atmospheric, at least for me, but it was also pretty interesting gameplay-wise, full of various secrets and obstacles.
So yeah, it's On A Rail for me.
On A Rail was not only extremely atmospheric, at least for me, but it was also pretty interesting gameplay-wise, full of various secrets and obstacles.
So yeah, it's On A Rail for me.
Forget About Freeman.
Unforeseen Consequences certainly.
It was pretty amazing seeing the facility slowly collapse.
It was pretty amazing seeing the facility slowly collapse.
Hello there.
Never really liked any of the Xen chapters, including the first one. Yeah, the borderworld may look fantastic and unusual but the levels feel rather, uhm, dull.
Black Mesa Inbound is probably the most memorable chapter for me, the accompanying track fits the map perfectly. Still remember how I enjoyed all the details and scenes during the ride when I played HL the first time.
So, Black Mesa Inbound.
Black Mesa Inbound is probably the most memorable chapter for me, the accompanying track fits the map perfectly. Still remember how I enjoyed all the details and scenes during the ride when I played HL the first time.
So, Black Mesa Inbound.
Questionable Ethics.
Definitely Power Up. Awesome chapter (which I always skip with tripmines).
"Get Quark for level editing"Wouldn't Jackhammer suit that purpose better?
Texturing the brush with NULL is a better option because if you do so then the lightmap for this brush will not be generated AFAIK.
Use the AAATrigger texture only on "trigger_" entities. I'd not recommend to use it for anything else.
Give your monster_gman a name first. Then, draw an invisible, null-textured brush around him and tie it to func_breakable. Set whatever properties you want, but set the "Material type" field to "Flesh". After that, also set the "Target on break" field to "kill_relay_1", this is going to be the name of our trigger_relay. Create it first, then set the "Name" field to "kill_relay_1". Then type your monster_gman's name into the "KillTarget" field. You may also turn the trigger_relay's "Remove on fire" flag on so it gets removed once it has been activated.
"I'm open to suggesitons on keeping this archive up to date."If so, may I ask you to replace the current version of deadlands with the new one? It would be very nice of you.
The map will mostly be lit with purple lights so I can't promise a great color diversity. I can't think of anything else that'd fit.
If a door has a name, it automatically becomes openable only via a trigger of some kind, even if there's no such trigger connected to the door on the map. So if you give the door a name, no matter what name, it'll become impossible to open by just bumping into it.
If you, though, want to make a door that can be opened the usual way or by triggering it remotely but that has to be unlocked first then you'll need to use the multisource entity. There's a tutorial about this kind of doors here on TWHL, so I recommend you to have a read through it.
If you, though, want to make a door that can be opened the usual way or by triggering it remotely but that has to be unlocked first then you'll need to use the multisource entity. There's a tutorial about this kind of doors here on TWHL, so I recommend you to have a read through it.
So, found my map in the pack, thanks for that. At least I've left a mark somewhere, kinda.
The problem is, I have almost finished rebalancing dm_deadlands. The old version had too many gaussclips lying around, and that wasn't the only issue. Also several cosmetic changes have been made.
If only you'd have waited with the release a little bit longer...
Anyway, nice job out there. Judging by the readme file you had to go through hell to get most of the maps lol.
The problem is, I have almost finished rebalancing dm_deadlands. The old version had too many gaussclips lying around, and that wasn't the only issue. Also several cosmetic changes have been made.
If only you'd have waited with the release a little bit longer...
Anyway, nice job out there. Judging by the readme file you had to go through hell to get most of the maps lol.
I hope you have the latest version of TSLRCM installed - there's no point to play this game without it. The mod restores most of the content that was cut from the final game.
Also you should try a mod that brings back M4-78, the droid planet, if you haven't. Looks pretty nice judging by the gameplay vids I've seen.
Also you should try a mod that brings back M4-78, the droid planet, if you haven't. Looks pretty nice judging by the gameplay vids I've seen.