http://www.gamefaqs.com/boards/198537-saga-frontier/61268429^Better make that crossposting between four forums - actually five, if you count RPDL.
And to reply to your queries:
A: You'll have your own forumboard rather than being a subforum of the DL forums, since I was under the impression that that was what you wanted set up.
That's exactly what I wanted to do.
Unless you purchase your own domain name, though, the forum link will be subset of the rpgdl.com domain (something like http://www.rpgdl.com/sagaforums/ with the directory name up to your discretion).
Money is an issue. In fact, I'm homeless right now, and posting from the local library, where I keep warm on weekdays.
The DL has no advertisements and generates no revenue; we subsist entirely on our own community contributions to pay for hosting.
If you ever need to generate revenue from ads in the future, ask and I will advertise the heck out of this forum... but probably not the SaGa Frontier modding forum, since that's kinda a gray area, legally.
We're offering to host you in hopes of assisting on the SaGa hacking/modding project and growth of its community in general, and while there will be no direct ties to the DL site/boards this is partially being done in hopes of seeing some intercommunity interaction, if nothing else. We do have an IRC channel and it's always great to see new faces. As I mentioned before, there are a number of us who are quite dedicated SaGa Frontier fans.
We can't intermingle our memberlists? As in, if you're a member here, you'll be a member there?
A: Yes. In the event that the hosting situation ends up not working on either of our ends, I will provide an entire copy of the forum's files in the case that you decide to migrate elsewhere.
Good to know.
I have some experience with site hosting (I am a system administrator by profession), but it's not my expertise, nor do I wish to maintain a web site. That's an entirely different can of worms unto itself (Talaysen handles the DL site, which is largely quiet, and I pitch in when needed). This proposal is to set up an SMF forumboard with the version you're requesting and adding in mods for it where possible; I'm quite confident that I can figure out most of what you're after in that regards. If you're looking for a dedicated webmaster with your own site that integrates with the boards, though (like romhacking.net), that's beyond the scope of what I'd prefer to do and, to be quite honest, asking a lot of one person. This is for just a forum board.
As I'll be doing the majority of the work here, I will be your technical admin and the one with actual access to server files, but for actual forum administration I'd rather stay out of that and let someone who actually knows the SaGa modding community and project manage the board. I can step in as necessary if requested and will address technical concerns (board downtime, etc.), but anything that can be handled either through moderation or through the Admin features of SMF should be addressed by this person.
So you just don't want to deal with the people, act as a leader of the entire forum, or otherwise constantly be bugged over everything and anything just for being the highest ranking member? Sounds fine.
If all of this can be done within the confines of SMF's forum administration tools, then it's possible. Posting restrictions is certainly dead easy to do through it. I'm not so sure about the forms stuff (if you have a mod or plugin that integrates into SMF for that, then I can install it); so long as it doesn't require stepping into the field of hosting a separate site it should be fine.
I will caution that I think it's much more prudent to stay relatively restriction-free and loose about who can post what and where as the project grows. It's only when things have really matured and organization becomes a necessity rather than a luxury that you need to worry about those things. To my knowledge, no actual hacks (outside of hex edits) or mods for SaGa currently exist, it's generally better to let things develop as they will and cohesively piece it all together once there's enough work in progress to justify it. Honestly, a judicious use of stickied topics and forum organization will likely suffice to begin with.
I actually found the aformentioned mod, but I'm not sure I really want to use such a thing, since it will entail setting up another database or sorts. Very much like RHDN, but more advanced, in that you can search on every possible detail of a hack, hacks are cross-referenced in terms of hacks that interact with each other - or cancel each other out, or whatever - and you can fill out forms to file bug reports on hacks on every possible platform (with drop down boxes for the various emulators, modded PS1, modded PS2, PS1 eboot on PSP,...), submit updates to hacks, report interactions with other hacks. As I said in the other topics, I don't want a FF3/6 situation, with a bunch of hacks and tools and no central and consolidated data source on conflict between them, canceling out, interactions, updates, bugs, and other things I've no doubt forgotten.
If you can think of a superior forum layout and posting protocol, which will correct these problems, then please share it.
This all, of course, comes with the mandatory disclaimer that all of us (you, myself, anyone involved in the project) are doing all of this out of our free time, and our dedication is largely dependant on our personal vested interests and motivation. If it ever ends up not working out for whatever reason, we can agree to settle things amiably and I will never withhold any kind of work (the forum's files and database in this particular case) from you guys if it comes to that. Flipside, I ask that you recognize that I am just one person and I may not be able to cater to every single technical request you want, or that things may just take time.
With that in mind, I'll trim the technical requests, and try to be short, clear, and to the point.
The other thing is that Talaysen, as our main admin host (aka he pays for stuff), has the right to bring up any concerns regarding proper use of resources such as bandwidth, space and all of that; these will have to be resolved promptly. I sincerely doubt that any of these will be a concern assuming you're not going to be uploading entire ISOs, though you should utilize off-site data storage (large images and other files, etc.) whenever possible.
Is it possible to only allow *.7z and *.rar filetypes for upload? And ban image uploading all together?
We can use imgur for images, and link to them. Avatars, screencaps, and whatnot. Does anyone know of any really good free file uploading services? With features like unlimited downloading for free users, and uploads last forever? Those are the only two we really need, but things like a really freaking high file capacity are nice too.
Since I'm on the subject, bring up any further technical details, and I'll tweak the proposed layout to remove as many mods as can be. Since I assume mods increase the amount of data which needs to be sent and recieved, which means more money needs to be spent to host us.
If you frequent IRC, please drop by at irc.lunarnet.org #rpgdl and fire off a PM to me and we can discuss in real-time if there's further topics that need to be clarified.
I lack the requisite Java.
Here's my forum layout, for now. I think SMF 2.0 - what this forum already uses - will be sufficient, for now, since I don't really want to use many mods. And speaking of mods, I have an account at the SMF forum, so I can find what I need myself and check if it works with the version this forum uses, though I think I'll need to know the specific version. PM it to me, I guess, since I think it's a bad idea to post it in public.
-Section: "Hacking" //this section is where it's generally okay to post
*Board: "Newbie Board" Description: "Got a question? POST IT HERE!"
*Board: "General Hacking" Description: "Investigating, documenting, and reverse-engineering SaGa Frontier." //tutorials are stickied here. As are documentation spreadsheets.
-Section: "Projects" //posting is very restricted in this section
*Board: "Hacks" Description: "Hex edits, assembly hacks, and hack-generating spreadsheets ONLY!" //self-note: Sticky a "Read this first!" topic on this board. Possibly limit posting to users at least 30 days old. Also, hack-generating spreadsheets go here.
*Board: "Mods" Description: "Full game makeovers. Don't post here unless you have a patch, or you're providing feedback." //Rules thread: "You must have a patch to start a topic. If you're just wanking, post in General Hacking."
-Section: "Tools" //each tool gets it's own board, where tool creator gets feedback and archives older versions, and each tool get's it's own feature request sub-board. Also, this section exists, but it doesn't get any boards yet. I want it to exist to highlight that we need SF-specific tools.
-Section: "SaGa Frontier Clone Project"
Board: "(Project Name) Discussion" //self-note: Sticky a topic: "WANTED: SaGa fanatic who wants to make a clone of SaGa Frontier."
-Section: "Off Topic"
*Board: "General Discussion" Description: "Talk amongst yourselves." //I wonder, should we just use RPGDL's general section here? It might make sense to do that if we can share member lists.
*Board: "Forum Feedback" Description: "Request and discuss new features, report bugs, and talk about the site here."
Anything preceded by a comment - the double slashes - is just me talking to you, to myself, or just saying things I want feedback on. It doesn't actually go in the forum. BTW, don't create the forum just yet, I want to see if anyone else has some ideas. Let's wait until, say, next Tuesday, before we set anything in stone.
We also need a name for the proposed SaGa Frontier clone.
EDIT
Forgot to say, we also need an exact hack (hex edit, asm hack, and hack-generating spreadsheet) posting protocol. Same goes for Tools. All are required unless otherwise posted. What we need:
*Emulator, and emulator version or SVN number tested on. INCLUDE OPERATING SYSTEM!
*Hardware tested on. PS1 eboot on PSP, modded PS1, modded PS2.
*Known bugs.
*Other hacks/tools it interacts with.
*Other hacks/tools it renders obsolete.
*Other hacks/tools it conflicts with.
*The actual hack - files it changes, the addresses in those files, the original data and the new data.
*Data it rearranges, if any. POST CODE!
*Data it optimizes, if any. POST CODE!
*Version History.
*Version number. (We'll just call the first release 1, and count up from there. And I don't mean this is version 1.45334234pi. I mean this is version 1, this is version 2, this is version 3, this is version 4,...)
*Edit/modification/release dates.