Alexander Morou
Sponsor
Well harbino,
Typically things like that are non-request offerings. If they want you, you'll know. Support, Report and Redefine.
Since you're not a moderator, or support staff. Assist within the rules as they are, but don't do it because you want a title, do it because you think it needs done. If you see someone causing a problem, report it to a moderator, don't mini-mod or continue the flame, let the people who need to know, know. Redefine what the community is, don't suggest things be changed, go about doing it within the rules. If a certain area could use this or that, do your part to make it be. Here's an example. Lets say you see a popular RGSS script, based upon popular response and so forth. You'd probably bookmark or otherwise archive it in some way. You repeat this process a few times, and by the time a few months have passed you have a fair collection. Compiling this collection for the community, about the community, would be helpful to a certain degree. If there's a need, you could then contact a moderator, discuss plans to create a thread that links to each individual script, providing a synopsis (in your own words) of the scripts functionality. Such a thing has already been done in the Script Analysis Forum, under the Forum Script Listings (somewhat outdated according to the topic title). This is just an example off the top of my head. If you see something about the community that could be changed, and there's a viable way to change it, do it, don't think about doing it, and do it because you genuinely want to help.
Now the entire above rant can be ignored if you were making a lame joke.
Typically things like that are non-request offerings. If they want you, you'll know. Support, Report and Redefine.
Since you're not a moderator, or support staff. Assist within the rules as they are, but don't do it because you want a title, do it because you think it needs done. If you see someone causing a problem, report it to a moderator, don't mini-mod or continue the flame, let the people who need to know, know. Redefine what the community is, don't suggest things be changed, go about doing it within the rules. If a certain area could use this or that, do your part to make it be. Here's an example. Lets say you see a popular RGSS script, based upon popular response and so forth. You'd probably bookmark or otherwise archive it in some way. You repeat this process a few times, and by the time a few months have passed you have a fair collection. Compiling this collection for the community, about the community, would be helpful to a certain degree. If there's a need, you could then contact a moderator, discuss plans to create a thread that links to each individual script, providing a synopsis (in your own words) of the scripts functionality. Such a thing has already been done in the Script Analysis Forum, under the Forum Script Listings (somewhat outdated according to the topic title). This is just an example off the top of my head. If you see something about the community that could be changed, and there's a viable way to change it, do it, don't think about doing it, and do it because you genuinely want to help.
Now the entire above rant can be ignored if you were making a lame joke.