FANDOM

A FANDOM user
  Loading editor
  • Sorry to bug you, just posting here for visibility. See comment there here.

      Loading editor
    • (Posted here because Wikia's not letting me post a reply to the page proper. Left the page open too long, I think.)

      Sorry for the (really) late reply. Yeah, that was my miss, not Wikia's. I just haven't gotten around to tweaking it to work on only the max stats yet - was trying to think of the best way to display the block/range boxes properly first. Originally, the c2A series of mods were only meant units that had a different Ability at c2 than c1, if any appeared (there aren't any presently), so it's kind of pointless at the moment. That said, I don't think just removing it will solve much, since the same kind of problem will occur when using the c1A mods on a Silver that don't have a c2.

      The best solution is probably as Noctv said, to add in s55A variables, least of reasons being more intuitive for the editor to see in the source code. I won't be able to work on it right away, but I'll try to build that in within 48 hours.

        Loading editor
    • A FANDOM user
        Loading editor
  • Hello, I recently began working on acquiring the original Japanese text from volume one of the Character Profile and I was told that you were previously handling this project on the wiki. I got the Japanese text for the first few pages of the book (all of the soldier and rogue class units), but I cannot translate it on my own. I am not sure if you currently have the time to translate the Japanese text into English like you previously were or if you are even interested in continuing with this, but I would like to help if you feel that having access to the Japanese text would be useful. I will post what I have currently completed on my profile for now if you would like to see it, please let me know what you think. Thank you.

      Loading editor
    • Yo, thanks for your interest.

      Wikis are collaborative resources, so you can always put the JPN text on the unit's respective pages and wait for other people to attempt to translate it. As for how to do this, if you don't know how, in the Wikia skin: click on the down arrow next to the "Edit" button and click "Classic Editor". There should be two tabs at the top-right, "source" and "visual"; click "source". You'll see wikitext code, and the part that you want to edit look like this:

      {{unit infobox
      |name = Phantom Rogue Cuterie
      |gender = Female
      |rank = Gold
      |class = Rogue
      |image = 
      |jpname = 怪盗キュテリ<br>''Kaitō Kyuteri''
      |artist = [http://susanoarashi2.blog40.fc2.com/ 竹森真太郎]
      }}
      

      The parameters I added for the profile stuff are:

      |body =
      |profile1EngText =
      |profile1JpnText =
      

      So at the end of it, it should look like:

      {{unit infobox
      |name = Phantom Rogue Cuterie
      |gender = Female
      |rank = Gold
      |class = Rogue
      |image = 
      |jpname = 怪盗キュテリ<br>''Kaitō Kyuteri''
      |artist = [http://susanoarashi2.blog40.fc2.com/ 竹森真太郎]
      |body = *BODY DATA HERE*
      |profile1EngText = *YOU CAN LEAVE THIS BLANK*
      |profile1JpnText = *JPN TEXT*
      }}
      

      Look at other pages like Sybilla (edit page) for examples, if you like.

      Incidentally, I actually focused on Soldiers for a while, so I think you'll find most of those already filled, sorry to say (except for the Bronze units). I also have a backlog of Bandit units that I never got around to translating but also never bothered to post (can't say I'm following my own advice there, haha). But the rogues should be mostly empty, so you can go ahead and work on them if you like.

      As for translation, I'm not sure about your level of Japanese, but if you took the time to transcribe them it's not that much harder to translate them. You just need a Japanese parser (I use the Translation Aggregator program (nsfw site), though I think web plug-ins like Rikan-chan do the same thing), decent ability in English grammar, and some knowledge of Japanese grammar. That's usually enough for a 90% accuracy.

      Lastly, I'll note that I say all this because I believe that on wikis, page histories should have the proper user credited for contributions. But if you're still not confident or comfortable about editing wikis, then of course I can do the edits for you and leave your name in the edit comments.

      Hope to see you around.

        Loading editor
    • Hello again, and thank you for your response. I appreciate the information that you provided on how to format the pages to include the original Japanese text from the character profile, as I am not highly familiar with the formatting styles that are used on this wiki. I may eventually work on editing articles to include the Japanese text once I have completed more, but being credited for making edits is not that important to me. I know Hiragana, Katakana, and I am familiar with about 200 Kanji, but translating is not something I can really do on my own. I take pictures of pages from the book and use an online OCR tool to convert the text in the image to a document format, so it can get pretty time consuming. I am working on the unit classes in order as they are presented in the book and I would at least like to get up to the samurai class before I even think about editing aticles on my own. If you would like, please feel free to use any of the information that I have posted in my profile, there is no need to credit me for anything. Thank you again.

        Loading editor
    • Bit of a late reply, but gotcha. Feel free to go at whatever pace you want, though I won't be focusing on this for a bit longer.

      I guess I should've pointed this out before, but princesses were actually a class I'd already mostly done too. There's a category of ones I already translated profiles for at Category:Profile written (and the ones transcribed but not translated at Category:Profile needs translating), and looking at that it looks like I did mostly Soldiers, Princesses, Valkyries, Archers, and Vincent and Khuri. I didn't do any of the Bronze-rarity units, and I haven't done some of the event units that came out since I put this on hold. It'd be more efficient to look in there and see which ones I already did before transcribing...unless you're doing this mostly practice transcribing, in which case, you can ignore me.

        Loading editor
    • A FANDOM user
        Loading editor
  • Hey Illumini! I may or may not have snagged your magical template coding skills :P
    Looking to enlist your help with the JP Aigis Wiki templates, I've just started a thread about it on Kure's wall, because I know he's got something in the works, but I'm not sure what ^_^

    I've got several hours set aside in the upcoming days, so I may or may not be blatantly copying many of the templates from this wiki... xD
    (this is also me indirectly, and now directly, asking your permission to use the wonderful templates you've been so kind to make for this site :) haha)

      Loading editor
    • View all 20 replies
    • I fixed it. Sorry for the lateness.

        Loading editor
    • There is no lateness! (trust me, I vanish off to work for weeks at a time. You reading my message with any sort of timeline is A+ haha)

      Now I get to go study your fix :)

        Loading editor
    • A FANDOM user
        Loading editor
  • So I was testing out something with a statblock on User:Kuremisago/sandbox, and it seems that 100AffBonusB doesn't display correctly with CC-less units? Or am I doing something wrong?

      Loading editor
    • No, I'm pretty sure I just forgot to account for subtracting 2 off the rowspan of the top row Aff box if the unit doesn't have c2. I added in the 100AffBonusB for Deine, who did have a class evolution, and just didn't make thorough considerations then.

      Hang on a sec, this should be a relatively quick fix.

      EDIT: And done. Just gotta remember to keep that change when I finally update the template to strip all the styling info...

      Incidentally, I forgot to bring this up when I was asking you to change the css page, but do you have any particular preferences to the whitespace usage in the template? As they are now, the Unitlist templates have a padding value of 5 - so there's (or should be) five pixel's worth of space between the lines and the actual text. Me, being still on the crusade to cram in as much in as little space as possible, reduced that to 2 for the listtable class, but I'm wondering now if that's maybe too little.

      For a visual representation of what's I'm talking about, see the c1 row on the template I made on User:Illumini9/sandbox2. (C2 and c3 still have padding value of 5 on that template though.)

        Loading editor
    • Cool, thanks.

      I kind of prefer it on the high side, honestly. If 2 seems too small, maybe 3 would work as a compromise?

        Loading editor
    • A FANDOM user
        Loading editor
  • The work done for Dark Knight (Injured)/stats is appreciated, thanks. It did have a side effect though on other units without affection bonuses, though (Iron/Bronze/Dorania/?). I guess these were working before and Dark Knight wasn't because they have no CC? It looked like the new standard was to put "n" (N/A) in the affection slot on the stats page, but just wanted to double check if you wanted to do it differently or not.

      Loading editor
    • Ack, sorry for the way late reply, should've been checking back here. I'm pretty sure that before, it was working on whether a unit had a class evolution; if it didn't, it showed N/A automatically. I must've accidentally deleted it - though if not, it's easy enough to implement Wait, wait, wait...confusing myself. That would never work in case of classes that have no c2. I guess I'll just add in a #switch checking for rarity Iron or Bronze, then.

      EDIT2, more direct answer: Yeah, you're pretty much right. Before, it was automatically "N/A" if nothing were put in (though it was one of those cases where you couldn't even put in |50AffBonus= (blank), which would pass along a variable of blank instead of actual nothing), but it depended on it not having a c2 to merge the two cells together (and to not categorize incorrectly) because I assumed a unit without Affection wouldn't have a class-evolution. (And the only exception Gadoras was hard-coded into the template itself.) Now, with any exceptions being waved away by putting in the "n", it should be more flexible for the end-user (though I definitely wanted to automate iron/bronze AFF to N/A automatically too, because I can't go and ask somebody to edit them all just to put in an N/A).

      Thanks for pointing it out.

        Loading editor
    • Oh, I didn't even notice about Gadoras. Thanks again for taking care of it :)

        Loading editor
    • A FANDOM user
        Loading editor
  • Hey there! I was wondering if I could pick your brain for a little bit of help on templates :p

      Loading editor
    • View all 11 replies
    • I'm back to bother you! ^_^ I'm thinking about adding to that template again, this time to indicate SAW with blue colouring instead of the yellow colouring that's currently indicating max level.
      So, is there a particularly neat way to fuse
      {{#if: {{{saw9|}}} | color:blue; | color:white; }} with {{#ifeq: {{#explode: {{{skill9}}} | / | 0 }} | {{#explode: {{{skill9}}} | / | 1 }} | color:yellow; | color:white; }}
      or should I just write it out as
      {{#if: {{{saw9|}}} | color:blue; | {{#ifeq: {{#explode: {{{skill9}}} | / | 0 }} | {{#explode: {{{skill9}}} | / | 1 }} | color:yellow; | color:white; }} }}
      and call it good like that? (Well, I'm going to test like that and if it looks alright, I'll do that unless someone points out a nicer solution ^_^ )

        Loading editor
    • Sorry for the late reply. Yeah, the method you listed is the only way to go. I mean, in the particular logic process of #ifeq, there's only two outcomes: a match or no match. You were always going to have to wrap something around/place something inside it, if not change it entirely in some way I currently don't see is possible.

      I'll mention that if one wanted to be hyper-efficient, you didn't even need a {{{saw9}}} variable - just put a 0 in the {{{skill9}}} parameter, to represent SAW, and then write {{#ifeq: {{{skill9}}} | 0 | color:blue; | ... }}. This bit though is mostly up to each person's style. I personally like to aggressively reduce the number of variables, but other people find it easier to read the source code if every factor was divided and explicit.

        Loading editor
    • A FANDOM user
        Loading editor
  • How does it exactly work? Does it automaticaly add "s" at the end and link to that page? Because there seems to be a problem. AW Materials for Rika's class are on Masters of Automata page while template links to Master of Automatas.

      Loading editor
    • Mostly, yes. But the helper template Template:ClassPlurals has a list of exceptions, so I just add in a new exception if one that doesn't conform to the "-s at the end, or -es at the end if last letter is 'h' or 's'" rule pops up.

      I'd be much obliged if you could give me a heads-up if that happens again, though. Originally I only intended to use that template for base classes, so I might've missed a few exceptions in the CE or AW classes.

        Loading editor
    • Not a problem, I will post if I will find any link that doesn't work. Thanks for fixing.

        Loading editor
    • A FANDOM user
        Loading editor
  • Regarding Shikioni/stats. I haven't looked at the template yet, but...

    I had to add N/A manually for c3Class and c1Skill. Also, the AW icon won't appear anywhere. Maybe it should appear on Mikoto.

    (Note that there is a translated name in the game data for the class and unit as Demon Familiar/Kongo Demon Familiar, but maybe it isn't visible anywhere.

      Loading editor
    • Back then, I seem to have arranged it so that there were three different types: c1Token, c2Token, and c3Token (and then I name Shikioni's type as just Token out of laziness...not my brightest idea). You use Template:Unitlist item once for each stage, and the rationale was that since the tokens have different names, they get different pages for their stats.

      But in retrospect, yeah, that distinction was not significant and completely unnecessary. Gimme a bit of time, I'll fix that right up.

      ...It's probably a smarter idea to separate the template for tokens, too, instead of making one all-encompassing unit template. That template is big enough as it is...

        Loading editor
    • A FANDOM user
        Loading editor
  • I was going to start switching the bronze and iron units to use Unitlist item template with /stats page. The only wrinkle seems to be with A/B units like Bandit Minion.

    I have no problem with keeping these on one page. However, the template code that suppresses the unit name based on matching the page name doesn't work as they don't actually match.

    There already seems to be some code related to A/B support in the edit stats section (which I'm not convinced is necessary at all, but whatever), and it seems that this can easily be adapted to fix the problem.

    However, editing the Unitlist item template is scary :)

    I would say change:

    {{#ifeq: {{{name}}} | {{FULLPAGENAME}}

    to:

    {{#ifeq: {{#ifeq: {{#len: {{#explode: {{{name}}} | | -1 }} }} | 1 | {{#sub: {{{name}}} | 0 | -2 }} | {{{name}}} }} | {{FULLPAGENAME}}

    Thoughts?

      Loading editor
    • View all 5 replies
    • Oh, so that's what you meant when you pointed out those two units before. I actually assumed, when I was building the template, that the Iron units would literally be given the names "Soldier (Unit) A" and "Ninja (Unit)", respectively. So yeah, like you noted, putting those in the |name = field makes it all work out.

      Working off from this, instead of making a new parameter I can edit the template so that while they take "Soldier (Unit) A"/"Ninja (Unit)" as the name, they display "Soldier A" or "Ninja" in the name link. That sound okay?

      Also, should I do this for just the Iron units or for Karma too? Her different versions are distinguished from each other by rarity "Karma (Black)" and "Karma (Platinum)". In her case though I think the rarity note is preferred rather than labelling her two forms "A" and "B" since...well, since she's actually a noteworthy character.

        Loading editor
    • Ah yes. Setting the name with "(Unit)" but hiding from the display would be good.

      No strong opinion on Karma, but I think she is fine as she is. In that case, the parenthetical is distinguishing two units with the same name whereas with Soldier and Ninja it is distinguishing two pages with the same name and really has nothing to do with the unit.

        Loading editor
    • A FANDOM user
        Loading editor
  • Out of curiosity, did you want any help with translating/posting character profiles?  Or is it more a personal project?  I do have the character profiles 1 and 2.

      Loading editor
    • Sure. That'd be very helpful with how slowly I'm going through them, anyway. I'm fully behind the ideal of sharing as much information as possible, and not allowing that flow of information to be stemmed if it can be helped.

      I'll probably be cross-referencing translations you post, me being me, but I shouldn't be making changes if I don't have a very good reason. Work through them however you'd like.

        Loading editor
    • I'll replicate your method as best I can then, and post the JP text as well.  Feel free to edit it as you see fit.

        Loading editor
    • If you guys want to, please post the Japanese profiles so people like me can help translating them. Finding raws is impossible for me but I can translate to a certain extend. My last translation was Victoria's profile.

        Loading editor
    • A FANDOM user
        Loading editor
Give Kudos to this message
You've given this message Kudos!
See who gave Kudos to this message

Ad blocker interference detected!


Wikia is a free-to-use site that makes money from advertising. We have a modified experience for viewers using ad blockers

Wikia is not accessible if you’ve made further modifications. Remove the custom ad blocker rule(s) and the page will load as expected.