Difference between revisions of "The re-PSUPedia talk:Item drop templates"

Revision as of 22:40, 24 December 2007

Most templates created

• Alright, I've made templates for pretty much all of the released enemies. SEED-Magashi and Fulyen Curtz are the only ones (I think) I haven't made yet. Pardon the mass of "unknowns," but I figured it'd be best to get templates for all levels created, that way we can populate our drop tables with the appropriate templates as missions are released and then edit the templates when we find new drop info so we won't have to go back into each individual mission article to add the template to the table. Besides, I made them all minor edits so they can be easily sorted out of the recent changes page. Also, I was going to use the original Perfect Bible to fill in drop info since it has pretty much everything from LV1-99 on most enemies, but then I started to notice incorrect data in the book compared to what we've already collected. Drop data must've changed between when it was published and now, so I'm going to wait until I get my new Perfect Bible (should be within a few weeks) and hope that it has up-to-date tables with all of the new enemies included. Honestly, I don't see why it wouldn't. Anyway, I'll begin adding templates to mission drop tables soon. - EspioKaos 16:40, 24 December 2007 (CST)

Enemy names

• Great work on this, Mewn! I noticed that you've got names for some enemies that haven't even appeared in the Japanese version. Fruits of some data mining, perhaps?  ;) Mainly just curious if these are official names so I can make some updates elsewhere. - EspioKaos 12:20, 1 December 2007 (CST)

Spacing of drops

• I noticed that the Jaggo special drops were changed from being broken into separate lines to being listed on one line separated by commas. To be honest, I prefer the line-by-line. I think it just looks cleaner. Thoughts? - EspioKaos 12:20, 1 December 2007 (CST)

Mission drop table template

You may or may not have seen my experimenting with templates. The result is a nice drop table template that may be handy sometime. Have a look in my sandbox: http://psupedia.info/User:Au/Sandbox As you can see in the source you need only very little wiki code to build the table. Some restrictions apply, though:

• All monsters in the mission must be in the same drop tier (except for boss, that one's filled in seperately). I know there are a few missions where they're different (Cost of Research, and one of the shrooms missions) but as far as I know they're the exception, not the rule.
• Every monster - including those that appear only below or above level 50, must have all drop tiers filled in in their templates.
• Max. 10 different monster supported. Can have less. Support for more can be added if needed.

S2 level is optional, leave it empty and nothing will be there but the other levels have to be filled in.

Thoughts? -Au+

• I was wondering how that was going to turn out. To be honest, the mass of brackets all over the place frightened me! XD It looks nice, but I imagine it'd take me a while to switch over to using this, especially considering how comfortable I've become in using the table layout we already have. - EspioKaos 09:09, 7 December 2007 (CST)
  • The template source looks scary for sure ;) In any case I mostly did this to learn some new template tricks; I'm not entirely sure if this single-drop-tier thing works for all missions, pretty sure it does but maybe I'm overlooking stuff. If this is useful, great, but if it isn't, the knowledge I've gained will be; I've learned how to do optional template arguments now. But I think this may make a few drop tables a bit easier. Au+ 11:39, 7 December 2007 (CST)
    • The optional field thing is something I'm interested in learning to do, actually. I could use it for the mission infoboxes to get rid of fields that aren't needed, for example, the item exchange missions don't need an enemy element section. Could you point me in the direction of something showing how to do this? - EspioKaos 11:50, 7 December 2007 (CST)
      • I'll try to explain. First you need to know that you can use default arguments. You normally call a parameter like {{{param}}}. You can make it use a default parameter if none is given like this: {{{param|defaultvalue}}}. Next, there is the #ifeq: command. It checks 2 strings; if they're equal it does one thing, if they're not, another. It works like this: {{#ifeq: string1|string2|do this if equal|and this if not}}. So how do you use this to check if a parameter is given? Well, you compare the parameter with itself, but with different default arguments. So if the parameter is given, they will be equal, but if not, they will not be. For example this will show param if it's there, and '--' if it's not: {{#ifeq: {{{param|+}}}|{{{param|-}}}|{{{param}}}|--}}. Hope this is clear! Au+ 14:42, 7 December 2007 (CST)
  • I'm not sure, I'm very comfortable with the system we have now, and switching over to the new system may prove to be a bigger headache than continuing to use this system, which kinda defeats the object. However, since Espio is largely responsible for the mission templates I'll leave any decision to him. - Mewn 11:48, 7 December 2007 (CST)