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)
SCRIPTS AREA SUGGESTIONS
Posts
Pages:
1
TDS
1453
TDS
View playlists
CloseSome suggestions for the scripts area.
- Allowing the submission of multiple scripts per page. This would help a lot
with scripts that are segmented or have add-ons that not everyone will
use or are add-ons dependent on other scripts like compatibility patches.
- Naming the scripts "View Scripts code" button if the above suggestion is implemented.
This would help a lot to differentiate the scripts by name.
- Adding a "Allow User Demo Submissions" and "Allow User Bug Fixes/Patches" option. This should be
self explanatory, but this would allow user if the person submitting the code allows, to
submit their own bug fixes/patches to the script or make demos/examples for the script.
- Add a view counter. A lot of people don't post on scripts unless they find a problem with it.
This means that scripters have to gauge interest in a script based on how many views it has.
Interest in a script helps determine which scripts and features people tend to like more and
this helps them focus their time and work into those scripts and features instead of working
on a script no one cares about. And since it's rare for people to post or sign up for a forum
just to show support, the view count is the next best thing to get that information.
- Adding a custom page to profiles where people can post, like the ones in projects. I would personally
use this to take script requests or general scripting questions. I know PM's exist, but answering the
same questions 10~15 times about a script or problem can be very tiring and having a place where I could direct people could answer a lot more questions faster.
- User Resource subscription. Not really vital, but it would be nice to be able to receive notifications
when people upload their resources like scripts, articles, tutorials etc.
- Allowing the submission of multiple scripts per page. This would help a lot
with scripts that are segmented or have add-ons that not everyone will
use or are add-ons dependent on other scripts like compatibility patches.
- Naming the scripts "View Scripts code" button if the above suggestion is implemented.
This would help a lot to differentiate the scripts by name.
- Adding a "Allow User Demo Submissions" and "Allow User Bug Fixes/Patches" option. This should be
self explanatory, but this would allow user if the person submitting the code allows, to
submit their own bug fixes/patches to the script or make demos/examples for the script.
- Add a view counter. A lot of people don't post on scripts unless they find a problem with it.
This means that scripters have to gauge interest in a script based on how many views it has.
Interest in a script helps determine which scripts and features people tend to like more and
this helps them focus their time and work into those scripts and features instead of working
on a script no one cares about. And since it's rare for people to post or sign up for a forum
just to show support, the view count is the next best thing to get that information.
- Adding a custom page to profiles where people can post, like the ones in projects. I would personally
use this to take script requests or general scripting questions. I know PM's exist, but answering the
same questions 10~15 times about a script or problem can be very tiring and having a place where I could direct people could answer a lot more questions faster.
- User Resource subscription. Not really vital, but it would be nice to be able to receive notifications
when people upload their resources like scripts, articles, tutorials etc.
- Allowing the submission of multiple scripts per page.
-- this would require a division between a SCRIPT ARTICLE, and SCRIPTS, where an SCRIPT ARTICLE can have ONE TO MANY SCRIPTS
-- also, allow scripts to upload a demo/download instead of posting a script.
--two people now have asked for this change in the recent past, so I will see if I can add it.
- Naming the scripts "View Scripts code" button if the above suggestion is implemented.
-- Button label to change to SCRIPT NAME; only if the above can be implemented
- Adding a "Allow User Demo Submissions" and "Allow User Bug Fixes/Patches" option.
-- ummm, not sure about this. Can't they post in the comments? I doubt I will implement this.
- Add a view counter. A lot of people don't post on scripts unless they find a problem with it.
-- ADD view_count
-- consider adding a view_count to BLOGS, ARTICLES, UTILS
- Adding a custom page to profiles where people can post, like the ones in projects.
-- make a thread in PROGRAMMING & PLUGINS, and sub to the thread. I won't be adding custom pages to user profiles anytime soon.
- User Resource subscription. Not really vital, but it would be nice to be able to receive notifications when people upload their resources like scripts, articles, tutorials etc.
-- SUBSCRIBE TO USER
-- would be part of a revamp to subscribe to more things; generalized notices
-- I have been mulling on how to generalize the subscription system here at RMN. Right now you can sub to games, and events (I think) and now threads, but adding the ability to sub to users and engines is under consideration.
Pages:
1
