1. I think most challenges should be open to whatever language, framework or game engine.

2. If it is very specific regarding a game engine, it should be very well justified.

3. Even with a good justification, it should be remembered that not everyone will be willing to download a bunch of dependencies to get in the challenge. For example, I wouldn't be willing to install JDK or Mono.NET. IF you are going to make a challenge that requires a specific dependency, at least chose a very easy one to get. Lua and Love2D are examples of extremely easy dependencies to install, and very lightweight.

1 minute ago, MarcusAseth said:

So yeah, I agree with you it depends on the challenge, what I was thinking was to not mix them in the same "Make X Game" challenge.

Agreed. "Make X Game" is clearly something focused on design and creative. No reason to mix.

Challenge is on!

I will probably use SDL2 to make the game (I thought about using my own engine, but it's probably not that portable yet).

I don't see this discussion thread, either. Maybe was deleted. But I think we can talk here, anyway.

2 minutes ago, MarcusAseth said:

As I already said (probably more than once) I don't think "make X game challenge" should be made into challenges with deadlines if begginners participation is to be expected, for instance one of the requirements is:

The deadline is more of a challenge than a requirement for submission. I think that's what is going to be for every challenge.

6 minutes ago, MarcusAseth said:

And I never did AI an have no idea about where to start, so that's why my idea of challenge was something of smaller scope with more focus on stuff like having the game framework already done and just make the behaviour AI part

I will update the post with a link for some youtube tutorials regarding AI.

I added this these topics:

Quote

• Enemy behavior can involve:
  • Response to the environment. What is the kind of tile that the enemy is currently at? What are the kind of tiles that are in front or behind the enemy?
  • Response to the player. Where is the player? Is it too far away? Is it close? In front or behind? How the enemy will respond to that?
  • Motion pattern. Does the enemy walk on the platform and stop for some time? Does it fly? Games like Super Mario World are good examples with a great variety of enemy patterns.
• The tutorials on Youtube by Shaun Spalding teach some enemy programming. They are for Game Maker, but the logic can be translated to other game engine or framework:

" rel="external">

" rel="external">

" rel="external">

I got a window working on SDL2 and the main loop.

I'm writing the structures before jumping into logic.

I will be updating my challenges here: https://github.com/ferreiradaselva/very-small-games

The structures.h file has all the structures that I have (and will have) in the game.

... Now I'm going to watch some Adventure Time.