Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

web moria improvements

19 views
Skip to first unread message

Brian Ramsay

unread,
Feb 3, 2010, 10:52:24 AM2/3/10
to
I have made some display optimizations that improve the performance of
the game. The latest Firefox and Chrome for Windows work well, and
Safari and Chrome for the Mac also work well (I am primarily using
Safari for development). Firefox for the mac is fast enough now, but
there are some keypress issues that are preventing it from being
nice. Even Internet Explorer 8 works, though it is too slow to
actually be usable.

http://foont.net/moria/game - to tool around a level
http://foont.net/moria/development - to see when the game will
actually be fun - or even a game :-)

Brian

Eli the Bearded

unread,
Feb 4, 2010, 2:05:50 AM2/4/10
to
In rec.games.roguelike.moria, Brian Ramsay <brian....@gmail.com> wrote:
> http://foont.net/moria/development - to see when the game will
> actually be fun - or even a game :-)

That's an aggressive schedule.

Elijah
------
not sure monster memories will fit in cookies

Brian Ramsay

unread,
Feb 6, 2010, 5:37:19 AM2/6/10
to
> That's an aggressive schedule.

So far, I've been running ahead of schedule rather than behind. But I
think you're right. Combat and all of its necessary spells and stats
will probably take much longer than I have penciled in. What I'll
probably end up doing is implement the structure, but leave a lot of
actual details unimplemented and continue to fill them in during the
beta period, like I've done with the actions. Eh, we'll see. Also, I
need to make it a priority to update my tests, which have fallen
behind development.

> not sure monster memories will fit in cookies

Yeah, I hadn't even looked into it yet. Looks like the most I'd be
able to store is ~4kb x maybe 25 cookies (because some are already
used). If 100kb is not enough I'll need to use either some invisible
flash stuff or, more likely, Google Gears. I'm avoiding having much
server-side interaction at this point, even though it's the logical
endpoint. I'd like to wait until I've got a working game before
dealing with those issues, hence all of the emphasis on client-side.

Actually, I just ran across this library which actually might be just
the ticket: PersistJS - http://pablotron.org/?cid=1557.

As an aside, Google Gears support would be pretty sweet anyway.
Because you could have a completely offline game in your browser if
you wanted to play while not connected to the internet.

Brian

0 new messages