Closed GoogleCodeExporter closed 9 years ago
Sounds like a good idea.
I'm thinking something like this:
* Manager. Besides the module manager these are optional "base components"
that deal
with a broad category or deal directly with modules (storing data for each
module,
etc. Like access mnanager creating groups for each module)
* Library. Basically this is like a manager except it's just a flat API that
doesn't
deal directly with modules. Like a usermessage library is a good example.
Just a
set of functions that wrap various usermessages.
* Module. Complete a specific task in the game. The other 2 exist so that
these can
utilize them.
Original comment by andrewbo...@gmail.com
on 13 Feb 2010 at 1:07
Original comment by andrewbo...@gmail.com
on 26 Mar 2011 at 5:30
Original issue reported on code.google.com by
richard.helgeby@gmail.com
on 10 Feb 2010 at 11:59