If you are looking for Information about PSU Clementine, Go check their Wiki
Difference between revisions of "Talk:Story Missions (Network)"
(→Section merge) |
(→Section merge: Thanks for redirect, updated all links.) |
||
(14 intermediate revisions by 2 users not shown) | |||
Line 7: | Line 7: | ||
** I actually threw an S-rank requirements table into the "[[Desert's End 1]]" Article. If it looks okay, it shouldn't be too hard to add to the other pages. :)<br/>--[[User:Kietrinia|Kit]] 14:47, 5 February 2008 (CST) | ** I actually threw an S-rank requirements table into the "[[Desert's End 1]]" Article. If it looks okay, it shouldn't be too hard to add to the other pages. :)<br/>--[[User:Kietrinia|Kit]] 14:47, 5 February 2008 (CST) | ||
* Ack, too many replies nested within replies, so I'll just start anew down here. XD Check out the sidebar on the left of your screen. In the top section (under our logo) the first link should be to the [[The_PSUPedia:Manual_of_style|manual of style]]. Read through that to see what we've established as out site standards. And if you have any questions, just let us know. ;) Now, for the S-rank requirements table, it looks a bit awkward, to be honest. For missions that have different requirements per difficulty, we can still use the reference tags, but separate each difficulty requirement by using line breaks. I'll throw together an example after while. - [[User:EspioKaos|EspioKaos]] 18:55, 5 February 2008 (CST) | * Ack, too many replies nested within replies, so I'll just start anew down here. XD Check out the sidebar on the left of your screen. In the top section (under our logo) the first link should be to the [[The_PSUPedia:Manual_of_style|manual of style]]. Read through that to see what we've established as out site standards. And if you have any questions, just let us know. ;) Now, for the S-rank requirements table, it looks a bit awkward, to be honest. For missions that have different requirements per difficulty, we can still use the reference tags, but separate each difficulty requirement by using line breaks. I'll throw together an example after while. - [[User:EspioKaos|EspioKaos]] 18:55, 5 February 2008 (CST) | ||
+ | ** OK, I've updated [[Desert's End 1]] to use the S-rank reference with line breaks. (Left the S-rank requirements table in though, just so folks can see both styles; you just have to imagine one or the other isn't there. <_<) I prefer having the text under the main table because it doesn't take up nearly as much extra space. (Three lines of text as opposed to the equivalent of six in the table.) Overall, in my opinion it just looks cleaner. Of course, my wording could probably use a little work. <_<; - [[User:EspioKaos|EspioKaos]] 19:28, 5 February 2008 (CST) | ||
+ | *** I'm sorry, text floating outside of a table just looks hideous to me, especially when it's going to be variable length for every page. Needs some sorta container to hold it and give it a uniform layout. Just seems clunky as text. x.x<br/>--[[User:Kietrinia|Kit]] 21:20, 5 February 2008 (CST) | ||
+ | **** The first time I saw it used (I think it was when the 10 PA Fragment disclaimer thing was added), I wasn't exactly fond of it, either. But over time, the look kind of grew on me, I guess. Anyway, if neither of these styles would work, we can always just leave these requirements to the strategies section of each article since that's where people would ideally head for specific strategies on how to get an S on the trials. - [[User:EspioKaos|EspioKaos]] 21:34, 5 February 2008 (CST) | ||
+ | **** I just tweaked the table in the [[Desert's End 1]] article to make it match the top one (which I also tweaked, please leave the <nowiki><br/></nowiki>s in the info headers or it'll break the width x.x). It seems alot nicer than a lil table out on it's own of a different width. It should also give you an idea of what I have in mind for the "other info" section, like VIP survival info and such. I hope it looks a bit better.<br/>--[[User:Kietrinia|Kit]] 12:22, 6 February 2008 (CST) | ||
+ | * That looks a lot better. :D It gave me an idea for a little more tweaking, though. Check it out: | ||
+ | {| class="wikitable" style="text-align:center" | ||
+ | ! rowspan="2" | LV !! rowspan="2" | Req. LV !! rowspan="2" | Enemy LV !! colspan="2" | Rank S !! colspan="2" | Rank A !! colspan="2" | Rank B !! colspan="2" | Rank C | ||
+ | |- | ||
+ | ! Meseta || Points || Meseta || Points || Meseta || Points || Meseta || Points | ||
+ | |- | ||
+ | | C || 1 || 3+ || 100 || 2 || -- || -- || -- || -- || 0 || 0 | ||
+ | |- | ||
+ | | B || 35 || 17+ || 390 || 5 || -- || -- || -- || -- || 0 || 0 | ||
+ | |- | ||
+ | | rowspan="2" | A || rowspan="2" | 60 || rowspan="2" | 30+ || 990 || 12 || rowspan="2" | -- || rowspan="2" | -- || rowspan="2" | -- || rowspan="2" | -- || rowspan="2" | 0 || rowspan="2" | 0 | ||
+ | |- | ||
+ | | colspan="2" | [[PA Fragment]] x10<ref>[[PA Fragment]] rewards for story missions are only awarded once per character.</ref> | ||
+ | |- | ||
+ | ! colspan="11" | Rank S requirements | ||
+ | |- | ||
+ | ! LV !! colspan="2" | Time !! colspan="2" | Defeated enemies !! colspan="6" | Miscellaneous requirements | ||
+ | |- | ||
+ | | C || colspan="2" | Under 17:30 (?) || colspan="2" | 64 enemies || colspan="6" | -- | ||
+ | |- | ||
+ | | B || colspan="2" | Under 17:30 (?) || colspan="2" | 64 enemies || colspan="6" | -- | ||
+ | |- | ||
+ | | A || colspan="2" | Under 17:30 (?) || colspan="2" | 64 enemies || colspan="6" | -- | ||
+ | |} | ||
+ | <references/> | ||
+ | * Basically, it's your table (with adjustments made per style guide standards) adhered to the original table. And the reason I keep reverting the changes made to the ''Req. LV'' and ''Enemy LV'' columns is because those headings were established as the standard for all mission tables last summer, so they should not be altered. I took out the predetermined pixel width since that can cause issues depending on your resolution. Larger resolutions will suffer from a slightly (but not by much) cramped table (the PA Fragment x10 part gets put on two lines for me, for example) and smaller resolutions run the risk of this table merging with the mission infobox to its right in cases when the mission infobox might get stretched out due to a long mission title or lengthy lobby or counter name. I tried out percentages instead of pixels, as well. It worked well on smaller resolutions, but looked quite unfortunate at a larger resolution. XD Anyway, to combat this, if any of the misc. requirements for getting an S rank are kind of wordy, we can just use line breaks to preserve the table. To be honest, though, I don't see too many of them being that involved. (Actually, are there any others aside from NPC protection? Nothing else seems to be coming to mind at the moment.) - [[User:EspioKaos|EspioKaos]] 14:04, 6 February 2008 (CST) | ||
+ | ** Okay, I think we can finally come together on this one after dueling to death over it. XD I like how it looks. I just worry about stretching of the upper table if it gets out of hand. We could use the "max-width" style property to keep it under control though. Though, it might be good to take this table and turn it into a template if we start getting column specific styles involved. Would that sound okay?<br/><br/>And about the <nowiki><br/></nowiki> tags...I'd no idea. I think a few more tables need to be template-ized to prevent this kind of confusion. x.x<br/>--[[User:Kietrinia|Kit]] 14:20, 6 February 2008 (CST) | ||
+ | *** Sweet. I'm glad you like it. :D I'll make the necessary changes to the article to put this in use. But, first I think I'll make this type of table into a template, as you suggested. - [[User:EspioKaos|EspioKaos]] 15:03, 6 February 2008 (CST) | ||
+ | *** Oh wow! I love it! Now we can start migrating information over and knock out the story missions page once we've all the information moved over. :D<br/>--[[User:Kietrinia|Kit]] 15:47, 6 February 2008 (CST) | ||
+ | **** Cool. :) I've made a separate mission template for the ''Episode 3'' missions since they have one extra reward thrown into them that the ''Episode 2'' missions don't have. Ah, and one thing to keep in mind for data transfer is that the old story missions page (this one) may have a lot of outdated rewards info. Well after this section was started, SonicTeam changed a number of the Meseta and MP payouts, so we'll have to be certain that our data is correct before it goes into the individual articles. I know for certain that all of the individual articles have up-to-date values (unless someone slipped something past me) since they were all wiped and redone after the change. - [[User:EspioKaos|EspioKaos]] 15:56, 6 February 2008 (CST) | ||
+ | **** Saw the different templates, and I even managed to wipe another variable from them (C rank gets you nothing but sad music and a lecture, unless there's a single mission out that that DOES reward C-ranking >.>). Though, would it make more sense to just put in a manual reference using an asterisk (*) with a note at the bottom of a table, instead of using a <nowiki><ref></nowiki> tag? It's confusing the actual template page a lil bit. o.O<br/>--[[User:Kietrinia|Kit]] 16:07, 6 February 2008 (CST) | ||
+ | ***** As far as I know, a C will always give you zeros, so good call. ;) I've likewise updated the ''Episode 3'' template. (I think party missions like Bruce and HSM -- and soon to be Her Hero Is a Thief -- are the only ones that give a reward for a C.) On the reference tag, I was looking for a way to fix it on the template page before, but eventually realized that it was only doing that because the reference is linked twice due to the example text and then the actual table. I plan on cleaning up the template pages to match the others we have later on. I'll add a note about that. But since everything works fine in the mission articles, I say we stick with the tag. ;) - [[User:EspioKaos|EspioKaos]] 16:17, 6 February 2008 (CST) | ||
+ | ***** I'll go ahead and install the template in a few of the story pages then. See how many I can do before class starts. ^-^v<br/>--[[User:Kietrinia|Kit]] 16:21, 6 February 2008 (CST) | ||
+ | ***** All done with all the maps. Pasted whatever strategies I found in here into the individual pages. Should we turn this page into a redirect to [[Story missions]]?<br/>--[[User:Kietrinia|Kit]] 14:45, 7 February 2008 (CST) | ||
+ | ***** Thanks for making it a redirect. I've also updated all the links to this page so the only pages that will ever link to this page is stuff in the "Special:" namespace. :)<br/>--[[User:Kietrinia|Kit]] 10:29, 8 February 2008 (CST) | ||
== New section == | == New section == |
Latest revision as of 16:29, 8 February 2008
Contents
Section merge
Just want to point out that this article is rather obsolete as far as style goes with the rest of the PSUPedia now that we have individual mission pages for each chapter and act. I've also just created a new index page for the story missions which can be found here. I'd like for us to update individual chapter articles with stuff like reward data as opposed to this page. Soon I'd like to change this article to a redirect to the new one. - EspioKaos 13:08, 1 February 2008 (CST)
- Just made a few of those changes on the first three network story pages (The Mask 1 and 2 and Desert's End 1) by adding the S-Rank requirements column. I also saw a strategy section at the bottom of Price of Genocide 2 that we could use on all the other pages to fill in strategy information. Also made a story missions category so it's easier to get to these things (PSUPedia needs more useful categories ;P). Hope it all looks okay. :)
--Kit 13:02, 4 February 2008 (CST)- Ah, just saw your addition up here after I replied down there. ;) The category addition is cool, though each article will have to be edited to change the category link to the standard capitalization (just put missions in lowercase). The strategies thing hasn't really been decided on yet, as far as I know. I guess strategies can be added to the bottom of each article, but it's got to be clean and well worded. I'm really sorry if I sound terribly nitpicky over all of this, but these mission pages are kind of my uh... babies. XD - EspioKaos 13:13, 4 February 2008 (CST)
- OK, just got home from work. Before I left, though, I checked out the (new) story mission articles on PSUPedia's recommended minimum resolution (1024x768), and uh... eek. The table gets pretty cramped with the requirements column, even when the player and enemy level columns are reduced in width. As such, I propose this. I've removed the S requirements column and replaced it with a footnote at the bottom of the table. The reference number is at the top in the Rank S heading, and if clicked will drop you down to the note. This makes the table look better at smaller resolutions while keeping the previous standardized format. - EspioKaos 17:36, 4 February 2008 (CST)
- Er, sorry, I didn't know 1024x768 was the minimum requirement, nor did I know you didn't capitalize second words. Is there a style guide in here somewhere? I'd trouble finding one, and I'd like to avoid causing anymore trouble. :(
That reference idea is a good one, but how do we list it when there's a difference between ranks? S-rank requirements change based on mission difficulty for most missions. Maybe have a reference table with requirements for each rank?
--Kit 14:24, 5 February 2008 (CST) - I actually threw an S-rank requirements table into the "Desert's End 1" Article. If it looks okay, it shouldn't be too hard to add to the other pages. :)
--Kit 14:47, 5 February 2008 (CST)
- Er, sorry, I didn't know 1024x768 was the minimum requirement, nor did I know you didn't capitalize second words. Is there a style guide in here somewhere? I'd trouble finding one, and I'd like to avoid causing anymore trouble. :(
- Ack, too many replies nested within replies, so I'll just start anew down here. XD Check out the sidebar on the left of your screen. In the top section (under our logo) the first link should be to the manual of style. Read through that to see what we've established as out site standards. And if you have any questions, just let us know. ;) Now, for the S-rank requirements table, it looks a bit awkward, to be honest. For missions that have different requirements per difficulty, we can still use the reference tags, but separate each difficulty requirement by using line breaks. I'll throw together an example after while. - EspioKaos 18:55, 5 February 2008 (CST)
- OK, I've updated Desert's End 1 to use the S-rank reference with line breaks. (Left the S-rank requirements table in though, just so folks can see both styles; you just have to imagine one or the other isn't there. <_<) I prefer having the text under the main table because it doesn't take up nearly as much extra space. (Three lines of text as opposed to the equivalent of six in the table.) Overall, in my opinion it just looks cleaner. Of course, my wording could probably use a little work. <_<; - EspioKaos 19:28, 5 February 2008 (CST)
- I'm sorry, text floating outside of a table just looks hideous to me, especially when it's going to be variable length for every page. Needs some sorta container to hold it and give it a uniform layout. Just seems clunky as text. x.x
--Kit 21:20, 5 February 2008 (CST)- The first time I saw it used (I think it was when the 10 PA Fragment disclaimer thing was added), I wasn't exactly fond of it, either. But over time, the look kind of grew on me, I guess. Anyway, if neither of these styles would work, we can always just leave these requirements to the strategies section of each article since that's where people would ideally head for specific strategies on how to get an S on the trials. - EspioKaos 21:34, 5 February 2008 (CST)
- I just tweaked the table in the Desert's End 1 article to make it match the top one (which I also tweaked, please leave the <br/>s in the info headers or it'll break the width x.x). It seems alot nicer than a lil table out on it's own of a different width. It should also give you an idea of what I have in mind for the "other info" section, like VIP survival info and such. I hope it looks a bit better.
--Kit 12:22, 6 February 2008 (CST)
- I'm sorry, text floating outside of a table just looks hideous to me, especially when it's going to be variable length for every page. Needs some sorta container to hold it and give it a uniform layout. Just seems clunky as text. x.x
- OK, I've updated Desert's End 1 to use the S-rank reference with line breaks. (Left the S-rank requirements table in though, just so folks can see both styles; you just have to imagine one or the other isn't there. <_<) I prefer having the text under the main table because it doesn't take up nearly as much extra space. (Three lines of text as opposed to the equivalent of six in the table.) Overall, in my opinion it just looks cleaner. Of course, my wording could probably use a little work. <_<; - EspioKaos 19:28, 5 February 2008 (CST)
- That looks a lot better. :D It gave me an idea for a little more tweaking, though. Check it out:
LV | Req. LV | Enemy LV | Rank S | Rank A | Rank B | Rank C | ||||
---|---|---|---|---|---|---|---|---|---|---|
Meseta | Points | Meseta | Points | Meseta | Points | Meseta | Points | |||
C | 1 | 3+ | 100 | 2 | -- | -- | -- | -- | 0 | 0 |
B | 35 | 17+ | 390 | 5 | -- | -- | -- | -- | 0 | 0 |
A | 60 | 30+ | 990 | 12 | -- | -- | -- | -- | 0 | 0 |
PA Fragment x10[1] | ||||||||||
Rank S requirements | ||||||||||
LV | Time | Defeated enemies | Miscellaneous requirements | |||||||
C | Under 17:30 (?) | 64 enemies | -- | |||||||
B | Under 17:30 (?) | 64 enemies | -- | |||||||
A | Under 17:30 (?) | 64 enemies | -- |
- ↑ PA Fragment rewards for story missions are only awarded once per character.
- Basically, it's your table (with adjustments made per style guide standards) adhered to the original table. And the reason I keep reverting the changes made to the Req. LV and Enemy LV columns is because those headings were established as the standard for all mission tables last summer, so they should not be altered. I took out the predetermined pixel width since that can cause issues depending on your resolution. Larger resolutions will suffer from a slightly (but not by much) cramped table (the PA Fragment x10 part gets put on two lines for me, for example) and smaller resolutions run the risk of this table merging with the mission infobox to its right in cases when the mission infobox might get stretched out due to a long mission title or lengthy lobby or counter name. I tried out percentages instead of pixels, as well. It worked well on smaller resolutions, but looked quite unfortunate at a larger resolution. XD Anyway, to combat this, if any of the misc. requirements for getting an S rank are kind of wordy, we can just use line breaks to preserve the table. To be honest, though, I don't see too many of them being that involved. (Actually, are there any others aside from NPC protection? Nothing else seems to be coming to mind at the moment.) - EspioKaos 14:04, 6 February 2008 (CST)
- Okay, I think we can finally come together on this one after dueling to death over it. XD I like how it looks. I just worry about stretching of the upper table if it gets out of hand. We could use the "max-width" style property to keep it under control though. Though, it might be good to take this table and turn it into a template if we start getting column specific styles involved. Would that sound okay?
And about the <br/> tags...I'd no idea. I think a few more tables need to be template-ized to prevent this kind of confusion. x.x
--Kit 14:20, 6 February 2008 (CST)- Sweet. I'm glad you like it. :D I'll make the necessary changes to the article to put this in use. But, first I think I'll make this type of table into a template, as you suggested. - EspioKaos 15:03, 6 February 2008 (CST)
- Oh wow! I love it! Now we can start migrating information over and knock out the story missions page once we've all the information moved over. :D
--Kit 15:47, 6 February 2008 (CST)- Cool. :) I've made a separate mission template for the Episode 3 missions since they have one extra reward thrown into them that the Episode 2 missions don't have. Ah, and one thing to keep in mind for data transfer is that the old story missions page (this one) may have a lot of outdated rewards info. Well after this section was started, SonicTeam changed a number of the Meseta and MP payouts, so we'll have to be certain that our data is correct before it goes into the individual articles. I know for certain that all of the individual articles have up-to-date values (unless someone slipped something past me) since they were all wiped and redone after the change. - EspioKaos 15:56, 6 February 2008 (CST)
- Saw the different templates, and I even managed to wipe another variable from them (C rank gets you nothing but sad music and a lecture, unless there's a single mission out that that DOES reward C-ranking >.>). Though, would it make more sense to just put in a manual reference using an asterisk (*) with a note at the bottom of a table, instead of using a <ref> tag? It's confusing the actual template page a lil bit. o.O
--Kit 16:07, 6 February 2008 (CST)- As far as I know, a C will always give you zeros, so good call. ;) I've likewise updated the Episode 3 template. (I think party missions like Bruce and HSM -- and soon to be Her Hero Is a Thief -- are the only ones that give a reward for a C.) On the reference tag, I was looking for a way to fix it on the template page before, but eventually realized that it was only doing that because the reference is linked twice due to the example text and then the actual table. I plan on cleaning up the template pages to match the others we have later on. I'll add a note about that. But since everything works fine in the mission articles, I say we stick with the tag. ;) - EspioKaos 16:17, 6 February 2008 (CST)
- I'll go ahead and install the template in a few of the story pages then. See how many I can do before class starts. ^-^v
--Kit 16:21, 6 February 2008 (CST) - All done with all the maps. Pasted whatever strategies I found in here into the individual pages. Should we turn this page into a redirect to Story missions?
--Kit 14:45, 7 February 2008 (CST) - Thanks for making it a redirect. I've also updated all the links to this page so the only pages that will ever link to this page is stuff in the "Special:" namespace. :)
--Kit 10:29, 8 February 2008 (CST)
- Okay, I think we can finally come together on this one after dueling to death over it. XD I like how it looks. I just worry about stretching of the upper table if it gets out of hand. We could use the "max-width" style property to keep it under control though. Though, it might be good to take this table and turn it into a template if we start getting column specific styles involved. Would that sound okay?
New section
- I'm working on creating a detailed guide to all of the story missions currently available on the English servers. I intend to include data tables for each chapter which will detail trial rewards based on character level, and possibly item drop tables. Also, I may be adding in detailed descriptions of plot points and story elements made in each chapter. EspioKaos 09:43, 27 December 2006 (CST)
- Thoroughly agreed with this article. It's been long overdue, and I'll try to help out as best I can. - Miraglyth 19:11, 27 December 2006 (CST)
Requirements / Difficulty?
- One of the questions I've been thinking is thus: The story missions are known to divide into difficulty tiers based on your character level. Does anyone know if the requirements for S/A/B rank differ based on the tier, or if they are all the same (i.e. 3/5/7 minutes for a time-based mission) and the monster level is the only difference? - Miraglyth 19:11, 27 December 2006 (CST)
- Related. I'll look into it; lolz reverse-calculating points. - Tycho 07:17, 28 December 2006 (CST)
JP 01.12 update will change a few things
- It's been revealed by SonicTeam that the level tiers used for the story missions will be changed to go by the standard C-S rankings used on free missions. Once we get to this update and can gather more information, we'll make any necessary alterations to our data tables. EspioKaos 13:20, 30 December 2006 (CST)
HIVE Clean-Up Mission 2 NPC location?
- The entry says that you need to leave your NPC at the "right location" and then do the lap hitting switches, but it doesn't tell you which one is the right location. Can that be added to the entry? MechaCrash 18:27, 13 February 2007 (CST)
- OK, I've clarified that section. EspioKaos 23:42, 13 February 2007 (CST)
- I wrote the original; For the entirety of this article I have tried to keep it spoiler-free, hence not even revealing NPC names. In addition I'd preferred not to throw out hints as some players may have desired to do everything by themselves. - Miraglyth 05:57, 14 February 2007 (CST)
- Updated. I changed Laia back to "NPC," but for the time being I've left the description of which terminal to leave her at. Perhaps we could make a separate section for strategies for these missions? EspioKaos 09:57, 14 February 2007 (CST)
- Perhaps state which terminal is the right one and use spoiler tags to hide it, like with the location? Although now that I think about it, EspioKaos's idea is way better, mine would just be a temporary thing for this one issue... MechaCrash 00:11, 17 February 2007 (CST)
Adding new missions (past chap. 4)
I'm going to be adding the newer missions. The work in progress is at User:Malice/Story Missions (Network). Malice 17:55, 17 April 2007 (BST)
Needing update
This section needs a major overhaul. Now that each mission has its own page, maybe this page should be a simple list and mission description?--JubeiSaotome 04:50, 3 December 2007 (CST)
- Ever since making the individual mission articles, I've been thinking of what we could do with this page. To be honest, I'm not entirely sure if it's even necessary anymore. But, at the very least, it could serve as a catalog of story missions. By the way, we absolutely must redo those strategy sections you added to some of the articles. Very useful, yes, but I will not tolerate the terrible grammar and spelling that's displayed in the copy-pasted strategies. We should rewrite those sections to clean them up. Unfortunately, at the moment I must get ready for work, so I can't tend to it right now. - EspioKaos 06:30, 3 December 2007 (CST)
- Would story mission strategies work better in a guide rather than normal articles? Also I noticed the mission grade requirements are not listed (kills, time, samples, Tomrain incapacitations, etc). Could strategies be written in as part of that list? --Zoamel Gustav 20:42, 3 December 2007 (CST)
- I've actually been working the S-Rank requirements into the individual story mission pages for the time being. As far as strategies go, I saw a section added to the Price of Genocide 2 page at the very bottom. Maybe follow a similar format?
--Kit 12:58, 4 February 2008 (CST)- I appreciate the additions, but I must point out that lots must be fixed as the site's capitalization standard has not been followed. Also, by altering some of the column titles, the standard established for mission info tables has been strayed from. I'm not too terribly excited about that because that means that either all of the edited articles must be reverted/fixed or all of the untouched articles must be edited to match. I messed around with The Mask 1 to clean things up, but the changes are not final. At the moment, I don't have time to do much more since my lunch break is more or less over, and I must get back to work. - EspioKaos 13:08, 4 February 2008 (CST)
- That's a good point. These articles are mostly supposed to be cut-and-dry facts on enemies, rewards and drops. Strategies would be better suited for a guide. In fact, this reminds me. I'd almost forgotten that we've got a guides section set up already. (Ack. Can't make categories link properly unless I make it external.) We might as well put it to some use, right? - EspioKaos 22:50, 3 December 2007 (CST)
- Sounds good to me. Maybe a template / table thingo for guide pages, which list links to each chapter for Offline Story, Online Eps 2 & 3 and so on? PSUpedia is the perfect knowledge base of PSU, it's basically THE official strategy guide. Let's make it live up to that. --JubeiSaotome 02:32, 4 December 2007 (CST)
Illuminus Ambition 2
Hm I've heard of a 2:04 time not getting S rank in A difficulty, and my first try was 2:07 getting S rank so I always thought the requirement was 2:05; can anyone confirm this? Essen 21:55, 27 January 2008 (CST)