Re: Let's Play Marathon 1


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

Re: Let's Play Marathon 1

Posted By: Dispatcher Date: 5/25/13 2:58 p.m.
In Response To: Re: Let's Play Marathon 1 (Hopper)

That sounds like a challenge (perhaps the entire Marathon engine was a challenge).
I can't help it if you laugh yourself silly for the following, but here goes. A rather simplistic outline of problem handling and not at all in coding language:
10 load begin level state
100 if marathon (1) game, next. if not marathon (1) game, go to 110
101 if goal includes exploration then next
102 if fov totals include all polygons class exploration then do not apply exploration goal state, next
103 if all polygons class exploration crossed by a player point (contact with floor plane needed?), then exploration goal met, next
104 check any remaining goal states, next
105 if all goal states not met, go to 110
106 if all goal states met, apply goal rules
107 more stuff
110 whatever
I'm just tossing ideas in that may be helpful or if not, at least entertaining.

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

Replies:

Let's Play Marathon 1 Godot 5/2/13 11:18 p.m.

Re: Let's Play Marathon 1 treellama 5/24/13 3:48 a.m.

Re: Let's Play Marathon 1 Dispatcher 5/24/13 7:23 a.m.

Re: Let's Play Marathon 1 President People 5/24/13 12:29 p.m.

Re: Let's Play Marathon 1 Dispatcher 5/24/13 5:10 p.m.

Re: Let's Play Marathon 1 Dispatcher 5/24/13 5:27 p.m.

Re: Let's Play Marathon 1 Hopper 5/25/13 11:22 a.m.

Re: Let's Play Marathon 1 Dispatcher 5/25/13 2:58 p.m.

Re: Let's Play Marathon 1 treellama 5/25/13 3:42 p.m.

Re: Let's Play Marathon 1 Dispatcher 5/25/13 5:13 p.m.

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

Your Name:
Your E-Mail Address:
Subject:
Message:
: That sounds like a challenge (perhaps the entire Marathon engine was a : challenge). : I can't help it if you laugh yourself silly for the following, but here goes. : A rather simplistic outline of problem handling and not at all in coding : language: 10 load begin level state : 100 if marathon (1) game, next. if not marathon (1) game, go to 110 : 101 if goal includes exploration then next : 102 if fov totals include all polygons class exploration then do not apply : exploration goal state, next : 103 if all polygons class exploration crossed by a player point (contact with : floor plane needed?), then exploration goal met, next : 104 check any remaining goal states, next : 105 if all goal states not met, go to 110 : 106 if all goal states met, apply goal rules : 107 more stuff : 110 whatever : I'm just tossing ideas in that may be helpful or if not, at least : entertaining.

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.

Let's Play Marathon 1	Godot	5/2/13 11:18 p.m.
Re: Let's Play Marathon 1	treellama	5/24/13 3:48 a.m.
Re: Let's Play Marathon 1	Dispatcher	5/24/13 7:23 a.m.
Re: Let's Play Marathon 1	President People	5/24/13 12:29 p.m.
Re: Let's Play Marathon 1	Dispatcher	5/24/13 5:10 p.m.
Re: Let's Play Marathon 1	Dispatcher	5/24/13 5:27 p.m.
Re: Let's Play Marathon 1	Hopper	5/25/13 11:22 a.m.
Re: Let's Play Marathon 1	Dispatcher	5/25/13 2:58 p.m.
Re: Let's Play Marathon 1	treellama	5/25/13 3:42 p.m.
Re: Let's Play Marathon 1	Dispatcher	5/25/13 5:13 p.m.



	Your Name:
	Your E-Mail Address:
	Subject:
	Message: : That sounds like a challenge (perhaps the entire Marathon engine was a : challenge). : I can't help it if you laugh yourself silly for the following, but here goes. : A rather simplistic outline of problem handling and not at all in coding : language: 10 load begin level state : 100 if marathon (1) game, next. if not marathon (1) game, go to 110 : 101 if goal includes exploration then next : 102 if fov totals include all polygons class exploration then do not apply : exploration goal state, next : 103 if all polygons class exploration crossed by a player point (contact with : floor plane needed?), then exploration goal met, next : 104 check any remaining goal states, next : 105 if all goal states not met, go to 110 : 106 if all goal states met, apply goal rules : 107 more stuff : 110 whatever : I'm just tossing ideas in that may be helpful or if not, at least : entertaining.
	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: