MT Framework Directory **DISCUSSION**
Posted: Wed Oct 26, 2011 11:24 pm
WELCOME
We have a directory of what frameworks are available for what systems, the links to get them, and who maintains them (forum ID).
This works quite easily: When a person writing/maintaining a framework has an update whether Framework Name, Link to Framework, or someone taking it over they PM me the info and I update it.
Every item will have a "last updated" so they know what's the latest and greatest.
If I can make it fit and look right, a direct link to the support thread.
Don't worry, the threads about the different Frameworks are not going anywhere - this is a LIST of them all and where to find them. Everything else is working great except the "Where can I find a framework for X" thing.
PLEASE POST DISCUSSIONS IN THIS THREAD
PROPOSED/REQUESTED FORMAT FOR FIRST POST IN AN 'FW SUPPORT THREAD/TOPIC
INTRODUCTION
Subscribing to a thread is a great way to stay on top of new posts, but for any actively updated framework (or infrequently updated) most posts aren't going to be updates - which means users of that FW get to slog through a bunch of posts to find the gems. Someone who is a user of multiple frameworks probably would go nuts
Azhrei and Gamerdude have been discussing something that would be a big help to all current and new users of these forums - and may actually ease up management of updates for the FW authors.
The basic idea is that the initial post of each support thread conatin all the necessary info on the FW, be where updated info is posted (new files etc) - and use a common format. Basically the info to be included is (at a minimum)
Latest (or last few) version of the FW, a change log, Installation Instructions, and upgrade instructions. Of course change log might best be post #2 of the thread, and any of these items the FW author doesn't wish to maintain in a post (like a
GENERAL FORMAT: (followed by an explanation/details)
1. Thread Title/Subject.
2. General Description
3. Link to current FW (or current and last few versions)
4. Install Instructions
5. Update Instructions
6. Change Log
EXPLANATION/DETAILS:
1. Just have the name of the game system, name of the FW and the Major version number. EX: "[Savage Dragons] Joe's Monstrous FW v3". The post can be edited to add "minor version number" on updates and the "date last updated" but that would be optional.
2. Just what it says. A description of the FW in a small paragraph or two.
3. Link. Either the link to where it can be found out on the web OR it is uploaded as an attachment and then use the <ATTACHMENT=X>FW NAME</ATTACHMENT> command (X is the number of the attachment, they are numbered starting with 0).
4/5/6. Put these inside the <SPOILER>text</SPOILER> command and the text will be hidden until the member clicks on the button. To label the button use <SPOILER=button text> text </spoiler>
Since 4, 5 and 6. might become quite large (especially 6) you can easily put them on separate posts immediately following the initial post of the thread. This requires the FW author to think a little when setting up the thread (and existing threads will have to stay to the first post) but it is workable.
FW Authors can of course post in the thread when they have released a new update, but it will be easily findable in that initial post.
I'm open to comments and ideas on this. The goal is simple quick organization that is not a burden on anyone, yet makes it much easier and faster for people to find what they want (on top of the FW Directory Listing).
For an example post, please look at Winter's great post in his GURPS FW Thread.
NOTE: In going through threads filling in the directory, I realized that Wrathchild's GURPS FW stopped at v1.1 and then changed over to Winter's v2 Beta - so I've split the threads starting a new one with Winter releasing the beta of v2. Both v1.1 and v2 beta are now in the directory listing.
We have a directory of what frameworks are available for what systems, the links to get them, and who maintains them (forum ID).
This works quite easily: When a person writing/maintaining a framework has an update whether Framework Name, Link to Framework, or someone taking it over they PM me the info and I update it.
Every item will have a "last updated" so they know what's the latest and greatest.
If I can make it fit and look right, a direct link to the support thread.
Don't worry, the threads about the different Frameworks are not going anywhere - this is a LIST of them all and where to find them. Everything else is working great except the "Where can I find a framework for X" thing.
PLEASE POST DISCUSSIONS IN THIS THREAD
PROPOSED/REQUESTED FORMAT FOR FIRST POST IN AN 'FW SUPPORT THREAD/TOPIC
INTRODUCTION
Subscribing to a thread is a great way to stay on top of new posts, but for any actively updated framework (or infrequently updated) most posts aren't going to be updates - which means users of that FW get to slog through a bunch of posts to find the gems. Someone who is a user of multiple frameworks probably would go nuts
Azhrei and Gamerdude have been discussing something that would be a big help to all current and new users of these forums - and may actually ease up management of updates for the FW authors.
The basic idea is that the initial post of each support thread conatin all the necessary info on the FW, be where updated info is posted (new files etc) - and use a common format. Basically the info to be included is (at a minimum)
Latest (or last few) version of the FW, a change log, Installation Instructions, and upgrade instructions. Of course change log might best be post #2 of the thread, and any of these items the FW author doesn't wish to maintain in a post (like a
GENERAL FORMAT: (followed by an explanation/details)
1. Thread Title/Subject.
2. General Description
3. Link to current FW (or current and last few versions)
4. Install Instructions
5. Update Instructions
6. Change Log
EXPLANATION/DETAILS:
1. Just have the name of the game system, name of the FW and the Major version number. EX: "[Savage Dragons] Joe's Monstrous FW v3". The post can be edited to add "minor version number" on updates and the "date last updated" but that would be optional.
2. Just what it says. A description of the FW in a small paragraph or two.
3. Link. Either the link to where it can be found out on the web OR it is uploaded as an attachment and then use the <ATTACHMENT=X>FW NAME</ATTACHMENT> command (X is the number of the attachment, they are numbered starting with 0).
4/5/6. Put these inside the <SPOILER>text</SPOILER> command and the text will be hidden until the member clicks on the button. To label the button use <SPOILER=button text> text </spoiler>
Since 4, 5 and 6. might become quite large (especially 6) you can easily put them on separate posts immediately following the initial post of the thread. This requires the FW author to think a little when setting up the thread (and existing threads will have to stay to the first post) but it is workable.
FW Authors can of course post in the thread when they have released a new update, but it will be easily findable in that initial post.
I'm open to comments and ideas on this. The goal is simple quick organization that is not a burden on anyone, yet makes it much easier and faster for people to find what they want (on top of the FW Directory Listing).
For an example post, please look at Winter's great post in his GURPS FW Thread.
NOTE: In going through threads filling in the directory, I realized that Wrathchild's GURPS FW stopped at v1.1 and then changed over to Winter's v2 Beta - so I've split the threads starting a new one with Winter releasing the beta of v2. Both v1.1 and v2 beta are now in the directory listing.