Mass Effect Wiki
Advertisement
Mass Effect Wiki
Forums: Index > Projects > Verbatim shop entries


The form below serves as a tool to describe the project. The form is intended to be as specific as possible to what the project is to accomplish.

  • Please place all comments under the Comments heading.
  • If there is a discussion page linked, then be sure to check it out as well.
  • Also please do not create any articles unless all the details have been worked out, or at least the majority of them.
  • Once the article/project has been created/finished, please put a mention that the article/project is completed and provide a redirect to the relevant article/s and talk page/s.

If any new things come up after the project proposal's passing, then please shift the discussion to the relevant article talk page/s.

If you have any questions on how to fill out the form, or any other question, please refer to the Project Forum talk page.

Project:

slight addendum to the shop article manual of style to allow for transcription of flavor text verbatim from the kiosks
Currently developed by: User:Temporaryeditor78
Developer(s) notes: voting open
Status last updated:

Page location:
Page should contain:
Supporting links or images: User:Temporaryeditor78/Shop_practical_mockup
Discussion on: here

Other Notes

description isn't as self-explanatory as it looks.

firstly, shop texts for weapons/armor/mods/fish are pretty much what we see when we look at them at the bench (ME3) or armory (ME2). they're already transcribed on the relevant parts of the wiki. what i'm aiming for here is

  1. to expand on the shop articles' right-hand text so it looks less like an infobox-only article
  2. to give a home for the overlooked loar present in some of those texts

so, in the interest of reducing redundancy, only verbatim texts from the following items should be allowed:

  • quest items not picked up during missions (reaper code fragments, etc)
  • unique items native to the shop (collected tennyson, peruvian whiskey, etc)
  • miscellaneous items not relevant to combat (model ships, personal apartment stuff etc but NOT fish)

placement? below the intro text. format is as follows:

== Items ==
;Aquarium VI
With so many exotic species of fish available in today's galactic market, it takes an expert to maintain an ideal aquarium. This VI automatically dispenses food, adjusts the temperature, pH, and algae content of the water, and even talks to the fish when you're not around, leaving you free to enjoy your aquatic friends without fear of killing them.
;Model Alliance Kodiak
A scale model of the Alliance Kodiak Shuttle.
;Reaper Code Fragment
Asari war strategists have encountered difficulty predicting Reaper movements due to poor understanding of Reaper thought processes. A scavenger is willing to sell a Reaper processor that he discovered among the debris from Sovereign's attack on the Citadel several years ago. This intel could dramatically improve the efforts of asari forces.
;TM88 - Peruvian Whiskey
Tasty yet Medicinal -- The Perfect Gift
Smooth and smoky with a hint of heat, each sip of TM88 has a story to tell, and each glass has a story to inspire.
TM88 isn't one of the Earth's top-selling beverage exports for nothing. Known for having both a calming influence and the ability to stimulate blood flow, TM88 is the only alcoholic drink endorsed by the Medical Board of Sur'Kesh.
The price for TM88 includes deposit. Please recycle.

see the mockup above in supporting links for a more practical view of the proposed changes.

for now, this is merely a brainstorming session, though i do intend to have this voted on sooner or later. sound off below.

Comments[]

It's a good idea and the proposed items would pad the shop articles nicely. Not much else that I can think of; if any help is needed in putting this together, I'll gladly lend a hand. Elseweyr talkstalk 20:22:36, 2014-11-04 (UTC)

Good idea, no objection. --DeldiRe (talk) 21:12, November 4, 2014 (UTC)

i'm in a toss-up on how to display the entries: === headers === or ;simplehighlighting.

with headers, we can have easy #lookuptags for searchability and in case of redirects to specific entries. thing is, i don't see the point as the shop pages are fairly short and we can see all items at first glance regardless of display resolution. there's also no point in having the option to edit individual sections there as they're all verbatim text. for these reasons i'd have to suppress the table of contents in this approach unless the article grows justifiably long enough.

;this form on the other hand is much more elegant in my opinion, but loses the searchability feature of headers. we'd have to manually specify with some more coding, which defeats the aim of simple elegance set in the first place. the items that would qualify for a specific redirect to the shops aren't many, though (kaidan's whiskey, ashley's gifts, missed ME3 quest items), which makes this approach a viable one.

i can go whichever way, but of course i'd rather have just one standard in place. T̴̴͕̲̞̳̖̼̱͒͛̎͒ͫ̃ͧeͩ̈̽̈҉͓̝̰̼̦̫̤̀͠m̫̪̪̯̻͎̫̅̇̓̇͌̚p̸̙̝̓̓͌ͨ͆ͣͥ̂̕o͒̽͐̽͏̞̬̻͕͔͕͚̰͍͠͞ṙ̢̞͚͈̹̰ͨ̓ͭ̈́̌ạ̢̧̪̹̺̺̣̹̲͂͆̏ͪͨ͒ͭř̹͈͜͠y̷͍̻̜̹̼̾̽̈́e̵̹̼̟̦͚͐̈́͌͘d͉̲̣̻͉̱͗̅ḭ̷̻̆͋̆̓̔͝t̨͍̦̫̗͂̅̍̋̆ͩ͝ộ̫̟̬̳̝̲̾ͫ̒̿ͮ̑̚rͯ̎ͨͭ̄̿̽͛҉̠̫̱̠̘̘̲́ͅ7̩̻ͤͩͨ͝͡8̜̣̙͇̻ͨ͛͛̆͒̆̽̒͐͜͡ ͥ̍̉̃̇ͥ̓ͨ͏̕҉̥̹͓̗̤̠̖̤ (talk) 04:20, November 5, 2014 (UTC)

I'd go with simple highlighting. Like you mentioned shop articles will still be short, so the need to point a redirect or link to a specific section might not be as great as for longer pages. Since the items would be few, however, manually coding in a few anchors is probably not that big of a deal either. As we already employ anchors in other articles and might do so in the future, one option to is to make use of an anchor template:
   {{#if:{{{1|}}}|<span id="{{{1|}}}"></span>}}<!--
    -->{{#if:{{{2|}}}|<span id="{{{2|}}}"></span>}}<!--
    -->{{#if:{{{3|}}}|<span id="{{{3|}}}"></span>}}
   etc.
Multiple anchors could be entered at once if needed: {{anchor|Anchor 1|Anchor 2}}, which would reduce clutter. Elseweyr talkstalk 10:45:23, 2014-11-05 (UTC)

I think this is a step in the right direction, but I see some issues. I think one problem with only putting entries in for certain items is we will no doubt have people trying to add entries for weapons/fish/etc, thinking the listing is incomplete and not realizing that's on purpose. So I think it might be a good idea to add "see also" entries for those items.

Also, the article should say how you get the discount. TheUnknown285 (talk) 22:01, November 5, 2014 (UTC)

Well the items are all present in the shop infobox and since this project includes an MoS blurb, it will be easy to refer to if edit conflicts arise. As for discounts, the ME2 shop articles already have the sections detailing the merchant-specific ones; seeing as discounts obtained in ME3 pertain to all stores, including the same note of it in every shop article seems a little redundant. Elseweyr talkstalk 23:10:29, 2014-11-05 (UTC)
i'm not sure multiple anchors in one template call is feasible since the whole thing is dependent on the span declarations' locations in the page - please elaborate? T̴̴͕̲̞̳̖̼̱͒͛̎͒ͫ̃ͧeͩ̈̽̈҉͓̝̰̼̦̫̤̀͠m̫̪̪̯̻͎̫̅̇̓̇͌̚p̸̙̝̓̓͌ͨ͆ͣͥ̂̕o͒̽͐̽͏̞̬̻͕͔͕͚̰͍͠͞ṙ̢̞͚͈̹̰ͨ̓ͭ̈́̌ạ̢̧̪̹̺̺̣̹̲͂͆̏ͪͨ͒ͭř̹͈͜͠y̷͍̻̜̹̼̾̽̈́e̵̹̼̟̦͚͐̈́͌͘d͉̲̣̻͉̱͗̅ḭ̷̻̆͋̆̓̔͝t̨͍̦̫̗͂̅̍̋̆ͩ͝ộ̫̟̬̳̝̲̾ͫ̒̿ͮ̑̚rͯ̎ͨͭ̄̿̽͛҉̠̫̱̠̘̘̲́ͅ7̩̻ͤͩͨ͝͡8̜̣̙͇̻ͨ͛͛̆͒̆̽̒͐͜͡ ͥ̍̉̃̇ͥ̓ͨ͏̕҉̥̹͓̗̤̠̖̤ (talk) 13:26, November 6, 2014 (UTC)
Just like articles might have several different redirects, I guess it's not inconceivable that sections could sometimes use multiple anchors too. It's true that they would likely rarely be needed, but I just figured it doesn't hurt to include the option if such a template is created. For a bit of an artificial example, see w:c:elseweyr:Intel Terminal#Prejek (note that anchors can be inserted directly into section headers as well). Elseweyr talkstalk 13:52:51, 2014-11-06 (UTC)
i see now where you're coming from. however, that system is more complicated than it's worth. for simplicity's sake, page anchor = unique identifier. redirect = as many as needed, all using the same custom anchor.
i've updated the mockups above for further inputs/clarifications. T̴̴͕̲̞̳̖̼̱͒͛̎͒ͫ̃ͧeͩ̈̽̈҉͓̝̰̼̦̫̤̀͠m̫̪̪̯̻͎̫̅̇̓̇͌̚p̸̙̝̓̓͌ͨ͆ͣͥ̂̕o͒̽͐̽͏̞̬̻͕͔͕͚̰͍͠͞ṙ̢̞͚͈̹̰ͨ̓ͭ̈́̌ạ̢̧̪̹̺̺̣̹̲͂͆̏ͪͨ͒ͭř̹͈͜͠y̷͍̻̜̹̼̾̽̈́e̵̹̼̟̦͚͐̈́͌͘d͉̲̣̻͉̱͗̅ḭ̷̻̆͋̆̓̔͝t̨͍̦̫̗͂̅̍̋̆ͩ͝ộ̫̟̬̳̝̲̾ͫ̒̿ͮ̑̚rͯ̎ͨͭ̄̿̽͛҉̠̫̱̠̘̘̲́ͅ7̩̻ͤͩͨ͝͡8̜̣̙͇̻ͨ͛͛̆͒̆̽̒͐͜͡ ͥ̍̉̃̇ͥ̓ͨ͏̕҉̥̹͓̗̤̠̖̤ (talk) 15:13, November 6, 2014 (UTC)
Sure thing, whatever works. Everything looks good to me. Elseweyr talkstalk 23:17:06, 2014-11-06 (UTC)

vote opened. time to get this over with. T̴̴͕̲̞̳̖̼̱͒͛̎͒ͫ̃ͧeͩ̈̽̈҉͓̝̰̼̦̫̤̀͠m̫̪̪̯̻͎̫̅̇̓̇͌̚p̸̙̝̓̓͌ͨ͆ͣͥ̂̕o͒̽͐̽͏̞̬̻͕͔͕͚̰͍͠͞ṙ̢̞͚͈̹̰ͨ̓ͭ̈́̌ạ̢̧̪̹̺̺̣̹̲͂͆̏ͪͨ͒ͭř̹͈͜͠y̷͍̻̜̹̼̾̽̈́e̵̹̼̟̦͚͐̈́͌͘d͉̲̣̻͉̱͗̅ḭ̷̻̆͋̆̓̔͝t̨͍̦̫̗͂̅̍̋̆ͩ͝ộ̫̟̬̳̝̲̾ͫ̒̿ͮ̑̚rͯ̎ͨͭ̄̿̽͛҉̠̫̱̠̘̘̲́ͅ7̩̻ͤͩͨ͝͡8̜̣̙͇̻ͨ͛͛̆͒̆̽̒͐͜͡ ͥ̍̉̃̇ͥ̓ͨ͏̕҉̥̹͓̗̤̠̖̤ (talk) 10:23, December 25, 2014 (UTC)

Voting[]

yep[]

  1. T̴̴͕̲̞̳̖̼̱͒͛̎͒ͫ̃ͧeͩ̈̽̈҉͓̝̰̼̦̫̤̀͠m̫̪̪̯̻͎̫̅̇̓̇͌̚p̸̙̝̓̓͌ͨ͆ͣͥ̂̕o͒̽͐̽͏̞̬̻͕͔͕͚̰͍͠͞ṙ̢̞͚͈̹̰ͨ̓ͭ̈́̌ạ̢̧̪̹̺̺̣̹̲͂͆̏ͪͨ͒ͭř̹͈͜͠y̷͍̻̜̹̼̾̽̈́e̵̹̼̟̦͚͐̈́͌͘d͉̲̣̻͉̱͗̅ḭ̷̻̆͋̆̓̔͝t̨͍̦̫̗͂̅̍̋̆ͩ͝ộ̫̟̬̳̝̲̾ͫ̒̿ͮ̑̚rͯ̎ͨͭ̄̿̽͛҉̠̫̱̠̘̘̲́ͅ7̩̻ͤͩͨ͝͡8̜̣̙͇̻ͨ͛͛̆͒̆̽̒͐͜͡ ͥ̍̉̃̇ͥ̓ͨ͏̕҉̥̹͓̗̤̠̖̤ (talk) 10:23, December 25, 2014 (UTC)
  2. No objection --DeldiRe (talk) 10:59, December 26, 2014 (UTC)
  3. Elseweyr talkstalk 14:58:43, 2014-12-30 (UTC)

nope[]

meh[]

Advertisement