rpg.  no doubt.  or just a simple character wandering around in a single simple level, doing whatever.

Actually I would love to see something like that too, however devil may cry, onimusha may be a bit too much, starter kits are supposed to be simple and easy to understand.

However a simple hack and slash game (specially one in 3d, since is really too easy in 2d) could be a great starter kit for all kind of projects. RPG, Adventure, Beat em up, even fighting games.

All we need is a character walking in an eternal plain and beating another single character (a giant ant per example) if the guy has two attacks (fast, strong) that would be enough code to add any number of attacks. and with just 2 characters (minion, boss) we could have a large number of enemies.

Somthing I think would be cool as I see it as the one of the future technologies in games is synthesized character animation. It would be cool to have a sample that covers that. However, I don't think it would end up being feasible as I believe it is a far larger subject to cover then I can fully grasp.

For those unsure what synthesized movement is. You will see in the new GTA game. To my knowledge they are not using any caned animations.

Vangald:

Somthing I think would be cool as I see it as the one of the future technologies in games is synthesized character animation. It would be cool to have a sample that covers that. However, I don't think it would end up being feasible as I believe it is a far larger subject to cover then I can fully grasp.

For those unsure what synthesized movement is. You will see in the new GTA game. To my knowledge they are not using any caned animations.

That would be better covered in a sample or article. It wouldn't make much of a starter kit, since the idea of a starter kit is to give a starting point for a game.

 

Ah. Yeah. Good point.

Any idea how far the old style rpg starter kit is progressed? If it has been started anyway ;)

It's looking good. We got to see it in action at the MVP Summit. It'll be interesting to see what people do with it.

Wow, great thread.  I'd like to summarize some of the popular requests / comments:

• Starter kits should be simpler in architecture (as relative to the "thing" they are starting)
• Demonstrate core concept(s)
• Easy to build on and extend
• Perhaps not a "complete" game?  That is, maybe not provide all the robustness code that a complete game needs? (Menus, profile checking, signing in and out, storage, options, save games, pause menu, etc).
• A more functional project template would be good (but different than a starter kit)
• Each starter kit should focus on a particular game style
• Game styles requested
• RPG (coming soon!)
• 2D Platform (Lode Runner, Mario, Metroid, etc)
• 3D "shooter" (either first person or third)
• RTS-ish
• Animation is still a topic that needs to be better explored.

Anything else?

Starter Kits should use the sample code you provide in the education section. Once people understand (for example) the GameState sample then they know how it works in ALL the starter kits instead of having to work it out. Same for particles or instancing etc.

 

So should all samples have an eye towards how they can be used together or in a starter kit?  Will this lead to feedback on the samples becoming too cluttered (as it will most likely take some amount of code that isn't directly related to the topic the sample is focused on).

Is there another category of materials that are closer to "components" (be they GameComponent or not) that are directly intended to be building blocks for a game?  I'm not sure I agree that samples should be building blocks, although a successful sample should allow the user to implement the concept in their game.

 

 

If a starter kit is purely an example of waht can be done then do whatever each author needs.

If they are supposed to be learning tools then the gap between the example code and the kits is too big today. If segments of each game were consistent then it would go a long way to bridging that gap. Using bits from the other samples would be a good way of getting some consistency. I don't want everything included if its not needed but all games need some menus and game state so if that all looked the same or similar we could basically learn it once. Right now you have to learn every line of every kit to get anywhere significant.

I'd like to see some of the starter kits focus more on game style instead of common programming tasks (such as menus, etc.). It'll be great if samples such as the GSM were wrapped up into an application building blocks and just referenced from the other samples instead of including the GSM code in the other samples, that way the sample's code doesn't get overwhelming when it includes the same code as other samples. Instead of including all of the GSM code, just use a GSM library and reference those libraries instead.

By turning things like GSM into application building blocks, it'll be easier to integrate into other games (while still giving the source code for those of us that want to tweak it). That also helps keep everything consistant across the kits and samples and keeps the focus of the samples on a particular topic instead of adding in all of the code of all of the other samples.