Messages

It seems that big words ruin the text-wrapping:

Fantastic! 

Some few future suggestions that just occured to me:
- Allowing the game author link to more than one screenshot and having a gallery in the game page instead of one screenshot.
- Allowing to link to a trailer and have it embedded in the game page.
- Adding a 'talkie' checkbox when adding a game, and then allowing to search for 'talkie' games.

I agree with Narushima.
Even if there is no new position, but there is still an unfilled position and a lot of time has passed since the last post, the author should be allowed to bump and remind people imo.
I don't see anything wrong with this as long as it's not bumped every day...
Maybe allow one bump per month?

Ok, let's do it. But someone should decide what to merge and what not to. Stuff like the dark theme and my test filters might not be to everyone's tastes.

Actually I was thinking of an xml file where you can set the theme yourself. This way people could create and share themes. But since you don't have the time/energy (I know that feeling too well  ) to make it optional, it's better to leave it out. As for the filters, they are optional, right? If so, I see no reason to not check them in.

Man, I wish I could come this year too..  :'(

Have fun, guys!

I love it!

It seems that the

Spoiler

spoiler

[close]

tag has stopped working.

Tips for beginners:
1. Watch the video tutorials.
2. Read the manual.
3. If you have a problem, first search in the manual. If you don't find an answer search in the forums. Most of the questions that beginners have were already asked and answered. Only if you don't find an answer in the forums post your question in the beginner forum.
4. Most important of all- start small. Make a small game at first, something you can finish in 1-2 months. Some people can start with their epic game and actually make it, but most people will give up and that's a shame. Making a small game first and getting feedback on it will teach you a lot, and it's a lot better to make your beginners' mistakes on a small game and not on a large game where it's a lot harder to fix. I've started 3 years ago (I think) and I still only make small games and learn new things each time.

Darth, can you create a blue cup in a wedding dress?
This way I can ask your hand in marriage!

I could enforce the use of an enum for directions (eDirectionUp,eDirectionLeft...), but then there could be people doing weird custom things.
Or screw them ?

An enum will make the function more intuitive, so I vote for that. Whoever wants to do weird custom things could just use two commands.

But now that I tried again I noticed another problem, scintilla seems to occasionally break (no formatting, no lines and with an asterisk even though it's not modified) when moving the pane onto different places, did that ever happen to you ?

Was that with the latest version? It did happen to me, but I thought I fixed it...

Do you mean the official codebase or mine own on github ? I wanted to sort out this little dilemma about changeroom before committing.

The official codebase. I don't see the reason for having another repository.

Well, I wouldn't make it crash for ChangeRoom  in debug mode, because it can be used for any character and there is no reason for every one of them to have all the loops, but for other cases yeah.

Yeah, but if someone wrote cEvilDoctor.ChangeRoom(..., evilDoctorLoop) and there is no evilDoctorLoop, you'd want the user to know that he made a mistake. If you don't crash on debug and just do nothing, he might not realize why his evil doctor doesn't animate properly. He'll figure out eventually that evilDoctorLoop should be 4 and not 5, but you can save him some head scratching by showing him the error.

p.s: How's your editor with docking panel version coming up ? I remember trying it  while ago and the title of panels were unreadable when unfocused.

I've worked with it on my last game (9 months in) and fixed all the bugs I found. Nobody reported the bug you found and I don't remember seeing it. I just re-checked and it looks fine to me. If you can get latest from svn, and check if you still have this issue so that I could fix it (send me a screenshot), I'd appreciate it.

And while we're on the subject, do you intend to check in your changes to the codebase? It would be a shame if you don't...

That is a very good question. I think there needs to be a decision regarding how AGS handles run time errors caused by the user, and then add it to the guidelines document (when such a document exists), so that all developers could keep consistent engine behavior.

In my view, if in debug mode, then the game should crash with an appropriate error message. If not in debug, then write the error to file (like the 'sprite not disposed' error) and try to overcome it (in your scenario, the first loop if one exists or nothing).

Finally!
I've been waiting for this game my whole life! 

Those past few month have been incredible!

All that's missing is Ken&Roberta coming up with a new game...

Great stuff! 

A few comments:
1. Is there a way to not show games with broken images on the front page? It kinda ruins the look.
2. When you click on a developer to see other games from him/her, there is no separation between games which the developer is the author of, and games in which he/she contributed to. If no separation, I'd at least put the author's games first. Also I think that the highly rated games should be put first, so that at a quick glance I'd be able to get a taste of that dev's best work.
3. The dev team comments are colored in red. Maybe a different choice of color? The red makes it look like an error.

I'm lovin' it! 
I agree with monkey, a "feature request" sub-forum is needed, otherwise where would you post it? Bug reports? Technical?

I have actually been keeping my eye on the Haxe NME project for a long time. The amount of supported devices is incredible, and it's being actively developed.

I'm planning on at least trying to create an adventure game library for that this year, we'll see how it goes...

#7, don't ever, EVER restrict a player from playing how they want to play.

When you create a game, you define a set of rules. Those rules do restrict the player and thus shape the experience that the designer wants to convey. Determining when the save is allowed is just one of those rules.

I like 7. If people like a challenge, they'll try without 'save-game-cheating'.

I don't think that's true.
I think most people will "cheat" if given the option, we are humans after all (and it's not really cheating since it's permitted by the game rules, it's just playing in a way that the game designer did not intend to). A player who wants to succeed will do whatever possible to achieve success, even if it means ruining the fun for himself.
It's up for the designer to do what he can so the experience he aimed for will remain intact.

I've ruined myself plenty of games in the past, most memorable was levelling up too quickly and early in Final Fantasy games, thus making the game very easy and boring.

As for what option is best, if you had unlimited budget I'd say try several options with different play testers and see what works the best...
If I had to choose one of them, I'd go with #2, seems the most reasonable to me.

is there anything else people are needing from me?

Sub-forum(s) for editor and engine development.

It's interesting you mention that it was a "known theme", are you referring to the story or rather the gameplay?

I was referring to the story, the "computer takes over" theme was done a lot, and even the

Spoiler

"computer falls in love with its creator"

[close]

theme was done a few times (I just recently watched a terrible b-movie with that theme).

Great to see s7 pushing forwards, and reaching out to the community in the process.
Small question: will you be offering or considering non exclusive deals as well (with bigger percentage for you, of course)?