Relighting Lights - Revision history

Geep: /* Light Switches */

2023-01-23T22:43:10Z

Light Switches

← Older revision		Revision as of 22:43, 23 January 2023
Line 78:		Line 78:
	Some lights, for example the desk lamp, are turned on/off by frobbing them directly. For lights that have a switch, AI will use the switch. If more than one switch can turn a light on/off, AI will use the nearest. Though AI need a direct line of sight to the light to notice that it's out, they don't need a direct line of sight to a switch. The switch can be behind a door, around a corner, or even on a different floor. Wherever it is, if AI can walk to it, they'll use it.		Some lights, for example the desk lamp, are turned on/off by frobbing them directly. For lights that have a switch, AI will use the switch. If more than one switch can turn a light on/off, AI will use the nearest. Though AI need a direct line of sight to the light to notice that it's out, they don't need a direct line of sight to a switch. The switch can be behind a door, around a corner, or even on a different floor. Wherever it is, if AI can walk to it, they'll use it.

	If there are difficulties, try adding the ~~relight-position~~ discussed below. Beyond that, for wall switches, sometimes the AI will try to get to the ''backside'' of the switch to (unsuccessfully) relight it. This can happen if the switch origin is buried in a worldspawn wall. Either make the wall func_static or move the switch origin out of the worldspawn.		If there are difficulties, try adding the relight_position discussed below. Beyond that, for wall switches, sometimes the AI will try to get to the ''backside'' of the switch to (unsuccessfully) relight it. This can happen if the switch origin is buried in a worldspawn wall. Either make the wall func_static or move the switch origin out of the worldspawn.

	==Height of Light==		==Height of Light==

Geep: /* Light Switches */ AI backside problem

2023-01-23T22:37:44Z

Light Switches: AI backside problem

← Older revision		Revision as of 22:37, 23 January 2023
Line 77:		Line 77:

	Some lights, for example the desk lamp, are turned on/off by frobbing them directly. For lights that have a switch, AI will use the switch. If more than one switch can turn a light on/off, AI will use the nearest. Though AI need a direct line of sight to the light to notice that it's out, they don't need a direct line of sight to a switch. The switch can be behind a door, around a corner, or even on a different floor. Wherever it is, if AI can walk to it, they'll use it.		Some lights, for example the desk lamp, are turned on/off by frobbing them directly. For lights that have a switch, AI will use the switch. If more than one switch can turn a light on/off, AI will use the nearest. Though AI need a direct line of sight to the light to notice that it's out, they don't need a direct line of sight to a switch. The switch can be behind a door, around a corner, or even on a different floor. Wherever it is, if AI can walk to it, they'll use it.

			If there are difficulties, try adding the relight-position discussed below. Beyond that, for wall switches, sometimes the AI will try to get to the ''backside'' of the switch to (unsuccessfully) relight it. This can happen if the switch origin is buried in a worldspawn wall. Either make the wall func_static or move the switch origin out of the worldspawn.

	==Height of Light==		==Height of Light==

Springheel: /* shouldBeOn */

2014-03-07T01:43:13Z

shouldBeOn

← Older revision		Revision as of 01:43, 7 March 2014
Line 68:		Line 68:

	If you want AI to completely ignore a light (not even comment when it goes out), put the following spawnarg on it:		If you want AI to completely ignore a light (not even comment when it goes out), put the following spawnarg on it:
	"~~AI_USE~~" ""		"AIUSE" " "

			If it has a def_attached flame, you also need to add the following

			"set AIUSE on flame" " "

	==Light Switches==		==Light Switches==

Springheel: /* shouldBeOn */

2014-03-06T21:01:05Z

shouldBeOn

← Older revision		Revision as of 21:01, 6 March 2014
Line 68:		Line 68:

	If you want AI to completely ignore a light (not even comment when it goes out), put the following spawnarg on it:		If you want AI to completely ignore a light (not even comment when it goes out), put the following spawnarg on it:
	AI_USE ""		"AI_USE" ""

	==Light Switches==		==Light Switches==

RJFerret: /* See also */ +wikilink

2014-03-06T19:24:59Z

Springheel: /* shouldBeOn */

2014-03-06T18:32:04Z

shouldBeOn

← Older revision		Revision as of 18:32, 6 March 2014
Line 66:		Line 66:

	''shouldBeOn'' can be set on light holders. For example, a candle is a candle flame entity bound to a candle model. The candle entity is what you place in your map, and since you can't directly change the ''shouldBeOn'' spawnarg on the flame, you need to set it on the candle. This is true for all compound entities that spawn lights, from candles to fireplaces.		''shouldBeOn'' can be set on light holders. For example, a candle is a candle flame entity bound to a candle model. The candle entity is what you place in your map, and since you can't directly change the ''shouldBeOn'' spawnarg on the flame, you need to set it on the candle. This is true for all compound entities that spawn lights, from candles to fireplaces.

			If you want AI to completely ignore a light (not even comment when it goes out), put the following spawnarg on it:
			AI_USE ""

	==Light Switches==		==Light Switches==

Tels: minor tweak

2011-07-15T07:06:40Z

minor tweak

← Older revision		Revision as of 07:06, 15 July 2011
Line 95:		Line 95:
	An AI that isn't carrying a torch can still relight doused flames. New animations allow him to pull a tinderbox from his belt to get the job done.		An AI that isn't carrying a torch can still relight doused flames. New animations allow him to pull a tinderbox from his belt to get the job done.

	==~~The Light Entity~~==		== Electric Lights ==

	If you construct an electric light using the basic light entity (''light'') and an electric light model, the AI won't try to relight it if it goes out. This may or may not change in a future rev.		If you construct an electric light using the basic light entity (''light'') and an electric light model, the AI won't try to relight it if it goes out. This may or may not change in a future rev.

	If you want AI to notice that an electric light has gone out, use one of the electric light entities in darkmod/Lights/Switchable/Electric/Flickering/. These entities use both lit and unlit model skins to match the light state, which makes them preferable to roll-your-own electric lights.		If you want AI to notice that an electric light has gone out, use one of the electric light entities in '''darkmod/Lights/Switchable/Electric/Flickering/'''. These entities use both lit and unlit model skins to match the light state, which makes them preferable to roll-your-own electric lights.

	== See also ==		== See also ==

Tels: add links

2011-07-15T07:03:44Z

add links

← Older revision		Revision as of 07:03, 15 July 2011
Line 1:		Line 1:
	==Overview==		==Overview==

	~~Contributed by Grayman~~.		Starting with '''[[What%27s_new_in_TDM_1.06\|v1.06]]''', TDM supports AI relighting lights. A previous version of TDM supported this in a rudimentary way, but interim versions lost that capability.

	~~Starting~~ in ~~version 1~~.06, ~~TDM supports AI relighting~~ lights. ~~A previous version~~ of ~~TDM supported this in a rudimentary way, but interim versions lost that capability~~.		In general, the human AI in TDM notice when a light that's been on suddenly goes out. They might simply comment on this, or they might try to relight the light. The mapper has control over which lights can be relit, which arouse suspicion when they've gone out, and which can be ignored. This gives the mapper another tool to enhance the atmosphere of their map.

	~~In general, the human AI in TDM notice when a light that~~'~~s been on suddenly goes out. They might simply comment on this, or they might try to relight the light. The mapper has control over which lights can be relit, which arouse suspicion when they~~'~~ve gone out, and which can be ignored. This gives the mapper another tool to enhance the atmosphere of their map~~.		The code for this was kindly contributed by '''grayman'''.

	==AI Spawnargs==		==AI Spawnargs==
Line 100:		Line 100:

	If you want AI to notice that an electric light has gone out, use one of the electric light entities in darkmod/Lights/Switchable/Electric/Flickering/. These entities use both lit and unlit model skins to match the light state, which makes them preferable to roll-your-own electric lights.		If you want AI to notice that an electric light has gone out, use one of the electric light entities in darkmod/Lights/Switchable/Electric/Flickering/. These entities use both lit and unlit model skins to match the light state, which makes them preferable to roll-your-own electric lights.

			== See also ==

			* [[Electric Lights]]

	{{ai}} {{editing}}		{{ai}} {{editing}}

Grayman: /* Relight Position */

2011-06-15T01:35:01Z

Relight Position

← Older revision		Revision as of 01:35, 15 June 2011
Line 80:		Line 80:

	Place this at the spot where you want the AI to stand when relighting. One requirement is that its horizontal distance from the light be no more than 68. Link it to the light by adding a ''target'' spawnarg on the light, with its value set to the name of the ''relight_position''. You can define multiple relight positions (''target1'', ''target2'', etc.) and TDM will select the one that's nearest to the AI at relight time.		Place this at the spot where you want the AI to stand when relighting. One requirement is that its horizontal distance from the light be no more than 68. Link it to the light by adding a ''target'' spawnarg on the light, with its value set to the name of the ''relight_position''. You can define multiple relight positions (''target1'', ''target2'', etc.) and TDM will select the one that's nearest to the AI at relight time.

			You can't assign a ''relight_position'' to a movable light, for example a candle. If you pick the light up, or knock it over, the relight position won't change. Because of this, TDM will ignore all ''relight_positions'' targeted by the light, and will instead determine a relight standing position based on where the movable light currently is.

	==Line of Sight==		==Line of Sight==

Grayman at 05:09, 9 June 2011

2011-06-09T05:09:19Z

← Older revision		Revision as of 05:09, 9 June 2011
Line 88:		Line 88:

	When a light can't be reached to be turned back on, we don't want patrolling AI to incessantly comment on the light being out. Over time, the number of comments will dwindle, then stop.		When a light can't be reached to be turned back on, we don't want patrolling AI to incessantly comment on the light being out. Over time, the number of comments will dwindle, then stop.

			==AI Don't Need a Torch==

			An AI that isn't carrying a torch can still relight doused flames. New animations allow him to pull a tinderbox from his belt to get the job done.

	==The Light Entity==		==The Light Entity==

← Older revision		Revision as of 19:24, 6 March 2014
Line 107:		Line 107:

	* [[Electric Lights]]		* [[Electric Lights]]
			* [[Light Properties]]

	{{ai}} {{editing}}		{{ai}} {{editing}}