Re: [M-dev]Re: True aim of marathon (and a 3D player model)

[Jeremy <dur...@xm...>]

A lot of these things I would definitely want to be in an MML script or
soemthing.  To just add it all into the engine with reckless abandon doesn't
seem too wise to me.  There's a reason that Bungie left out a lot of what
they left out.  And most assuredly, not all of it was because the game is so
"old".  I'm all for adding optional things in there for scenarios.  That's
great.  But to just make an engine around a scenario (or set of ideas) gets
away from what bungie was doing with their physics, shapes, sounds, etc.
files.  I think they were very justified in doing so and we would be as
well.

  My point is to make things like this optional or enabled by a scenario,
not necessarily all the time in-engine as you seem to be suggesting.

  --Jeremy

----- Original Message -----
From: <Alc...@ao...>
To: <mar...@li...>
Sent: Monday, January 29, 2001 4:59 PM
Subject: Re: [M-dev]Re: True aim of marathon (and a 3D player model)


>
> In a message dated 1/28/2001 2:55:27 AM, ag...@co... writes:
>
> << Arrrgh! Why does *everybody* say this! What part of "author specified
> function" don't you understand? *Nobody* thinks we should have jumps,
> headshots, etc. available by default in current maps! Are you missing the
> whole reason MML was invented? >>
>
> Perfectly true, and I don't see why some of these things would even
conflict
> to begin with. The only spot I see is on level 4 where you jump down the
> shaft. Fall damage would be bad bad bad for that map, unless you remade it
> with a ladder all the way down. We couldn't do that before, but now with
that
> amazing number of polys thing, it would be feasible. I don't see anywhere
> that headshots would conflict though...
>
> Hannibal
>
> _______________________________________________
> Marathon-devel mailing list
> Mar...@li...
> http://lists.sourceforge.net/lists/listinfo/marathon-devel
>