Re: Eternally Bored - and bugged


	/-/S'pht-Translator-Active/-/

Re: Eternally Bored - and bugged

Posted By: Lunair Date: 8/9/04 9:59 a.m.
In Response To: Re: Eternally Bored - and bugged (goran)

: I never knew what you wanted to trigger actually. But, I see now, if you
: still like my way of doing things, we can change the crusher platfrom into
: a...
: dam-dam dam-daaam light platform.
: Place no bobs under "crusher platfrom" and check the box
: "deactivates polygon lights" in the deactive field.
: Make 2 ligths, both with initially active checked. One is 100% and one is 0%
: in active mode, and in inactive mode it's vice versa.
: Place one light on the platform's floor and the other one on the platform's
: ceiling.
While I'm not an extremely experienced mapmaker, I had an idea for the other issue, that of requiring that both circuits be smashed but without a constraint on which must be done first. I think that using three platforms -- A, the "crusher", B, the deactivates-adjacent,-never-deactivates, and C the deactivator -- would require that B's circuits be smashed before C's circuits. Well, I say "my idea", but I've ripped it wholesale from Jason Harper's scenario Missed Island, and requires two awake monsters, either two platforms or two liquids with associated lights, and another switch: when you start the timer, a modified and immobile enforcer is woken up in a remote corner of the map and starts firing on an immobile tick. Right in front of the tick is a one-time switch (A) which deactivates platform A (the one with the terminal's lights). Blocking the line of fire from the enforcer to switch A are two platforms (or liquids with lights). In order for the enforcer to hit switch A, the player must lower both platforms by smashing both sets of circuits in the level. They both have to be smashed and it doesn't matter what order. My new bit comes in that the "crusher" platform would actually crush the enforcer or the tick when the time limit is reached, making it so that the switch to stop the crushing platform will not be hit and so the platform continues moving for the rest of the level, never deactivating the terminal lights.
So there's platform A which slowly descends to the floor; if it is stopped in time, it will deactivate the two lights associated with it which will let the player read the Success terminal and not the Failure terminal. To stop it, the player must smash circuit boards B and C, removing obstacles B and C from the enforcer's line of fire. When the enforcer's shot hits the switch beyond obstacles B and C, platform A is stopped and the Success term is lit up. If it is not stopped, then the last sentence of the preceding paragraph comes to pass. Alternatively (solely for the sake of freeing up a few extra processor cycles), you could have two crushing platforms above the enforcer and the tick; this way they'll die at the time limit no matter what but platform A (which no longer crushes) can still be stopped.
There are probably numerous variations you could go with, but I think the basic structure is sound.
Lastly, to impress upon the players that there is, in fact, a time limit, you could have a room somewhere in the level with, oh, say, seven progress bars (platforms behind a sort of grating) which fill up as the time runs out. Platform 1 touches 2 and 3; 2 touches bars a through f; 3 touches g. Platforms 1, 2, and 3 are initially active and never deactivate, but all deactivate adjacent upon deactivation. Each progress bar touches the next one in line and activates adjacent upon deactivation. When the player starts the timer, progress bar a starts counting the time; when the enforcer's shots hit the switch, platform 1 is deactivated, which deactivates platforms 2 and 3, which deactivate all of the progress bar platforms. (Platforms 1, 2, and 3 are split up so as not to violate the 8-vertex limit.) I've made an ASCII representation of it, because that probably wasn't clear enough.
.____________.
|______1_____|
|_____2____|3|
a b c d e f g

Hope this helps!
Lunair

[ Post a Reply | Message Index | Read Prev Msg | Read Next Msg ]
Pre-2004 Posts

Replies:

Eternally Bored Steve Levinson 8/8/04 7:57 a.m.

Re: Eternally Bored Simon of team Sigma 8/8/04 9:24 a.m.

Re: Eternally Bored deathmonger 8/8/04 12:01 p.m.

Re: Eternally Bored Adam Ashwell 8/8/04 12:10 p.m.

Re: Eternally Bored Mr. Cactus 8/8/04 12:26 p.m.

Re: Eternally Bored blake37 8/8/04 1:11 p.m.

RE: Eternally Bored Blayne 8/8/04 3:45 p.m.

Re: Eternally Bored D-M.A. 8/8/04 7:31 p.m.

Re: Eternally Bored Forrest of B.org 8/8/04 4:24 p.m.

Re: Eternally Bored Steve Levinson 8/8/04 5:39 p.m.

Oh, and yes, I'm using the 512 high-res textures *NM* Steve Levinson 8/8/04 6:55 p.m.

Re: Eternally Bored Forrest of B.org 8/8/04 6:59 p.m.

Re: Eternally Bored Steve Levinson 8/8/04 8:46 p.m.

Re: Eternally Bored - and bugged Steve Levinson 8/8/04 9:10 p.m.

Re: Eternally Bored - and bugged Forrest of B.org 8/8/04 10:00 p.m.

Re: Eternally Bored - and bugged Steve Levinson 8/9/04 3:25 a.m.

Re: Eternally Bored - and bugged goran 8/9/04 4:06 a.m.

Re: Eternally Bored - and bugged Adam Ashwell 8/9/04 6:19 a.m.

Re: Eternally Bored - and bugged goran 8/9/04 7:34 a.m.

Re: Eternally Bored - and bugged Adam Ashwell 8/9/04 7:43 a.m.

Re: Eternally Bored - and bugged goran 8/9/04 7:50 a.m.

Re: Eternally Bored - and bugged Adam Ashwell 8/9/04 8:08 a.m.

Burning in the light of the moon Forrest of B.org 8/9/04 11:32 p.m.

Re: Burning in the light of the moon Adam Ashwell 8/10/04 5:02 a.m.

Re: Eternally Bored - and bugged Lunair 8/9/04 9:59 a.m.

Re: Eternally Bored - and bugged Blayne 8/9/04 2:16 p.m.

Re: Eternally Bored - and bugged goran 8/9/04 3:18 p.m.

Re: Eternally Bored - and bugged Adam Ashwell 8/9/04 6:26 a.m.

Re: Eternally Bored - and bugged Adam Ashwell 8/9/04 6:57 a.m.

Re: Eternally Bored - and bugged Steve Levinson 8/10/04 4:41 p.m.

Don't let this go to your head Steve Levinson 8/11/04 9:00 a.m.

Re: Don't let this go to your head Adam Ashwell 8/11/04 9:21 a.m.

Re: Eternally Bored - and bugged Adam Ashwell 8/9/04 10:30 a.m.

Re: Eternally Bored - and bugged Steve Levinson 8/9/04 5:23 p.m.

Anyone notice that Enforcers can't kill you? *NM* a disreputable source 8/8/04 8:20 p.m.

Yes - 1 of the bugs - Ernie, is this your fault? *NM* Steve Levinson 8/8/04 8:48 p.m.

Re: Yes - 1 of the bugs - Ernie, is this your faul Forrest of B.org 8/8/04 10:02 p.m.

Re: Yes - 1 of the bugs - Ernie, is this your faul Ori 8/8/04 11:10 p.m.

Re: Yes - 1 of the bugs - Ernie, is this your faul goran 8/9/04 12:58 a.m.

Re: Yes - 1 of the bugs - Ernie, is this your faul Adam Ashwell 8/9/04 5:57 a.m.

Re: Yes - 1 of the bugs - Ernie, is this your faul blake37 8/9/04 6:03 a.m.

Re: Yes - 1 of the bugs - Ernie, is this your faul Adam Ashwell 8/9/04 6:03 a.m.

Re: Yes - 1 of the bugs - Ernie, is this your faul Yossarian 8/9/04 6:55 a.m.

Re: Yes - 1 of the bugs - Ernie, is this your faul Adam Ashwell 8/9/04 7:03 a.m.

Re: Yes - 1 of the bugs Blayne 8/9/04 3:40 p.m.

Re: Eternally Bored Adam Ashwell 8/9/04 5:40 a.m.

Re: Eternally Bored Adam Ashwell 8/9/04 5:41 a.m.

Re: Eternally Bored goran 8/9/04 7:44 a.m.

Re: Eternally Bored Johannes Gunnar 8/9/04 8:04 a.m.

Re: Eternally Bored Adam Ashwell 8/9/04 8:06 a.m.

Re: Eternally Bored Forrest of B.org 8/9/04 9:04 a.m.

Re: Eternally Bored Adam Ashwell 8/9/04 9:16 a.m.

Re: Eternally Bored Forrest of B.org 8/9/04 9:25 a.m.

Re: Eternally Bored Adam Ashwell 8/9/04 9:41 a.m.

Re: Eternally Bored Adam Ashwell 8/9/04 9:45 a.m.

I hate this title Forrest of B.org 8/9/04 2:09 p.m.

Re: I hate this title Forrest of B.org 8/9/04 2:27 p.m.

Re: I hate this title Adam Ashwell 8/9/04 2:49 p.m.

Re: I hate this title Forrest of B.org 8/9/04 3:00 p.m.

Re: I hate this title Adam Ashwell 8/9/04 3:05 p.m.

Re: I hate this title Adam Ashwell 8/9/04 3:13 p.m.

Re: I hate this title goran 8/9/04 4:07 p.m.

Re: I hate this title Adam Ashwell 8/9/04 4:12 p.m.

Re: I hate this title blake37 8/9/04 3:50 p.m.

Re: I hate this title deathmonger 8/9/04 5:11 p.m.

I'd hate to see you *really* fly off the handle Steve Levinson 8/9/04 6:03 p.m.

A lesson for us all Plague Bearer aka Nick 8/9/04 8:09 p.m.

Re: A lesson for us all D-M.A. 8/10/04 8:34 a.m.

Re: A lesson for us all blake37 8/10/04 8:44 a.m.

Trojan infected PC = porn spam bot *NM* D-M.A. 8/10/04 9:33 a.m.

fun, i'll send your comp a get well card blake37 8/10/04 11:06 a.m.

Re: Trojan infected PC = porn spam bot deathmonger 8/10/04 12:17 p.m.

Re: I hate this title Jacke 8/10/04 5:16 a.m.

Re: I hate this title D-M.A. 8/10/04 8:26 a.m.

Re: Eternally Bored blake37 8/9/04 6:02 a.m.

On TC, everything attacks from the start *NM* Steve Levinson 8/9/04 5:42 p.m.

ok, then im just a wuss ;-) *NM* blake37 8/10/04 4:17 a.m.

Re: Eternally Bored Forrest of B.org 8/10/04 8:10 a.m.

Re: Eternally Bored blake37 8/10/04 8:34 a.m.

[ Post a Reply | Message Index | Read Prev Msg | Read Next Msg ]
Pre-2004 Posts

Your Name:
Your E-Mail Address:
Subject:
Message:
: While I'm not an extremely experienced mapmaker, I had an idea for the other : issue, that of requiring that both circuits be smashed but without a : constraint on which must be done first. I think that using three : platforms -- A, the "crusher", B, the : deactivates-adjacent,-never-deactivates, and C the deactivator -- would : require that B's circuits be smashed before C's circuits. Well, I say : "my idea", but I've ripped it wholesale from Jason Harper's : scenario Missed Island, and requires two awake monsters, either two : platforms or two liquids with associated lights, and another switch: when : you start the timer, a modified and immobile enforcer is woken up in a : remote corner of the map and starts firing on an immobile tick. Right in : front of the tick is a one-time switch (A) which deactivates platform A : (the one with the terminal's lights). Blocking the line of fire from the : enforcer to switch A are two platforms (or liquids with lights). In order : for the enforcer to hit switch A, the player must lower both platforms by : smashing both sets of circuits in the level. They both have to be smashed : and it doesn't matter what order. My new bit comes in that the : "crusher" platform would actually crush the enforcer or the tick : when the time limit is reached, making it so that the switch to stop the : crushing platform will not be hit and so the platform continues moving for : the rest of the level, never deactivating the terminal lights. : So there's platform A which slowly descends to the floor; if it is stopped in : time, it will deactivate the two lights associated with it which will let : the player read the Success terminal and not the Failure terminal. To stop : it, the player must smash circuit boards B and C, removing obstacles B and : C from the enforcer's line of fire. When the enforcer's shot hits the : switch beyond obstacles B and C, platform A is stopped and the Success : term is lit up. If it is not stopped, then the last sentence of the : preceding paragraph comes to pass. Alternatively (solely for the sake of : freeing up a few extra processor cycles), you could have two crushing : platforms above the enforcer and the tick; this way they'll die at the : time limit no matter what but platform A (which no longer crushes) can : still be stopped. : There are probably numerous variations you could go with, but I think the : basic structure is sound. : Lastly, to impress upon the players that there is, in fact, a time limit, you : could have a room somewhere in the level with, oh, say, seven progress : bars (platforms behind a sort of grating) which fill up as the time runs : out. Platform 1 touches 2 and 3; 2 touches bars a through f; 3 touches g. : Platforms 1, 2, and 3 are initially active and never deactivate, but all : deactivate adjacent upon deactivation. Each progress bar touches the next : one in line and activates adjacent upon deactivation. When the player : starts the timer, progress bar a starts counting the time; when the : enforcer's shots hit the switch, platform 1 is deactivated, which : deactivates platforms 2 and 3, which deactivate all of the progress bar : platforms. (Platforms 1, 2, and 3 are split up so as not to violate the : 8-vertex limit.) I've made an ASCII representation of it, because that : probably wasn't clear enough. : .____________. : |______1_____| : |_____2____|3| : a b c d e f g : : Hope this helps! : Lunair

If you'd like to include a link to another page with your message,
please provide both the URL address and the title of the page:
Optional Link URL:
Optional Link Title:

If necessary, enter your password below:
Password:

Problems? Suggestions? Comments? Email maintainer@bungie.org
Marathon's Story Forum is maintained with WebBBS 5.12.

Eternally Bored	Steve Levinson	8/8/04 7:57 a.m.
Re: Eternally Bored	Simon of team Sigma	8/8/04 9:24 a.m.
Re: Eternally Bored	deathmonger	8/8/04 12:01 p.m.
Re: Eternally Bored	Adam Ashwell	8/8/04 12:10 p.m.
Re: Eternally Bored	Mr. Cactus	8/8/04 12:26 p.m.
Re: Eternally Bored	blake37	8/8/04 1:11 p.m.
RE: Eternally Bored	Blayne	8/8/04 3:45 p.m.
Re: Eternally Bored	D-M.A.	8/8/04 7:31 p.m.
Re: Eternally Bored	Forrest of B.org	8/8/04 4:24 p.m.
Re: Eternally Bored	Steve Levinson	8/8/04 5:39 p.m.
Oh, and yes, I'm using the 512 high-res textures NM	Steve Levinson	8/8/04 6:55 p.m.
Re: Eternally Bored	Forrest of B.org	8/8/04 6:59 p.m.
Re: Eternally Bored	Steve Levinson	8/8/04 8:46 p.m.
Re: Eternally Bored - and bugged	Steve Levinson	8/8/04 9:10 p.m.
Re: Eternally Bored - and bugged	Forrest of B.org	8/8/04 10:00 p.m.
Re: Eternally Bored - and bugged	Steve Levinson	8/9/04 3:25 a.m.
Re: Eternally Bored - and bugged	goran	8/9/04 4:06 a.m.
Re: Eternally Bored - and bugged	Adam Ashwell	8/9/04 6:19 a.m.
Re: Eternally Bored - and bugged	goran	8/9/04 7:34 a.m.
Re: Eternally Bored - and bugged	Adam Ashwell	8/9/04 7:43 a.m.
Re: Eternally Bored - and bugged	goran	8/9/04 7:50 a.m.
Re: Eternally Bored - and bugged	Adam Ashwell	8/9/04 8:08 a.m.
Burning in the light of the moon	Forrest of B.org	8/9/04 11:32 p.m.
Re: Burning in the light of the moon	Adam Ashwell	8/10/04 5:02 a.m.
Re: Eternally Bored - and bugged	Lunair	8/9/04 9:59 a.m.
Re: Eternally Bored - and bugged	Blayne	8/9/04 2:16 p.m.
Re: Eternally Bored - and bugged	goran	8/9/04 3:18 p.m.
Re: Eternally Bored - and bugged	Adam Ashwell	8/9/04 6:26 a.m.
Re: Eternally Bored - and bugged	Adam Ashwell	8/9/04 6:57 a.m.
Re: Eternally Bored - and bugged	Steve Levinson	8/10/04 4:41 p.m.
Don't let this go to your head	Steve Levinson	8/11/04 9:00 a.m.
Re: Don't let this go to your head	Adam Ashwell	8/11/04 9:21 a.m.
Re: Eternally Bored - and bugged	Adam Ashwell	8/9/04 10:30 a.m.
Re: Eternally Bored - and bugged	Steve Levinson	8/9/04 5:23 p.m.
Anyone notice that Enforcers can't kill you? NM	a disreputable source	8/8/04 8:20 p.m.
Yes - 1 of the bugs - Ernie, is this your fault? NM	Steve Levinson	8/8/04 8:48 p.m.
Re: Yes - 1 of the bugs - Ernie, is this your faul	Forrest of B.org	8/8/04 10:02 p.m.
Re: Yes - 1 of the bugs - Ernie, is this your faul	Ori	8/8/04 11:10 p.m.
Re: Yes - 1 of the bugs - Ernie, is this your faul	goran	8/9/04 12:58 a.m.
Re: Yes - 1 of the bugs - Ernie, is this your faul	Adam Ashwell	8/9/04 5:57 a.m.
Re: Yes - 1 of the bugs - Ernie, is this your faul	blake37	8/9/04 6:03 a.m.
Re: Yes - 1 of the bugs - Ernie, is this your faul	Adam Ashwell	8/9/04 6:03 a.m.
Re: Yes - 1 of the bugs - Ernie, is this your faul	Yossarian	8/9/04 6:55 a.m.
Re: Yes - 1 of the bugs - Ernie, is this your faul	Adam Ashwell	8/9/04 7:03 a.m.
Re: Yes - 1 of the bugs	Blayne	8/9/04 3:40 p.m.
Re: Eternally Bored	Adam Ashwell	8/9/04 5:40 a.m.
Re: Eternally Bored	Adam Ashwell	8/9/04 5:41 a.m.
Re: Eternally Bored	goran	8/9/04 7:44 a.m.
Re: Eternally Bored	Johannes Gunnar	8/9/04 8:04 a.m.
Re: Eternally Bored	Adam Ashwell	8/9/04 8:06 a.m.
Re: Eternally Bored	Forrest of B.org	8/9/04 9:04 a.m.
Re: Eternally Bored	Adam Ashwell	8/9/04 9:16 a.m.
Re: Eternally Bored	Forrest of B.org	8/9/04 9:25 a.m.
Re: Eternally Bored	Adam Ashwell	8/9/04 9:41 a.m.
Re: Eternally Bored	Adam Ashwell	8/9/04 9:45 a.m.
I hate this title	Forrest of B.org	8/9/04 2:09 p.m.
Re: I hate this title	Forrest of B.org	8/9/04 2:27 p.m.
Re: I hate this title	Adam Ashwell	8/9/04 2:49 p.m.
Re: I hate this title	Forrest of B.org	8/9/04 3:00 p.m.
Re: I hate this title	Adam Ashwell	8/9/04 3:05 p.m.
Re: I hate this title	Adam Ashwell	8/9/04 3:13 p.m.
Re: I hate this title	goran	8/9/04 4:07 p.m.
Re: I hate this title	Adam Ashwell	8/9/04 4:12 p.m.
Re: I hate this title	blake37	8/9/04 3:50 p.m.
Re: I hate this title	deathmonger	8/9/04 5:11 p.m.
I'd hate to see you really fly off the handle	Steve Levinson	8/9/04 6:03 p.m.
A lesson for us all	Plague Bearer aka Nick	8/9/04 8:09 p.m.
Re: A lesson for us all	D-M.A.	8/10/04 8:34 a.m.
Re: A lesson for us all	blake37	8/10/04 8:44 a.m.
Trojan infected PC = porn spam bot NM	D-M.A.	8/10/04 9:33 a.m.
fun, i'll send your comp a get well card	blake37	8/10/04 11:06 a.m.
Re: Trojan infected PC = porn spam bot	deathmonger	8/10/04 12:17 p.m.
Re: I hate this title	Jacke	8/10/04 5:16 a.m.
Re: I hate this title	D-M.A.	8/10/04 8:26 a.m.
Re: Eternally Bored	blake37	8/9/04 6:02 a.m.
On TC, everything attacks from the start NM	Steve Levinson	8/9/04 5:42 p.m.
ok, then im just a wuss ;-) NM	blake37	8/10/04 4:17 a.m.
Re: Eternally Bored	Forrest of B.org	8/10/04 8:10 a.m.
Re: Eternally Bored	blake37	8/10/04 8:34 a.m.



	Your Name:
	Your E-Mail Address:
	Subject:
	Message: : While I'm not an extremely experienced mapmaker, I had an idea for the other : issue, that of requiring that both circuits be smashed but without a : constraint on which must be done first. I think that using three : platforms -- A, the "crusher", B, the : deactivates-adjacent,-never-deactivates, and C the deactivator -- would : require that B's circuits be smashed before C's circuits. Well, I say : "my idea", but I've ripped it wholesale from Jason Harper's : scenario Missed Island, and requires two awake monsters, either two : platforms or two liquids with associated lights, and another switch: when : you start the timer, a modified and immobile enforcer is woken up in a : remote corner of the map and starts firing on an immobile tick. Right in : front of the tick is a one-time switch (A) which deactivates platform A : (the one with the terminal's lights). Blocking the line of fire from the : enforcer to switch A are two platforms (or liquids with lights). In order : for the enforcer to hit switch A, the player must lower both platforms by : smashing both sets of circuits in the level. They both have to be smashed : and it doesn't matter what order. My new bit comes in that the : "crusher" platform would actually crush the enforcer or the tick : when the time limit is reached, making it so that the switch to stop the : crushing platform will not be hit and so the platform continues moving for : the rest of the level, never deactivating the terminal lights. : So there's platform A which slowly descends to the floor; if it is stopped in : time, it will deactivate the two lights associated with it which will let : the player read the Success terminal and not the Failure terminal. To stop : it, the player must smash circuit boards B and C, removing obstacles B and : C from the enforcer's line of fire. When the enforcer's shot hits the : switch beyond obstacles B and C, platform A is stopped and the Success : term is lit up. If it is not stopped, then the last sentence of the : preceding paragraph comes to pass. Alternatively (solely for the sake of : freeing up a few extra processor cycles), you could have two crushing : platforms above the enforcer and the tick; this way they'll die at the : time limit no matter what but platform A (which no longer crushes) can : still be stopped. : There are probably numerous variations you could go with, but I think the : basic structure is sound. : Lastly, to impress upon the players that there is, in fact, a time limit, you : could have a room somewhere in the level with, oh, say, seven progress : bars (platforms behind a sort of grating) which fill up as the time runs : out. Platform 1 touches 2 and 3; 2 touches bars a through f; 3 touches g. : Platforms 1, 2, and 3 are initially active and never deactivate, but all : deactivate adjacent upon deactivation. Each progress bar touches the next : one in line and activates adjacent upon deactivation. When the player : starts the timer, progress bar a starts counting the time; when the : enforcer's shots hit the switch, platform 1 is deactivated, which : deactivates platforms 2 and 3, which deactivate all of the progress bar : platforms. (Platforms 1, 2, and 3 are split up so as not to violate the : 8-vertex limit.) I've made an ASCII representation of it, because that : probably wasn't clear enough. : .____________. : \|______1_____\| : \|_____2____\|3\| : a b c d e f g : : Hope this helps! : Lunair
	If you'd like to include a link to another page with your message, please provide both the URL address and the title of the page:
	Optional Link URL:
	Optional Link Title:
	If necessary, enter your password below:
	Password: