FANDOM

61,151 Pages
A FANDOM user
  Loading editor
  • Hey, I know you've been less active recently. Wanted you to know that I've read Upon Arrival now and had a few thoughts. The writing is decent enough—a few grammar nitpicks exist of course—but nothing too distracting. In these very short stories, it can be difficult to truly flesh out a conflict and resolve it with such limited wordcounts, but I did feel this one was lacking a central core of conflict, even if internal. It reads more like the introductory scene for a video game level set on a new map, or perhaps an interactive tour, and so it doesn't frame the conflict well enough to truly come into its own. It'd be more fitting as a piece of a larger work rather than a standalone. I've started on No Chaos and that one seems much better in that regard.

    Cheers!

      Loading editor
    • Thanks, Ataru! I appreciate the feedback, and I pretty much agree with your assessment. Perhaps some day I’ll revise, but it isn’t high on my list right now. If/when you finish No Chaos, I’d love your thoughts on it too. I wouldn’t be so bold as to claim it’s amazing, but I do think it’s significantly better than its predecessor. Thanks again!

        Loading editor
    • I've read No Chaos now, and I like it much better than Upon Arrival in terms of narrative structure. The central conflict is well-framed and I like the issue you brought up about intervention and the role the Jedi play in resolving conflict—it's one of the classic dilemmas of wielding power. However, I did feel the ending was a little too impersonal and didn't really dive into Jordo's mind as much as it could have to internalize the conflict. Also, the story had a handful of puzzling things that distracted me. Why wouldn't Jordo have simply looked up what a Cathar was if he was curious about what they looked like? Why does Zhar send the apprentice off to a 'delicate off-world operation' with no details other than to "Trust in the Force?" If he's going with another Master, why not simply say that Master So-and-So would fill him in? I know that reciting the Jedi Code is kind of a thing, but I feel it's overdone here. There's so many random Jedi Code insertions at inopportune times that it ends up being distracting. I also don't think it's quite so simple to just pop a crystal into a lightsaber to make it work.  Technically, there's a smattering of various grammar things, but nothing that stands out as too outrageous. I don't love that "said" is used so much, but Sakaros has at least made me aware that some editors ~~are wrong~~ prefer to keep dialogue attribution simple as possible. I think it definitely shows significant maturation as a writer from On Arrival in that you are able to construct, frame, and resolve the conflict, but it leans a little too much on the Jedi Code IMO. Cheers!

        Loading editor
    • Thanks so much for reading! I appreciate the feedback immensely. To briefly respond to a few of your points:

      • Cathar: I weirdly hadn’t considered this at all and will be revising that moment as such.
      • Zhar: It’s meant that Zhar knows Jordo knows Jaci, and he’s doing something nice(?) by surprising Jordo. He knows Jordo isn’t actually going without further guidance. I guess that’s not clear though.
      • Jedi Code: if it’s overdone, it’s overdone. I don’t have much of a defense here. If I feel particularly inspired, I might look at trimming a few of them.
      • Crystal: Although “pop it in” is meant a bit euphemistically, I’m fairly certain it has, actually, been depicted as pretty much that easy. That said, I don’t recall precisely where, so the “canon” status of that is definitely up in the air. If you have a suggestion for a different phrasing, I’d be happy to hear it.
      • Grammar: You’re welcome to fix any grammar issues and/or point them out to me, but you’re also definitely under no obligation.
      • Said: Also not sure what to say here. It’s pretty standard practice not to overuse colorful dialogue tags. YMMV.

      Thanks again for the overall notes though! It’s nice to hear from someone as thoughtful and practiced as yourself.

      P.S. If you’re planning on reading some of my older stories, as suggested by your Reading List, I wouldn’t set your expectations too high.

        Loading editor
    • A FANDOM user
        Loading editor
  • Hey there, I was an old user on this wikia a few years ago and I'm planning to delete all of my pages I've created as well as any photo that I've added for characters I made a few years ago on this wikia. I don't use this wikia anymore and I really would appreciate it if you can delete each page and picture I've created and added, since I can't delete them myself. I am 100% positive of my decision to delete the pages I've made and you have my permission to do so. Hopefully you can understand. Thank you so much and thanks for your understanding.

    Here are the links to those pages:

    https://swfanon.fandom.com/wiki/Tiberius_Starcade

    https://swfanon.fandom.com/wiki/Maximus_Starcade

    https://swfanon.fandom.com/wiki/File:Maximus.jpg

      Loading editor
  • Hey man! I'm contacting you (& the rest of the administrative team) to provide prior notice of an upcoming RFB vote on my nomination of Sakaros for Bureaucrat. Naturally, as standing Bureaucrat, your opinion on the matter is particularly welcome, & I'd encourage you to weigh in & voice your thoughts on the nomination if you have the time. The nomination is expected to go live this Saturday, May 2nd, & conclude on May 9th, provided no extension is required. Cheers!

      Loading editor
  • Hey! Could you weigh in here? Apparently Sak doesn't have the user rights permissions necessary to amend or remove the "Expand these articles" module from Special:Community, but you probably do as Bureaucrat. Thanks!

      Loading editor
  • I wanted to make sure you're tracking this proposal. I'm waiting until there's a week left to weigh in so it doesn't look like the admin team is putting a hand on the scale (although the scale seems to have tilted pretty hard without my help), but since we've had extensive discussions about this very issue in the past, I thought you might want to weigh in.

      Loading editor
  • 15WA Hello, I'm Sakaros, Star Wars Fanon Administrator and host of the Fifteenth Wiki Awards! Since you've been an active contributor here on Star Wars Fanon in the last year, I'd like to invite you to take part in this year's Wiki Awards in celebration of the best fanon & fan fiction our wiki has to offer!
      Loading editor
    • A FANDOM user
        Loading editor
  • Boss, do you mind weighing in here? Additionally, we're still waiting on your guidance here.

      Loading editor
    • I’ve replied to both. I appreciate the message as I don’t recall getting anything for that older one, which is unfortunate. Then again, my current breakneck lifestyle of job + grad school is... intense, to say the least, so it’s possible I just slipped up and missed it.

        Loading editor
    • Got your back, Boss. Good to hear from you, too; it's been far too long.

        Loading editor
    • A FANDOM user
        Loading editor
  • Hey man! Sak & I got to discussing templating during our time in Chat yesterday & came up with a proposal governing user contributions to the Template namespace we'd like you to look over. Sorry in advance for the wall of text—I feel an overview of the key points is in order so as to provide you the requisite context.

    Regarding user-made templates, I've since been operating according to the precedent you tacitly set here, here, & here & outright stated here that "if a similar template already exists among the officially supported & maintained templates, that template should be transcluded in place of a newly created duplicate." In most cases, I've generally gone about implementing this precedent in one of three ways: 1) redirecting the duplicate template to the official template, automatically transcluding the official by default, 2) replacing the duplicate's in-article transclusions with the official template before deleting the duplicate, or 3) updating the official template to reflect desired changes (for example, if a user creates a duplicate because the primary template has not yet been converted to mobile-friendly XML, I update the main template accordingly & delete its duplicate).

    I've generally been pretty liberal in my policing of the Template namespace due to the desire to reduce redundant clutter on the namespace, ensure a standardized aesthetic per the Layout Guide, & respect mobile contributors by ensuring only officially supported, mobile-friendly templates are used. Regarding the first two points, issues of aesthetic consistency have always been the purview of the administrative team—as I told Sak in Chat, that unstated precedent is the reason you two committed to my suggested overhaul of the infobox styling without feeling the need to submit a consensus track thread to the community first (to quote, "a Wiki-wide transformation like this isn't quite a Consensus Track issue..."). In my opinion, templates, infoboxes or otherwise, should share a unified aesthetic & appear similar on any page when viewed on any device.

    In addition to ensuring a unified design aesthetic, the requirement that users only transclude officially supported, readily maintained, & mobile-friendly templates also guarantees that all users—contributors & anonymous mobile viewers alike—can access pages on any device without issue, per content portability best practices. From what I gather from Community Central threads, a large segment of Wikia's viewing audience & even contributor base is made up of mobile viewers. As such, I figure enforcing the use of officially supported templates optimized for mobile is better than allowing a redundant mess of broken, half-working templates to clutter the namespace. If it were up to me, I would follow Wikipedia's precedent & lock down the Template namespace entirely with the MediaWiki namespace—while I would welcome user suggestions for new templates (just as Sak welcomes suggestions for new infobox CSS themes for MediaWiki pages), I believe it's best that the creation & editing of templates be left to those versed in template creation & mobile content portability best practices (incidentally, this is Wikipedia's approach as well, encapsulated in the template editor user right).

    Since I don't think we can lock down the namespace without submitting a request to Wikia Staff, Sak & I came to the consensus that we should instead have a forum subpage dedicated to user-submitted template proposals. The benefits of such a system would be two-fold: 1) to allow us to check if the proposed template already exists & redirect the user to an extant equivalent accordingly, or 2) allow the user to make a compelling case for either an inextant template's inclusion based on its potential for widespread use or the modification of an existing template by means of the addition of new fields. Per the MediaWiki documentation regarding their intended usage, templates should ideally be useful to multiple users in multiple contexts on multiple pages, not exclusive to overly specific use cases. A proposal system would help ensure that all templates exhibit such wiki-wide utility while not outright limiting user input regarding the creation of new templates.

    Your thoughts?

      Loading editor
    • Apologies for the late reply; I don’t recall ever getting an alert for this.

      While I appreciate your work with the template namespace, and I also see the value of unified design and functionality, my initial hesitation that jumps right to mind comes from templates like {{UNSWS}}, which I think users have always created (go back to Brandon’s ASWS and beyond), and which I think have real value. I have a hard time quickly jumping to limit users’ ability to do so without excessive red tape. I’m open to something, though, as your ultimate goals do seem like something worth striding for.

        Loading editor
    • Perhaps I should have clarified a bit more—the main subject of this discussion is infobox templates, not navigation or advisory templates like the aforementioned UNSWS. The latter rarely show up on mobile anyway as they are not built with Wikia's infobox XML & are not (usually) intended to even appear on mobile devices.

        Loading editor
    • Ah, my bad. I’m totally onboard with limiting infobox template creation. I think it’s kind of a no-brainer; as I believe I’ve said before, nearly every infobox need should be met with something already available.

        Loading editor
    • Alright then, with your permission, we'll go about implementing some form of infobox suggestion forum moderating the creation of new 'boxes & the modification of existing ones based on user request.

      Good to see you again, by the way! (:

        Loading editor
    • A FANDOM user
        Loading editor
  • Hello there.

      Loading editor
    • A FANDOM user
        Loading editor
  • Still need you to weigh in here and issue guidance here.

      Loading editor
    • View all 6 replies
    • It seems to me that the “|bg1=“ from the template isn’t passing along to the ”{{#if:{{{BG1|}}}|{{{BG1}}}|94C7D1}}”, but that’s just a reckon, and I haven’t the foggiest how to fix that either.

      Unrelated, I think you should consider a “Category:Images from the UNSWS” given the increasing array of original commissioned images you’re curating.

        Loading editor
    • This reply has been removed
    • A FANDOM user
        Loading editor
See archived talk page
Give Kudos to this message
You've given this message Kudos!
See who gave Kudos to this message
Community content is available under CC-BY-SA unless otherwise noted.