Editing WarioWare: D.I.Y.
From the Super Mario Wiki, the Mario encyclopedia
Jump to navigationJump to search
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 251: | Line 251: | ||
When the [[Wii]] was developed, various Nintendo departments held meetings to discuss the new console. Abe was the representative of [[Nintendo Software Planning & Development]] and learned that the Wii and DS could exchange data via [[Nintendo Wi-Fi Connection]]. This information inspired him to build on his previous pitch.<ref name="Iwata Asks"></ref> | When the [[Wii]] was developed, various Nintendo departments held meetings to discuss the new console. Abe was the representative of [[Nintendo Software Planning & Development]] and learned that the Wii and DS could exchange data via [[Nintendo Wi-Fi Connection]]. This information inspired him to build on his previous pitch.<ref name="Iwata Asks"></ref> | ||
Following the completion of ''[[WarioWare: Smooth Moves]]'', Goro Abe shared his idea with fellow SPD 1 employee [[Takumi Hatakeyama]]. Hatakeyama was interested in the pitch as he had fond memories of creating content on | Following the completion of ''[[WarioWare: Smooth Moves]]'', Goro Abe shared his idea with fellow SPD 1 employee [[Takumi Hatakeyama]]. Hatakeyama was interested in the pitch as he had fond memories of creating content on [[Mario Paint]], despite sharing Abe's inability to focus on completing longer, more involved content.<ref name="Iwata Asks"></ref> Goro Abe also invited [[Intelligent Systems]] employee [[Taku Sugioka]], who too was interested in the idea, but he was unsure of the feasibility of the project.<ref name="Iwata Asks"></ref> | ||
The team decided to base the music and drawing tools on ''Mario Paint''. As there was no template for the game content-creation aspect, the developers felt it was the aspect that was the hardest to implement – according to Abe, half of the game's 2-years development cycle was spent on experimenting to create an approachable editor.<ref name="Iwata Asks"></ref> It was eventually decided that microgame creation would be split into three components: "objects" (moving sprites), "background" (static graphics) and "sound". To integrate the sound and graphic creation tool in the game editor, the development team created a test model which surprised them with its efficiency when a designer with little programming experience was able to make a game within a few hours.<ref name="Iwata Asks"></ref> | The team decided to base the music and drawing tools on ''Mario Paint''. As there was no template for the game content-creation aspect, the developers felt it was the aspect that was the hardest to implement – according to Abe, half of the game's 2-years development cycle was spent on experimenting to create an approachable editor.<ref name="Iwata Asks"></ref> It was eventually decided that microgame creation would be split into three components: "objects" (moving sprites), "background" (static graphics) and "sound". To integrate the sound and graphic creation tool in the game editor, the development team created a test model which surprised them with its efficiency when a designer with little programming experience was able to make a game within a few hours.<ref name="Iwata Asks"></ref> |