Full Games List
Featured Games
New Games
Reviews
Media
Images
Blogs
Game Updates
Images Feedback Summary
Game Design Highlights
Tutorials
Articles
Scripts
Utilities / Plugins
Resources
Engines
Engine Bulletins
What is Makerscore?
Past Events
Achievements
Misaos
Forums
Post History
Chat
New to RMN?
Full Store List
RMN Music Pack (free)
ARTICLES: WHY THEY ARE NEGLECTED AND WHAT YOU CAN DO ABOUT IT.
Posts
Neophyte
155
Neophyte
View playlists
CloseI have no ideas but I like articles and I have many planned in my head. I don't really like requests though because the request might be something you have little knowledge of.
Also, I think in-game tutorials work very well too. Instead of explaining how something works through text, there is always the option of showing how it's done through an example game. Just an idea for some of you.
oops I just realized I said I have no ideas and then gave an idea. How smart of me.
Also, I think in-game tutorials work very well too. Instead of explaining how something works through text, there is always the option of showing how it's done through an example game. Just an idea for some of you.
oops I just realized I said I have no ideas and then gave an idea. How smart of me.
What I do is comment all of my common events and most of my algorithms in the code (for my own reference and karsu's, if need be). If somebody wants to learn how something's done, crack open V&V and take a look.
post=101441
I don't really like requests though because the request might be something you have little knowledge of.
You can always say 'Sorry, I don't know how to do this.' Chances are someone else does, though!
post=101443
What I do is comment all of my common events and most of my algorithms in the code (for my own reference and karsu's, if need be). If somebody wants to learn how something's done, crack open V&V and take a look.
Yes, because your game's common event code is as easily accessible as a big huge link on the nav bar.
post=101443
What I do is comment all of my common events and most of my algorithms in the code (for my own reference and karsu's, if need be). If somebody wants to learn how something's done, crack open V&V and take a look.
/me sighs.
I don't recommend this on any level.
I didn't say it was a substitute for an article! I was continuing Neo's thought about in-game tutorials.
I can write a tutorial on changing a diaper, burping a baby and bath time, but that's about it at the moment. Any requests for that?
but it feels good man
Just throwing this out there, if someone wants to request some articles on the down low, PM me and I'll see what I can do. However I will get to work on some stuff I had in mind regardless.
Just throwing this out there, if someone wants to request some articles on the down low, PM me and I'll see what I can do. However I will get to work on some stuff I had in mind regardless.
If you're looking for ideas on topics, perhaps this thread could be of use.
http://rpgmaker.net/forums/topics/3952/
http://rpgmaker.net/forums/topics/3952/
Relyt
1242
post=101552
Crazetip: Don't fuck women. They make BABIES come out of their BLOODHOLE.
I wasn't aware Men made babies that came out anywhere else.
Fractal Advocate
1252
Shouldn't this be in Game Discussion & Development or something instead of Game Design & Theory?
post=101601post=101552I wasn't aware Men made babies that came out anywhere else.
Crazetip: Don't fuck women. They make BABIES come out of their BLOODHOLE.
c-section
DFalcon
2141
post=101440
It's far easier for me to write an article about a specific subject if someone asked me about it, than me spontaneously deciding that 'Hey, I want to write an article about X!'. Sure, I don't mind writing either way, but as someone with a full time job/college and other responsibilities/hobbies/life, it's easier for me to zone in on a request than to randomly spurt them out. I don't mind writing just to write sometimes, though. They're not mutually exclusive.
I tend to agree with this. The key part isn't necessarily somebody asking me, but having a specific thing I think I could helpfully write about better than most people here. It's good both to have something to bite into that's not overly general, and to know somebody thinks they could use help on it (if there's one, there are probably more).
LDanarkos
430
Possible article: Comparing and contrasting the various game makers (RM2K, RM2K3, RMXP, RMVX, GM, etc.). Criteria to compare: how many pictures can be shown on the screen simultaneously, which sound formats can be played, what picture resolutions and file formats are allowed, which operating systems can they be used on, what are the limitations of the DMS / DBS, how similar are the commands to the other game makers (i.e. if you already know how to use X, will you immediately pick-up Y, or would you have to learn everything all over aain?), etc. etc.. Make-up your own other criteria, but try to cover all of the most important contrasts.
A topic like that almost seems to me like it should be stickied.
I don't understand why not. This is considered good form in the programming world. Plus, it very well can help a player learn how you did what you did. Although, a lot of times, a system can be so complex that the comments won't give perfect clarity if they're relatively brief (especially in my systems, because my variable names can be confusing, and get used for multiple things).
post=101561
If you're looking for ideas on topics, perhaps this thread could be of use.
http://rpgmaker.net/forums/topics/3952/
A topic like that almost seems to me like it should be stickied.
post=101499post=101443/me sighs.
What I do is comment all of my common events and most of my algorithms in the code (for my own reference and karsu's, if need be). If somebody wants to learn how something's done, crack open V&V and take a look.
I don't recommend this on any level.
I don't understand why not. This is considered good form in the programming world. Plus, it very well can help a player learn how you did what you did. Although, a lot of times, a system can be so complex that the comments won't give perfect clarity if they're relatively brief (especially in my systems, because my variable names can be confusing, and get used for multiple things).
sellout
54
Maybe people read articles, but don't commet?
Maybe people would just rather ask questions.
Maybe people would just rather ask questions.
