I think it's about time that we set down some 'procedures/rules/techniques' about what we expect in a klik game. Basically, it's things that everyone expects to see from a klik game. It's common knowledge. It's the little things that both noobs and experts miss and we hate them for it. It's the little things that everyone should know just to. So I want to write an article about this and I'd like for you guys to add to it as well
1. Don't use installers.
2. Instead of using a RAR, make it a ZIP file. That way, people don't need winRAR to open it.
3. The minimum timer counter should be 0.03 seconds (as of MMF 1.5, I have to recheck it with MMF2 to see if it still applies)
4. If you're going to use INI files, put them in the same folder as the game. Not the Windows folder! If you really want people not to read it, encrypt it.
5. When testing your game, try to keep the maximum amount of objects at 500. Always keep the frame rate above 30!
Edited by an Administrator.
Disclaimer: Any sarcasm in my posts will not be mentioned as that would ruin the purpose. It is assumed that the reader is intelligent enough to tell the difference between what is sarcasm and what is not.
1: Never, ever, under any circumstances, use an installer
2: WinRar does not exist to us, and your .rar file is about as useful as a load of turds on my desktop
3: Just don't use timer events for anything, really. Use values and counters, please!
4: $appdir goes a long way, folks!
5: Make that 40 frame rate.
Originally Posted by Matt Gayles No ball shaped characters. It's so noobish. Give your character a head and a body.
And anything with Blob in the title is really unoriginal.
Kirby doesn't like your opinion.
-
Deleted User
9th June, 2008 at 01:22:10 -
Kirby wasnt made by in amatuer using klick team products in 2008. It was made by pros in 1993. Thats 15 years. The trend needs to die. Unless you add some really good rolling animations your circle dude just looks lazy. No offense Pixelthief. Im sure your blob game is awesome.
Even I made one a long time ago. It was called bill the blob.
It's less related to making the games and more related to posting it here, but writing up a good description needs to be something people start doing.
It's not that hard to make a nice looking paragraph or two out of even the most simple of games.
1. I will continue to use Rar files so more people can download my game before my server cuts me off
2. Games need good instructions. Too many supernaff text files that just tell you the important things. Give us HTML manuals!
Limit objects to 500? Hmm! I'm running up to 700-1000 objects and I haven't got Tormi to drop below 55fps on my machine (just a 2ghz C2D). Speed set at 60fps. It's a very optimised engine though.
Originally Posted by Dr. James 1. I will continue to use Rar files so more people can download my game before my server cuts me off
2. Games need good instructions. Too many supernaff text files that just tell you the important things. Give us HTML manuals!
Limit objects to 500? Hmm! I'm running up to 700-1000 objects and I haven't got Tormi to drop below 55fps on my machine (just a 2ghz C2D). Speed set at 60fps. It's a very optimised engine though.
Good point, but I don't see why you can't use ZIP instead of RAR. And you can host it on googlepages or some other free host. I think the frame rate is more important than object limit, so I take away point 5.
Disclaimer: Any sarcasm in my posts will not be mentioned as that would ruin the purpose. It is assumed that the reader is intelligent enough to tell the difference between what is sarcasm and what is not.
Yea frame rate (or rather a consistent frame rate) is ultra important to me, I worked my bum off to get the lowest FPS rate to 55. It might be slower on older systems but thats where graphic limitation options kick in.
And I don't want to use external hosting. It likely wont, but what if in a few years Google is gone but all my pages still link to that file? I like everything self contained in 1 place, and for £75 for 2 years hosting it's almost pennies.
Originally Posted by Dr. James 1. I will continue to use Rar files so more people can download my game before my server cuts me off
2. Games need good instructions. Too many supernaff text files that just tell you the important things. Give us HTML manuals!
Limit objects to 500? Hmm! I'm running up to 700-1000 objects and I haven't got Tormi to drop below 55fps on my machine (just a 2ghz C2D). Speed set at 60fps. It's a very optimised engine though.
Good point, but I don't see why you can't use ZIP instead of RAR. And you can host it on googlepages or some other free host. I think the frame rate is more important than object limit, so I take away point 5.
That's because Dr. James has stock in WinRar!
--
"Del Duio has received 0 trophies. Click here to see them all."
"To be a true ninja you must first pick the most stealthy of our assorted combat suits. Might I suggest the bright neon orange?"
DXF Games, coming next: Hasslevania 2- This Space for Rent!
Have a tutorial! I hardly ever read readme's because no-one wants to read before a game - tutorials are nice but only if they're skippable etc.
I'd say the most frames you ever want to lose is 5 to 10 in testing because SOMEONE out there will have a worse PC than you even if yours sucks. Also, custom controls and joystick/joypad/whatever you guys call 'em support!
Max objects isn't a real indication of slowdown unless they're all on screen at once - I don't ever go over 300 unless it's for a super special purpose. Processing that many objects (if they have lots of events etc) is where slowdown hits big time.
Originally Posted by Del Duio
Originally Posted by Pixelthief 3: Just don't use timer events for anything, really. Use values and counters, please!
Aw, they're not THAT bad, depending on where they go, or what they're for.
Yes, they are. Only use them if your game never drops a single bit in fps or if you're doing things that need to be in real time increments.
Originally Posted by Muz I think it's about time that we set down some 'procedures/rules/techniques' about what we expect in a klik game. Basically, it's things that everyone expects to see from a klik game. It's common knowledge. It's the little things that both noobs and experts miss and we hate them for it. It's the little things that everyone should know just to. So I want to write an article about this and I'd like for you guys to add to it as well
1. Don't use installers.
2. Instead of using a RAR, make it a ZIP file. That way, people don't need winRAR to open it.
3. The minimum timer counter should be 0.03 seconds (as of MMF 1.5, I have to recheck it with MMF2 to see if it still applies)
4. If you're going to use INI files, put them in the same folder as the game. Not the Windows folder! If you really want people not to read it, encrypt it.
5. When testing your game, try to keep the maximum amount of objects at 500. Always keep the frame rate above 30!
Edited by an Administrator.
1.Agree
2.LOL! Winrar is 10 sec download and 1 min install... Last time I used .zip files was, when I had windows 3.2. That time .zip files were good, but not anymore
3.I prefer trigger objects more accurate
4.Roral agreement, but nowadays I havn't seen them in games.
5.Classic framerate is 32, because then you can't see so darn big lag.
I have proven new mathematic formula to be true...
I was hoping that you guys would add a 6,7, etc to it. Oh well
To comment, WinRAR can open ZIP files, but Winzip and Windows can't open RAR files. WinRAR also makes perfectly fine ZIP files. Obviously you can download it, but that means that people who don't have winrar would just toss your game in the recycle bin because they're too lazy to do a search for WinRAR. Serves you right for being too lazy to click on the ZIP option instead
I'd disagree on timers. I find them to be the most reliable method if combined with counters. Frame rates will bounce up and down throughout the game. ED, heck all the Blackeye Software games used extensive amounts of Always events and as such, I was able to beat ED's bosses by slowing down the computer. Also many of the earlier BES games were unplayable when computer speeds reached 1000 Mhz. A good Always event now could be ridiculously fast in 4 years. That's sloppy coding Timer events may run a little with a dip in frame rates, but if you made your game properly, there shouldn't be any dip in frame rates!
6. Avoid putting transitions in every frame just because you can. If you REALLY have to, keep them short, below 5 seconds.
7. Avoid using library objects, musics, etc. Sound may be forgiven. Why? Because everyone has seen them. Using a single library graphic is as ugly as a movie using a stunt double.
8. Don't use the built-in MMF random generator. It is not completely random. You'll find it skipping some numbers and leaning towards others.
9. On your first game of a certain type, don't be too ambitious. Focus on finishing the game as fast as possible. By the time you finish it, you'll learn a great deal of things about creating that type of game, including what shouldn't even be there. Then you create the sequel properly.
10. It's tempting to use editors, but don't rely on them. As 9 above, editors are better used in a sequel, once you figure out which variables you've overlooked and which were redundant. Also, editors are very inflexible.
Disclaimer: Any sarcasm in my posts will not be mentioned as that would ruin the purpose. It is assumed that the reader is intelligent enough to tell the difference between what is sarcasm and what is not.
Advertisement
Post Reply
Edited by an Administrator.
