On Halloween of 1994 Nintendo filed for a series of patents that were later granted between the years 1997 and 2000. This essay refers to them more homogeneously as “Mario Factory” (Hibino and Yamato, 1994; Yamato et al., 1994a; Yamato et al., 1994b). This sequence of documents describe a videogame development, testing, and manufacturing system designed specifically for hobbyists and users to enjoy the creative possibilities of developing games for console videogame systems. Many of the systems and ideas described in the documents have not yet come to market for licensed Nintendo game developers and certainly not for the general player or hobbyist game developer.

Mario Factory, at its core, was about creating, not only the possibility of (co)creative content creation for console video games, but an entire set of tools by which users could begin (co)creating games. Figure 1 depicts a splash screen from this hypothetical device. While the patent seems to specifically target less technically inclined would-be videogame developers, it was also stated that these same tools would prove as productive prototyping and testing systems for more experienced videogame developers.

This invention relates generally to a method and apparatus for generating unique videographic computer programs. More particularly, the present invention relates to a video game fabricating system designed primarily for users who are unfamiliar with computer program[ing] or video game creating methodology. Such users may conveniently create a unique video game through and icon driven, interactive computing system that permits a video game to be executed, stopped, edited, and resumed from the point where the editing began with the editorial changes persisting through the remainder of game play.
…
In accordance with the present invention, unique video games may be simply created by users ranging from a relatively unsophisticated elementary school students to sophisticated game developers. A unique hardware and software platform enables users to create original games by selecting icons which access more detailed editor screens permitting the user to directly change a wide variety of game display characteristics concerning moving objects and game backgrounds. (Yamato et al., 1994a53)

As early as 1994, Nintendo was critically aware of the complexity associated with videogame development practices and the kinds of interdisciplinary creative collaborative practice that is necessary for success. While their patent hints at perhaps a declining collaboration between engineer, artist, and designer, it seems to be more about creating tools that foster effective collaborative practice between those groups.

Mario Factory was, in effect, a DevKit for the masses. This approach hints at a very different possibility than one that is currently experienced by game developers. DevKits were introduced so that game developers could create games for consoles where the hardware differed significantly from that of PC’s. Nintendo developed technologies to bridge the gap between the PCs, where code was typically written, and the consoles, which ran the compiled code.

Hibino, T. & Yamato, S. (1994). U.S. Patent No. 5599231. Washington, DC: U.S. Patent and Trademark Office. Assignee: Nintendo Co., Ltd.
Yamato, S. et al. (1994a) U.S. Patent No. 5680534. Washington, DC: U.S. Patent and Trademark Office. Assignee: Nintendo Co., Ltd.
Yamato, S. et al. (1994b) U.S. Patent No. 6115036. Washington, DC: U.S. Patent and Trademark Office. Assignee: Nintendo Co., Ltd.

Water Dropplet Guy

So, as you can see I’m playing with water and fire a bit this summer. I’m not entirely happy with the way that the brush system worked out on the little water guy, but all in all not too bad. I’m not sure how well the transparency of the brush has worked, but I’ll get a sense of that in a bit as I start tiling the image on the screen. The next component of what I’ve done is create feet and animations of those feet and assembled them into PNG files which can then be animated on the screen. I’ll post these assembled PNG files next. Once I’ve done one set of animations, I’ll work on some other poses for each fo the water/fire characters.

Again, I used similar methods for this drawing, though the real experiment was in determining how to use the brush system of Pixelmator, which for a geek like me was probably more fun than it ought to have been.

I am assembling these together in a simple little iPhone/iPod Touch application while preparing a syllabus for an iPhone class based heavily on the Stanford iPhone class, though our emphasis will be more on the technology and design for it than the particularly computer science focus of the Stanford course.

Playing with Fire

I have already drawn several other little characters for some of my game concepts, unfortunately I’ve taken my sweet time getting them posted online. In part I’ll blame it on just being busy at the end of the semester and my trip to Iowa to see my little sister graduate from high-school.

In the mean time, I’ve been playing a great deal with Lineform, Pixelmator, and my Wacom Bamboo tablet. I continue to use Scribbles a bit, but for what I’m attempting to do, it just doesn’t seem to do the trick. I really like being able to use a vector graphics program to do my line art and then color. Scribbles does not allow me to import an image, so I cannot color something in created in another application. Now, this isn’t spectacular stuff that I’m creating. It is just my attempt as someone with no training to try and get some of my ideas and the visions in my head into my computer such that I can begin using them to prototype game mechanic prototypes. The first set of little images are fire and water characters.

I am currently enamoured with simple 2D games as they can seemingly be more compelling to a wide range of audiences. They also seem to express more clearly some of the design mechanics one is attempting to express in a given game. More images shortly as they come along.

Thus, began my new experiment. I started thinking about how much time I invest in the tools that make me a better programmer, designer, writer, etc. What I realized was that I had not put much time or energy into the tools and software that I was using to create art. I use Mellel for writing, TextWrangler for many text editing things, Versions for SVN management, Omnigraffle for diagrams, Bookends for bibliographic and research material, Evernote for research and archival, ScreenFlow for software demonstrations, and even a special program for using Gmail, Twitter, etc. Now, I will cut myself a bit of slack, because I long ago invested in Pixelmator for image editing, but I use only a fraction of its capabilities.

So, I have begun testing out graphics creation and editing tools. Some for bitmap graphics, some for vector graphics, etc. But I’ve also invested in a small “Bamboo” Wacom tablet. It only makes sense to invest in my tools, right? I ought to pay as much attention to how I’m going about creating graphics as I’m going about selecting a new graphics library. So, I’m going to document the process here. Now of course, I’m tweaking things a bit here. Obviously based on the above software selection, you can tell I don’t immediately go for the Microsoft/Adobe solutions, but I try to support independent developers first. Often I find much “sharper” tools as I term them.

So, first on the docket are a selection of indy graphics tools before I launch into those “other” programs, unless I find the cat’s meow first!

• Game Salad – This seems to be an actual release of something similar to the long promised Stencyl application. I have been looking for system like these GameMaker that allow you to quickly mock up 2D game prototypes. Of course one of the major sticking points with all of these applications is that they are not cross platform in many cases.
• Lost Garden (Danke’s Numerous Artistic Contributions) – The numerous freely available graphics that Danke has shared with the independent community are awesome, and I can’t really thank him enough for doing this sort of thing. My students have made some use of these tile sets. I on the other hand, use them all the time to mock up designs.
• IndieLib and Pieced Image Map Editor – IndieLib is a new find for me. I’ve spent a significant amount of time as the OS X lead on G3D, a cross-platform game tech/engine. Lately I’ve had more need for something like G3D, but 2D. IndieLib seems to have found a kind of critical mass of independent game developers interested in working on the library, so I’ve begun looking at what it will take to bring it to OS X. To this end, I’ve been focused on making it as friendly as possible with Quartz Extreme, which would give a 2D library the biggest spread of support from graphics cards on OS X (including those integrated Intel cards).
• FlashDevelop – Flash Develop is a kind of sideline interest. Open Source Flash development seems to be a growing interest for many. I am no exception. I have no love for proprietary software like the Adobe Creative Suites, but Flash certainly is a growth area, so figuring out how to support developers interested in Action Script and Flash is something I have spent a great deal of time with lately.
• Löve – Löve is also a love/hate/hate-love thing I have going. I’ve been using a great deal lately to prototype my own game concepts. So I love it. At the same time, I’ve encountered several strange things related to the underlying Lua language, which I hate. At the same time, some of the things I hate are actually kind of growing on me. Hmmm…

I wined a few weeks back about being unable to register on the PopCap Developer Forum so that I could download the PopCap Framework. Post GDC this announcement came out, which seems to indicate that the project is being scrapped by PopCap, but released into the wild at some future point as an Open Source Software project. This is partially why I decided to throw my hat into the IndieLib ring.

All in all I’m only now beginning to put this list of resources into a more readable format. Yes, there are numerous libraries, tools, etc not listed here, but that is part of the ongoing project. Given that my development resources and prototyping tools bookmarks have nearly 100 items in it means I have only scratched the surface.

Forbidden
You do not have access to this page.
You must be logged in to developer.popcap.com before downloading files

To which I dutifully clicked the “Register” link, which returns the following:

Sorry, registration has been disabled by the administrator.

I’ve sent several messages through the “contact us” link with no reply. I have found the alternative Tuxcap port of the library, but it is a little sad to see such a great community boon lost to the non-responsive industry ether that pervades in many cases. Of course I can’t ask the question on the Popcap developer forum because registration is closed. Thus I cry my tears into the Internet ether.