addressalign-toparrow-leftarrow-rightbackbellblockcalendarcameraccwcheckchevron-downchevron-leftchevron-rightchevron-small-downchevron-small-leftchevron-small-rightchevron-small-upchevron-upcircle-with-checkcircle-with-crosscircle-with-pluscrossdots-three-verticaleditemptyheartexporteye-with-lineeyefacebookfolderfullheartglobegmailgooglegroupshelp-with-circleimageimagesinstagramlinklocation-pinm-swarmSearchmailmessagesminusmoremuplabelShape 3 + Rectangle 1ShapeoutlookpersonJoin Group on CardStartprice-ribbonShapeShapeShapeShapeImported LayersImported LayersImported Layersshieldstartickettrashtriangle-downtriangle-uptwitteruserwarningyahoo

Adventure Series: Design Mission Data Structure

In part one our quest to design a simple adventure game, we'll be designing the data structures to hold the global constants for mission data. Things like how the map is laid out, starting values, starting equipment, equipment locations, activities/actions to be performed, etc. 

Because this is part one, we'll also be setting up a git repository, a Dist::Zilla config file, and a CPAN module (which we may or may not release at the end of each part of the adventure series, but definitely will later on). 

Come join us and help to create a simple adventure game.

This blog post describes what we're trying to do in more detail.

Join or login to comment.

  • Steve K.

    Most inspiring! We got started thinking about the pros and cons of various representations -- a spirited conversation! (So, I'm guessing this was a complete success from the teamwork point of view :-) Also, amusing just watching JT type ("go ahead, we'll wait" -- well, he's not *that* slow :-) ...but theoretically, we could think about how to contribute content-transcription... If you'd like, I'll borrow the printout from you and pre-type all the words before next month...

    2 · January 11

    • Beth S.

      I was pleased at how it involved the spirited conversation AND we got decisions made.

      January 26

  • Jesse T.

    We should have invented our own. YAAML - Yet Again Another Markup Language ... Or YML - a simpler version of YAML ... Or ML - even simpler still; just the basics ... Or M - which doesn't actually parse anything. The opportunities that we're missing are endless!

    2 · January 11

    • Mark F.

      Would it have been too sadistic to use make(1) syntax -- without GNU extensions? 😅

      January 15

  • Michael M.

    I'm glad I braved the weather to be there.

    3 · January 12

  • Steve K.

    ...and yes, we YAML'd.

    1 · January 11

  • JT S.

    I'm still ok with using YAML. This project isn't going to be decided by me. The group will decide.

    January 8

  • Don

    I'm not able to make it this month, but I'm keen to see how this shakes out.

    FWIW, I spent some time checking out YAML's anchors/references, which I initially thought would be a slick way of defining room relationships, but the spec for how they actually work is unbelievably lame and really ill suited to this particular task.

    I still favor YAML, generally, but I'm extremely disappointed to see that, given all of the awesome that YAML can bring (yes, JT, I know you're not a fan :P), this potentially useful feature is essentially DOA for all but trivial use cases :(

    January 8

Our Sponsors

People in this
Meetup are also in:

Sign up

Meetup members, Log in

By clicking "Sign up" or "Sign up using Facebook", you confirm that you accept our Terms of Service & Privacy Policy