STO Awakening.jpg

Hi Gamepedia users and contributors! Please complete this survey to help us learn how to better meet your needs in the future. We have one for editors and readers. This should only take about 7 minutes!

STOWiki talk:Suggestion Box

From Star Trek Online Wiki
Jump to: navigation, search
Suggestion Box archives


This page is for Wiki related suggestions only. To request game features visit the appropriate forums. If your feedback does not comply with this rule, it will be tranfered to this site by an admin. Click the "+" button above to add your own suggestion, or "Edit" to reply to someone else's suggestion.


Fleet pages and template[edit source]

I was wondering if any Fleet has a page describing it. It appears to me none has, is this against STOWiki policy?

If not, I think we should create a template and encourage members to create pages about their fleet. This should also be a place where consistently list the fleets in order for the players to get more information and to figure out what fleet would suit their style the most. --Luca Mauri 22:04, 17 February 2013 (UTC)

I'm not sure if the previous admins ever actually wrote up a fleet page policy, but I am pretty sure they decided to disallow them. At least, I thought I had read something to that effect somewhere on the wiki, but I'm having trouble finding it now.
To be honest, based on what I've heard about other wikis that chose to allow guild pages, I'm of the opinion they are much more trouble than they are worth, even with a good policy framework to deal with them. They end up generating drama about whether to retain old ones, minor edits to these pages can start filling up recent changes, and fleets can end vandalizing the pages of others; in short, many other wikis found them to become unmanageable over time. Eyes User-Eyes-Sig.png 23:22, 17 February 2013 (UTC)
I see your points and I actually imagined something like this was the cause of no information on Fleets.
Still, it is my opinion that STO cannot be complete without at least some basic information about Fleets. What about a list maybe similar to STO User Hub?
I think we should find a way to integrate some information about fleets without risking serious troubles as you explained. --Luca Mauri 23:02, 18 February 2013 (UTC)
I'm not sure I agree or disagree with the idea that fleet information is important to be complete or that we should include some kind of hub page for fleets. For now, I'll just wait and see if anyone else wants to register their opinion on the matter. Eyes User-Eyes-Sig.png 02:45, 19 February 2013 (UTC)
I like the fleet page idea, I can also see how it can cause issues. One way to limit the issues would be to limit the edits, only by selected users, for example those who actually run the fleet, can only edit there page. Another idea is have all edits go under review, now that would cause more work for the admins, moderators. --Byll Helotis (talk) 22:47, 28 March 2017 (UTC)

Weapons update[edit source]

Any info on fleet or andorian weapons yet?

Request Resubmission - Powers Template[edit source]

I've been doing some looking into powers here on STOWiki, thinking about a new build. The pages you have are a great help, but there's somewhat sloppy, many are incomplete, and a few are even out-of-date (using the old skills system). So, I propose an overhaul of them to make them cleaner and easier to use. Part of this would be a template for powers, as follows (copy-pasted and upgraded from last time):

Name:
Icon:
Ranks: (I, II, and/or III)
Class: (Eng, Tac, Sci)
Area: (Space or Ground)
Type: (Buff/Debuff, may be more than one)
Source: (what grants this power - list all)
Cooldown:
Effect: (Basic summary of what it does)
Skills: (what skills will boost this power, if any)

The page itself would proceed to go into greater detail on exactly what each power did, including the effect BOff Points had on powers (for BOff Powers) and the exact numerals for each power's Rank. This combined would make Powers pages easier overall to use.

Feedback anyone? CPTNIce 03:00, 8 March 2013 (UTC)

Legacy of Romulus expansion and wiki UI style updates[edit source]

With the recent announcement of a playable Romulan faction, I'm wondering what prep work we should do for the wiki with regards to populating content pertaining playable Romulans (info pages for ships, NPCs, missions etc).

There's also new screencaps showing the updated in-game UI (which more closely resembles LCARS) - perhaps someone would like to update the wiki skin too?

Of course, all this is dependent on what we actually get when the expansion hits Tribble / Holodeck, but I thought you guys would like a heads-up. --Sumghai 08:02, 22 March 2013 (UTC)

I strongly advise AGAINST setting up articles of upcoming features. Look at Fleet Advancement System. It was written BEFORE Season 6 was released and still suffers from that. --Akira-sensei 11:44, 22 March 2013 (UTC)
We could make a simple "Legacy of Romulus" page and put everything we know about that update there. Individual pages like Romulan Republic can wait, though. - Mitchz95 17:13, 22 March 2013 (UTC)

STO Wiki Mobile Site?[edit source]

While playing STO I usually find something in the game while actively playing I would like to research, so I use my smart phone or a Tablet (I use Samsung Note II and a Nook Color)to access this wiki. I find it very difficult to to read and load on my mobile devices since there is no mobile or .mobi version of this wiki. I would suggest adding a .mobi or mobile version of the wiki, or even better an Android or Apple app. Thank you for any consideration duane17

Unless someone else is working on mobile apps for MediaWiki, I don't think that's on the horizon. I do believe there are plans to set up a mobile skin for our wikis, but I don't have any ETA on that. I'll follow up on this when I can. Eyes User-Eyes-Sig.png 01:28, 14 April 2013 (UTC)
Okay, I've confirmed that mobile skins for our wikis are planned for sometime in the near future. We don't have a specific ETA yet, though. Eyes User-Eyes-Sig.png 02:07, 17 April 2013 (UTC)

Search borked[edit source]

please look at the search feature, nothing is coming up for keywords.


also we need to create a currency converter

as a newb i do not know how much energy credits are valued compared to say GPL ?

we should have an easy 1 GPL = 1000 credits list etc or whatever the true values are

i have not played in a year and forgotten alot! thank you :)

Ship Weapons updates[edit source]

Will anyone be amending the ship weapons to include the newer ones (ie Nanite Disruptors)?

I think everything is in there now but Refracting Tetryons and Romulan Plasma. I plan to add those later this week. Asanad (talk) 01:13, 5 September 2013 (UTC)

But

What about the Solanae Dual Heavy Proton Cannons or the Protonic Polaron Cannon, Beam Bank, Beam Array or Turret or the Experimental Romulan Plasma Beam Array and the Voth Antiproton Dual Cannons. 02/12/2014

All of them are there except the Solanae Dual Heavy Proton Cannons, Protonic needs to be added to the ship weapon nav. Asanad (talk) 15:49, 12 February 2014 (UTC)

German section of STO Wiki[edit source]

In the german community forum, some users are interested in a german STO wiki. Is it possible to add another language to this wiki, so that german user can translate and add new articles?

I just helped open the German version of Neverwinter Wiki, so yes. There are two approaches we can take.
The traditional approach we use is to launch a separate wiki once enough content has been translated. Our rule of thumb is that the main page and every page linked from it needs to be translated before we'll launch a separate wiki. This involves making subpages at Main Page/de, Playing STO/de, and so on. All the German translations would also be added to Category:Translations/de. After that, we'd launch a separate wiki and then copy the templates, images, translated pages, and other miscellany over to the new wiki.
Our DOTA2 Wiki use a different approach that keeps all of the translated content on the same wiki. There are certain advantages, as it's easier to keep all of the templates in synch and linking between different language pages is effectively automatic, but the disadvantage is that adding translations to the templates makes them more complex. Also, the page names have to remain in English, so there's extra work involved in creating redirects from the German page name to the correct subpage, i.e. Hauptseite would have to be a redirect to Main Page/de.
Either way, for now, the translations end up on /de subpages, so the translations can start before any decision is made on which approach STOWiki would prefer to use. oOeyes User-Eyes-Sig.png 22:15, 19 June 2013 (UTC)
Thanks for that answer. So i have a look on the Neverwinter Wiki for the tradional way and asking for users in the german community who whants to help. Can you assist on that way and create and opening the german wiki for editing? DarthPetersen 07:49, 22 June 2013 (UTC)
Yes, when enough is translated, ask me to look it over. I may ask for more pages to be translated if I think anything important is missing, but generally, if the main page and everything linked from it has been translated to /de subpages, I'll get things rolling on launching a German wiki and I'll copy over the translated pages, templates, and other miscellany at that time. Not being a German speaker, though, I can't do much more than that. Someone else will have to work on moving the pages to their German names and updating the links. oOeyes User-Eyes-Sig.png 20:44, 22 June 2013 (UTC)
I have added a german Main Page to the wiki and a category for the Translation. How we proceed with categories? Will be there german category pages with /de or can we add the translated Sites to the english categories? DarthPetersen (talk) 13:11, 24 June 2013 (UTC)
This will depend on which approach we end up going for. For the traditional approach, using German category names would be best. You could even add the category pages to the translations category to allow them to be transferred over. The DOTA2 approach creates new categories with /de after the English name. If there's no consensus on which to do yet, maybe it'll be best to just do both for now.
Also, some templates, especially infobox templates, autocategorize, so unless the templates also get translated, the pages using them will end up in the English categories. I think, for now at least, that'll be okay. If we open a separate German wiki, those pages will end up being transferred to the new wiki anyway. If we go with the DOTA2 approach, we'll have to update the templates anyway. oOeyes User-Eyes-Sig.png 22:03, 24 June 2013 (UTC)

Lohlunat Festival.[edit source]

Considering the number of accolades, activities, and such

I believe the Lohlunat Festival should have it's own page.

Thank You Very Much

Just made Lohlunat Festival have its own page, Your Welcome - OmegaZeroX 2:15, 15 July 2013 (PST)

References[edit source]

I have seen a lot of pages with what are suppose to be facts about the changes made in the game. However, there are no links to see where the information can actually be viewed. Usually there are patch notes made by someone.

One example of this is here: http://sto.gamepedia.com/Mission:_Khitomer_Vortex/Walkthrough

In this walkthrough, it claims that the Scimitar will no longer cloak when someone is in 5km, that the cloaking is random. Then it references Release Note: April 4, 2013. This release note says nothing about this change ever being made, but does say that a change has been made that kept it from cloaking for an extended period of time.

Then, there are developers that have told myself, and others that there is still a 5km trigger that will cause her to cloak. If there are facts on this site, there should be links to show where they come from, instead of them just appearing.

Thank you,

Tim.

Can you provide a link of some sort to verify someone from cryptic indicated the 5 km trigger still exist? Asanad (talk) 23:47, 22 December 2013 (UTC)

Item tooltips[edit source]

Hi,

I'd like to make a suggestion about item/stat tooltips. When on an item page, there are usually links to the stats for that item. Instead of having to click on them, it may be more convenient to have the game description appear in a tooltip when hovering over the link. This could also be applied to item links. When hovering over them, you'd see a tooltip with it's stats/description.

Cheers.

Most wikis that have this feature are able to draw from a data-mining site to create the tooltips. I'm not aware of any for Cryptic's games. I've been told they are difficult to data mine, so this is probably why there don't seem to be any.
I wrote a script that allows wiki pages to be used as the tooltips on Neverwinter Wiki, but that wiki benefited from having the script from the start so that the pages could be set up appropriately from the beginning, where here it'd be a significant change involving changing a lot of existing pages. The community would have to be invested in moving the tooltip information to /Tooltip subpages for it to work. If there is interest, I could probably set up the script and needed templates sometime next week, but I probably wouldn't be able to contribute much to actually moving the tooltip data. oOeyes User-Eyes-Sig.png 12:19, 31 January 2014 (UTC)
I think having it work that way would be huge. I don't know what is involved to do this yet but it is definitely one of the things that I think would greatly improve this wiki. Looking at sites (my personal experience) wowpedia and wowhead, its so very useful. I'd be willing to put some time into making this happen. Asanad (talk) 14:02, 31 January 2014 (UTC)
After looking at neverwinter and wowpedia. I notice they both do it differently. Just out of curiosity how is it done on the wow site? Does it draw from wowhead like you mentioned earlier? Asanad (talk) 14:10, 31 January 2014 (UTC)
It looks like WoWpedia does draw them from the wiki, but it uses templates to identify which links should display tooltips in most cases. It seems there's an exception for items, but I'm not sure how that's working or if that approach could be used here. For the others, it must be using DPL to harvest information from the infobox, which wouldn't be my favorite approach. I'll look closer when I have time, but I doubt any tooltip system can be integrated without a lot of grunt work on articles.
Neverwinter Wiki's system examines each link when a page is loaded and attaches a tooltip if the given page has a /Tooltip subpage. And quite simply, the tooltip that's displayed is whatever is on that page, so it's very simple and flexible. The tooltip pages can be treated as templates to display the tooltip on the item page, such as {{:Tholian Crystalline Sword/Tooltip}}. oOeyes User-Eyes-Sig.png 19:22, 31 January 2014 (UTC)
Simplicity and Flexibility is probably the better route to go. No doubt adding tooltips to this wiki will be a lot of grunt work but I still think it would a huge improvement. Asanad (talk) 10:16, 3 February 2014 (UTC)
A while back I wrote a bit of CSS that made the tooltips look more like they do ingame now (see User:KarikaSlayer/common.css). Let me know if there's anything I can do to help. KarikaCommunicator 18:48, 31 January 2014 (UTC)

Update[edit source]

The tooltip functionality is currently in place. You can test it by hovering over this link: Tholian Crystalline Sword. You may need to refresh the page fully before it will work (Shift-F5 or whatever your browser uses).

To enable a tooltip for a page:

  1. The {{infobox}} needs to be copied to a new page called pagename/Info.
  2. The }} at the bottom needs to be changed to <noinclude>|nocat=yes</noinclude><includeonly>|nocat=</includeonly>}}
    • This prevents the infobox from assigning properties or categories to the /Info page, but lets it do so on pages it's used on. This means any other infoboxes we might want to use for tooltips will need to properly support a nocat parameter, so it's probably best to stick to items for now.
  3. On the original page, replace the whole infobox call with {{/Info}}. The /Info will now get treated like a template.
  4. You can use the page like a template elsewhere like this: {{:pagename/Info|nocat=yes}}. And in most cases, you will want the |nocat=yes.

Known issues and planned improvements[edit source]

  • STO has many long tooltips, so the positioning code may need to be made smarter to prevent tooltips from being cut off at the top or bottom.
  • An animated loading icon will be added to the loading tooltip when I can get one made up.

oOeyes User-Eyes-Sig.png 20:37, 7 February 2014 (UTC)

Very Nice. Karikslayers updated style changes to infobox looks good as well. I'm going to start adding these and see if there are any issues. Only thing I can think of now is Set items with multiple infoboxes on the page. I'll play with it some see how it goes. Thx Asanad (talk) 23:46, 7 February 2014 (UTC)
Last I knew, the set items usually had redirects set up. The thing to do for that is to set up an /Info subpage of the redirect page, then go ahead and link to the redirect to get links where the tooltip shows up. (It used to be considered bad to link to a redirect, but it seems they've backed off on that.) As for displaying the infoboxes, you can use the {{:pagename/Info|nocat=yes}} noted above to get the infoboxes on the set page. oOeyes User-Eyes-Sig.png 01:08, 8 February 2014 (UTC)
I think I gotcha. I'll mess around with it some and let you know if i have any problems Asanad (talk) 01:16, 8 February 2014 (UTC)

Time for a new Wiki skin?[edit source]

Are there any plans to update the wiki skin to match the current look of the game? The current skin is based on the old simple blue with loud outlines. A skin based on the current look of the game can potentially increase speed rendering since its more desaturated and features flatter colors.

Xaionik (talk) 07:38, 26 February 2014 (UTC)

Not at this time. I'd probably have to be the one to do it given the level of customization necessary, and currently I have too much going on between real life and wiki work to devote the necessary time to it. oOeyes User-Eyes-Sig.png 16:01, 26 February 2014 (UTC)

CSS change to fix Unique items having a different font to all other items[edit source]

This s a fairly minor thing, but has been bugging me for a while: items defined using Template:Item that use the Unique rarity end up with a different font formatting than all other rarities (noticable mainly due to using a serif font rather than sans-serif). This seems to be due to the CSS that formats items being defined for classes named .common, .uncommon, .rare, .veryrare, .legendary, and .epic, but not .unique

In theory this should be a fairly quick and simple change, but I'm guessing the CSS is not editable by anyone except high-level site admins... anyone know who I should be talking to? Trelfar (talk) 22:14, 20 April 2014 (UTC)

Yes, the CSS can only be edited by admins. But anyway, .ultrarare and .unique have now been added, so this should now be fixed. oOeyes User-Eyes-Sig.png 08:32, 21 April 2014 (UTC)
Great, thanks! That should assuage my borderline-OCD when looking at lists of items now. Trelfar (talk) 11:46, 21 April 2014 (UTC)

Star Cruiser vs. Assault Cruiser[edit source]

The assault cruiser needs to be swapped with the star cruiser as it is in the game because in the game they call the Soverign, Majestic and Noble class star cruiser while in the wiki you call it the assault cruiser. —The preceding unsigned comment was added by 93.143.110.243 (talk · contr)

Only the Mirror Universe Star Cruiser does that, because things are apparently different in the mirror universe. In the "prime universe", the Sovereign/Majestic/Noble classes are Assault Cruisers while Star Cruisers consist the Sentinel/Vanguard/Emissary classes. - Mitchz95 (talk) 19:20, 23 July 2014 (UTC)

Level-less icons[edit source]

It seems that sometime in the perhaps not to distant past, the Crytpic team started making level-less item icons for a good number of items, perhaps even all of them (one example being the Protonic Arsenal set), should we start utilizing them, and replace existing leveled icons with level-less ones? (and perhaps even remove the ability to specify a mark rarity in the icon, and other, templates?) --LordTrekie (talk) 02:08, 16 September 2014 (UTC)

Combat pets to which ship table[edit source]

I would not mind seeing a table that shows all combat pet options for all ships with hanger bays.

p.s. the shield amount for the jem'hadar dreadnaught carrier does not fit the shield percentage shown on the comparison chart for the dreadnaughts.

Fixed Upgrade Path items[edit source]

Any thoughts on how we could incorporate fixed upgrade path items into the wiki? This primarily would affect set items, so it would need to be something added to the item template that could be used to display variations in rarity without making it take up a ton of space. Perhaps some way when viewing the template to choose a rarity from some kind of drop down, or a way to scroll left and right between available rarities with arrows. Zernin (talk) 00:34, 3 June 2015 (UTC)

Don't all set items have a set modifier when they are upgraded to ultra rare? Maybe something could be added to the infobox to indicate what it would be for each item. Asanad (talk) 01:05, 3 June 2015 (UTC)

Doff Icon Index Update[edit source]

I was wondering if the 'Epic' and 'Fleet' Doff Overlays will be added to the STOWiki:Doff_icon_index page anytime soon. (I'm not sure if this is where I post a question such as this!) Thanks in advance!

Done! (ps, make sure to sign your stuff so we know who asked what. --~~~~)
--LordTrekie (talk) 14:31, 19 June 2015 (UTC)

Hi,

I think it could be good idea to introduce Temporal Cold War in the future. It would give opportunity to go introduce more Star Trek characters and could take players to Star Trek TV Shows Universe as well.

Another suggestion; would it be possible to swap between Space Traits and Ground Traits? When I'm doing space missions I always using 10 space traits and when I do ground I change all traits to ground, but it take time. Something similar to Star Ship load-outs.

Kind regards, Marcin

Mirror Danube Runaboue[edit source]

The Mirror Danube Runabout has 2 tactical console slots and no science console slot. The Wiki article states it has 1 tac 1 sci. 91.11.95.59 10:55, 20 November 2015 (UTC)

Fixed Asanad (talk) 18:45, 20 November 2015 (UTC)

New quality colors[edit source]

The game has been updated to include Ultra-rare and Epic quality items and personnel (i.e. duty officers). Unfortunately, there is no option for these color identifiers, nor the Ultra-rare item border (the Epic border is available) in the current templates. My suggestion would be to revise templates so that Ultra-rare items and doffs are neither listed as Purple quality nor use the Very Rare image borders, but instead are correctly identified as Indigo Violet quality and displayed with correct any erroneously Very Rare-bordered items corrected to display the Ultra-Rare indigo violet-colored image border (i.e. purple with barred corner instead of violet with arrows in corner). Epic, likewise, ought to be updated to Gold quality so that templates are not showing input errors. Gethralkin (talk) 01:01, 11 March 2016 (UTC) Gethralkin (talk) 23:57, 10 March 2016 (UTC)

Actually, the Ultra-Rare border is available on the site - it's violet, not indigo. The problem with the site not properly listing the Quality, however, does remain. -- Turbomagnus (talk) 00:09, 11 March 2016 (UTC)
Thanks for pointing those things out. I have edited my above suggestion accordingly. Gethralkin (talk) 01:01, 11 March 2016 (UTC)
Just so I understand exactly what are you saying can you provide a page where this is incorrect? Asanad (talk) 23:08, 11 March 2016 (UTC)
Think he means Sartis Krett, for example. It has arrows in the lower left corner, which are not present with the in-game version of Ultra Rare doffs and its frame doesn't have right shade of purple/violet. Lower right corner, for example, is currently kind of bluish, while it is more purple in game. -- Damixon (talk) 11:27, 21 March 2016 (UTC)

Ability icon templates[edit source]

Hi everyone, I wanted to hear your opinion on ability icon templates, and naming of ability icons. There is option to use Template:Ability icons and Template:AbilityiconAoY. {{Ability icons|<Ability name>}} is useful for abilities that have different icon for each faction (for example, Ability: Corbomite Maneuver) or icons that are exclusive for one faction (for example, Ability: Romulan Battle Cloak) as it shows that other faction don't have access to that ability. With 4 factions available, using the {{Ability icons|<Ability name>}} for abilities that have same icon for all factions will make it look crowded (for example, Ability: Enhanced Plasma Manifold, in my opinion. I'm guessing {{AbilityiconAoY|<Ability name>}} can be used here to overcome this, as it just uses the Federation icon variant. But if we will use just one icon, <Ability name> icon (<faction>).png format becomes obsolete, making the {{iconlink/icon|<Ability name>}} enough for ability pages which use same icon 4 times. --Damixon (talk) 23:59, 1 November 2016 (UTC)

I've been wondering about this, since whenever I edit pages recently I see it done in different ways, and usually just use whatever way was used before on that page. I think we should do whatever we can to reduce redundancy; file names should be whatever is most useful, since they're not 'visible' to end users, as they're not part of the presentation of the wiki. If I understand your proposal correctly, it's to use just one icon, without (faction) in the name, for abilities with the same icon for every faction? I guess I support that, since it does make sense for there to be a 'default' for cross faction. In the future if they add different icons, we can always move the file to the right name and add the others. DanPMK (talk) 03:18, 2 November 2016 (UTC)
Ability icons used to be blue for fed and red for kdf, but that was changed so I suggest using one icon if they are same for all factions. I checked, Template:AbilityiconAoY and Template:Abilityicon provide a similar result so they could be used for pages that already have uploaded icons so that we don't have to move them, which would conflict with pages where faction format generated an icon. So yeah, in the end, I don't see problem with leaving out faction from icon name for newly uploaded icons which are not unique. Problem is that {{iconlink/icon|<Ability name>}} would not link to ability page when icon is clicked on, because "Ability:" is missing from icon name. Template:Abilityicon would need to be adjusted so we could use {{abilityicon|<Ability name>}} even when there is no (faction) in the name. I don't know how to make that change. Thanks for the reply DanPMK --Damixon (talk) 12:12, 2 November 2016 (UTC)
I'm sure we could figure out the template change easily once the plan is all solidified. I guess upload an example icon and we can try some things out. DanPMK (talk) 13:44, 2 November 2016 (UTC)
Intel and Pilot abilities already use single icon on their ability pages and have icon named without (faction). There are more examples, but I guess those could be used as example. --Damixon (talk) 14:19, 2 November 2016 (UTC)
In any case, I do believe that ability names should exist in the main namespace as redirects to the ability article, just to aid people searching. So that might ameliorate the problem. DanPMK (talk) 21:53, 2 November 2016 (UTC)
I'll add Template:AbilityiconAoY to ability pages that qualify using the AutoWikiBrowser. Probably sometimes this week. --Damixon (talk) 00:11, 22 November 2016 (UTC)

Console updates[edit source]

I believe there needs to be more separation for the wiki regarding console updates. Considering Fleets just came out and there's no page for it I can't exactly just put it into 'current / upcoming events'. 64.113.177.152 12:59, 21 November 2016 (UTC)

I agree. We should start adapting to this change, maybe add some kind of an indicator to the top of every page which would show which platform has access to the content we are talking about. --PiralDorrm (talk) 19:46, 21 November 2016 (UTC)
Perhaps we can generalize Template:Testserver into something like Template:Availability. It could take different parameters like "PC" "XB1" "PS4" "Tribble" and then display the relevant information. So if something is on PC and Xbox but not Playstaton, or if it's on Console but still on Tribble somehow, it would all be readily apparent. I could whip something up if you want. DanPMK (talk) 23:27, 21 November 2016 (UTC)
Maybe some other multi-platform wiki (neverwinter online for example) already has something cooked regarding consoles so I'll let you know what I find. "Current and upcoming events" on main page could have separate section to cover all platforms, same for Upcoming content article. --Damixon (talk) 00:11, 22 November 2016 (UTC)

TOC improvements[edit source]

I'd love it if Tables of Contents for articles supported the noautonum and toclimit-# features described here, particularly for articles like 24th Century. DanPMK (talk) 01:46, 15 September 2017 (UTC)

The CSS rules have been added. oOeyes User-Eyes-Sig.png 10:21, 15 September 2017 (UTC)
Thanks! DanPMK (talk) 18:39, 15 September 2017 (UTC)

Ship costs (commas for thousands)[edit source]

One of the biggest problems on the otherwise-amazing {{Playableshipsbytype}} list for ships is that the cost section is often empty. This is caused by commas in the price on the ship's individual infobox, which isn't parsed correctly. Items with costs less than 1000, and with those whose price is written as "1000" and not "1,000" do show up correctly. Is there a way to fix the template to read commas correctly, or should infobox prices omit the commas? (This is probably fine for zen costs as 3000 isn't much harder to read than 3,000, but it may be annoying for dilithium costs that reach five digits.) Arkhain (talk) 00:50, 2 November 2017 (UTC)

I'm not sure what can be done with that template to accept numbers with commas. I tried to adjust it using formatnum -Help:Magic_words, but it didn't worked. I think removing the comma manually on each page is the only option. Anyone knows if this can be done differently? --Damixon (talk) 13:12, 2 November 2017 (UTC)
Separately, many ships have their price listed as a "Lock box" number, of the currency Lock Box. This does not sort well, either. Is it reasonable to put the price as 1 Lock Box, as on the Cardassian ships for example, or is there another way to wield wiki wizardry to make the text 'Lock box' show up in the price column? Arkhain (talk) 14:04, 2 November 2017 (UTC)
Not sure what could be done here, it has to be number. --Damixon (talk) 21:44, 2 November 2017 (UTC)
Check the Sphere Builder Denuos Dreadnought Carrier, it shows "1 or more Generic Lock Box v2.png" as its cost. I think it is better than 1 Generic Lock Box v2.png. Or we can have text instead of icon: "1 or more Lock Box". Any better idea as price of lock-box ships? --Damixon (talk) 21:22, 3 November 2017 (UTC)
I fiddled with the template:row and used the #ifeq feature to output "Generic Lock Box v2.png" if the input was "1 (LB)". I personally think just the Generic Lock Box v2.png lb icon is the best, rather than "1", or "1 or more", since it's so hard to apply a number to lockbox rng. I'm not sure if you can line up multiple #ifeqs to get multiple different text outputs based on coded inputs, but that might be an option for other things too. Arkhain (talk) 05:38, 5 November 2017 (UTC)
Nice! Yeah, {{LB}} is the best option out there. We should also enable the same thing for {{PPP}} (Phoenix Prize Pack) - it should replace most of the event currencies. --Damixon (talk) 21:21, 5 November 2017 (UTC)
I'm quite happy with #ifeq for the template lists, it's exactly what I was hoping. Still, using "1 (LB)" as a code has the problem of having the ship infobox itself display the price as 1 LB. I tried using #ifeq on the Template:Shiptypeinfo but it just added the test string instead of replacing the cost string. Is there a way to make it intercept the value of cost and just display the costunit, for certain values of cost? I was hoping we could do like, -1 cost for invisible cost values. Arkhain (talk) 19:16, 6 November 2017 (UTC)
It seems #explode function is required to make this work. Haven't played with it before so some testing would be needed. --Damixon (talk) 19:27, 6 November 2017 (UTC)

Bots?[edit source]

Have we thought about using bots at all? They could automate many things for us, like fixing broken/double redirects, managing categories and orphaned pages, and more. Shadowslasher410 (talk) 19:59, 2 November 2017 (UTC)

I don't have any experience with that, so if you know how to use them and set them up, I'm all for it. --Damixon (talk) 21:32, 2 November 2017 (UTC)

Faction infoboxes[edit source]

Hey, so we have infoboxes for everything else but I'm surprised there isn't one for factions. Below is just a few things it might be good to cover in it, but obviously it depends exactly what take it would be. There needs a bit of in-universe, but not too much or we'll just duplicate MA, but also not too reliant on faction info or it will be bloated for the main ones and threadbare for the minor factions. It would be good to give a taste of how the faction operates though, what their role is in the game.

Header text Header text Header text
emblem = KlingonSymbol.png
state_name = Klingon Empire
faction_status = Playable Faction
notable_species = Klingon, Gorn, Orion
location = Beta Quadrant

capital = Qo'noS
political_system = Feudal monarchy
foreignpolicy = Expansionist
leader = Chancellor J'mpok
alliancerelations = Member

imagepeople = KDFmob.png
imageships = Brel.png
emblem = FerengiSymbol.png
state_name = Ferengi Alliance
faction_status = NPC Faction
notable_species = Ferengi
location = Alpha Quadrant

capital = Ferenginar
political_system = Democratized Corporate Oligarchy
foreignpolicy = Mercantilism
leader = Grand Nagus Rom
alliancerelations = Friendly

imagepeople = Farek.png
imageships = D'kora.png
emblem = Vaadwaur.png
state_name = Vaadwaur Supremacy
faction_status = NPC Faction
notable_species = Vaadwaur
location = Delta Quadrant

capital = Vaadwaur Prime
political_system = Dictatorship
foreignpolicy = Expansionist
leader = Gaul
alliancerelations = Agressive, Iconian Servitor

imagepeople = RevolutionCrowd.png
imageships = VaadwaurHeavyArtilery.png

Scientifictheory (talk) 11:26, 5 November 2017 (UTC)

Good idea, we should have a template like that on faction pages. It also covers information that isn't mentioned in the {{Factionnav}} template so it would be nice addition. --Damixon (talk) 21:21, 5 November 2017 (UTC)
I've put a draft up at Klingon Empire. Template is factioninfo. I feel like I'm missing an ingame element that is useful. Also, the game doesn't seem to do larger scale emblems (flags), I'd like to include them but they're just not that common are they? Scientifictheory (talk) 07:42, 6 November 2017 (UTC)
I like this idea. Good job, Scientifictheory! As Damixon already said, it would help cover more info which isn't in the Factionnavs. Yes, the only problem is the lack of larger scale emblems - you'll find them for playable factions, but I doubt you'll be able to find them for anyone else. I'll look into it myself. --PiralDorrm (talk) 09:10, 6 November 2017 (UTC)
One thing, though. Might I suggest replacing the starship photo with a photo of the faction homeworld? (if one is in-game) --PiralDorrm (talk) 09:16, 6 November 2017 (UTC)
That is an idea, but my thinking over people and ships is it covers the two mob types which nearly every faction have and would be relevant when considering factions from an in-game perspective as opposed to an in-universe perspective. You'd want to identify the rough look of a ship and a ground NPC that a player would encounter. Now we could do the homeworld in addition to that, but three photos might be a bit much for an infobox - and the homeworld is linked. An alternative approach might be if we put together a single "postcard" image comprising what relevant images we have of the faction (like on Wikipedia city pages) but that would mean custom images for all, rather than simple re-use, which increases time investment in the project.Scientifictheory (talk) 09:48, 6 November 2017 (UTC)
Nicely done, looks good on pages of those three factions. Postcard image would be too much work so I'd rather limit it to two images. --Damixon (talk) 03:20, 7 November 2017 (UTC)
Headsup. I was going to do a separate box for species/races, but there is so much crossover I've built in options for that into the faction box so it can serve as either, or both. Still working out some kinks, but Vulcan, Jem'Hadar and Herald are examples where I've tested it so far. My aim is to cover the relevant parts already mentioned plus playability and traits unique/required for that species (where it exists for players or boffs).Scientifictheory (talk) 14:16, 8 November 2017 (UTC)

Species/Faction Portraits[edit source]

When the foundry is back up, I am planning to do a high resolution glamour shoot in there along the lines of;

  • Having both male and female generic species in one screenshot rather than two for the race pages.
  • Having a screenshot of all the faction species -maybe famous NPCs- in a single shot at an iconic location for the faction pages.

If you have any requests I can throw on the pile (maybe interactions between certain types of NPCs, or an image we have that really needs to be updated), let me know below and I'll try to grab a particular shot or combo as I'm going through.Scientifictheory (talk) 21:11, 10 November 2017 (UTC)

Possible Extensions?[edit source]

So, I was going through Mediawiki the other day, and I found these two awesome extensions that I think would really help improve the wiki. I checked and there shouldn't be any issues in terms of compatibility or anything, although one of them does require an extension we don't have (more on that below).

The first one is RelatedArticles, which, as the name suggests, adds a list of related articles and their descriptions at the bottom of a content page. It uses CirrusSearch (an extension we already have) to go through the site and collect all the related articles.

The other extension is GuidedTour, which after discovering it I totally wish they had something like this on the site back when I first started editing wikis. Basically, it lets admins create popup guided tours on wiki pages, which will help new wiki editors gain a familiarity with things like how to edit the wiki, upload files, using templates, creating pages, page guidelines, and all that stuff. Note that this does require the EventLogging extension, which is a framework for logging analytic events.

Obviously, oOeyes is the only one who actually has access (or permission) to actually do anything with extensions, but what do the rest of you think? Should we ask oOeyes to have one or both of them installed? Shadowslasher410 (talk) 23:29, 1 December 2017 (UTC)

Sounds useful, you can ask him on his talk page about possibility of implementing it here. --Damixon (talk) 22:07, 3 December 2017 (UTC)

What are the best Duty Officers to donate to the Fleet or trade in a the Academy?[edit source]

So I'm finding myself bloated with Duty Officers, and so it'd be nice if there was some list or research done for what are the best Duty Officers to donate to the Fleet, trade in at the Academy (both lower rank to trade in for a higher, and which overrated higher rarities should be traded for lower), or Execute for Incompetence (for Klingon players). Corollary to that, what Prisoners/Refugees should be traded in and which to keep for Assignments, that sort of thing. What Duty Officers are best as Active Space/Ground is obviously up to personal play style, so probably only lightly touch on that, unless there's an agreed-upon meta that I'm unaware of? --BarGamer (talk) 05:44, 8 August 2018 (UTC)

New Link to Game Based suggestions forum[edit source]

When clicking the "add your own suggestion" button, you are given a reminder near the top of the new page "This page is for Wiki related suggestions only. To request game features visit the appropriate forums 1" Well that link is dead, and a new one should be provided.

Link updated. In case there is a more accurate subforum it should link to - let me know so I can change it. --Damixon (talk) 23:49, 24 March 2019 (UTC)

A Fistful of Gorn walkthrough error[edit source]

The walkthrough says to go right after beaming to Paradise City, however the canyon is to the left (south on map). Just wanted to share this so other people don't wander in the wrong direction for half an hour like me..

Ship article names[edit source]

Alright folks, I have a radical suggestion: I want to change how playable ship articles are named. Most ships released in the past several years are advertised with a specific class name attached to it, but the naming is virtually always inconsistent between the C-Store, the Ship Requisitions NPC, and other names I've listed below. Taking inspiration from how Wikipedia handles things, eg. Nimitz-class aircraft carrier, I would like to propose the following name format to be used for most if not all playable ship articles, new and old:

  • Ship articles in general be named [Species] [Classname-class] Ship Type. For example: Paladin-class Temporal Battlecruiser
    • On the article itself, the ship class name in the title will be italicized, as is standard and seen on Wikipedia, eg. Paladin-class Temporal Battlecruiser (since we can't put italics in the URL name).
    • No species name for Federation, Klingon and Romulan ships, only Jem'Hadar, Kelvin Timeline and Cross-Faction ships.
    • Ship type will be uppercase as they have proper meanings in STO, including ones that don't exactly like Marauder or Interceptor, with a lacking ship type appended at the end for some of them (case-by-case basis).
    • Flight-Deck Cruiser will always be hyphenated.
    • Flight Deck Carrier will not be hyphenated as per the new standard.
    • Battle Cruiser will be used instead of Battlecruiser, for consistency with Flight-Deck Cruiser, Dreadnought Cruiser, et al.
    • Battlecruiser will be used instead of Battle Cruiser; while there are some ships that use "Battle Cruiser", all ships released in the past several years, including all T6 Battlecruisers, spell it as one word.
    • (T6) will only be appended on articles that would otherwise have the same name. The other tier name would also be added, eg. (T5), with the page name sans-parenthetical being a disambiguation page.
  • Alternate names will redirect to it, including:
  • Ships with multiple costumes from the get-go, mostly lower tier ships now, like Heavy Escort, would use the default (Akira-class).
    • We'd have disambiguation pages for other class names, eg. Akira and Zephyr would redirect to Akira-class and Zephyr-class (or maybe both to Akira-class), which would be a disambigs to all the ships that can use those costumes.
  • The {{{name}}} field in Template:shiptypeinfo will use the name as it appears in the Ship Selector menu, as this is the only ship name that every single ship has without exception (not all are in the C-Store, or purchasable via the NPC, or even have admiralty cards, etc.), even if it suffers from being a crappy name. It's a universal constant, so we should document that as the official name for that ship SKU. It just doesn't have to be the article name.
  • This would not affect any NPC articles.

I believe this system not only looks better, both making it look more professional and for consistency's sake, but that it will make it easier for users to find what they're looking for, whether searching here or on google or whatever search engine. And more importantly, we'll no longer be beholden to Cryptic's system of letting 5 separate employees name every ship multiple times via what I can only assume to be musical chairs.

Some examples
Current name New name
Denorios-class Bajoran Interceptor ("name-class") Bajoran Denorios-class Interceptor
or Bajoran Denorios-class Interceptor Escort
Miradorn Theta Class Heavy Raider ("name Class") Miradorn Theta-class Heavy Raider
Gagarin Miracle Worker Battlecruiser (no "class') Gagarin-class Miracle Worker Battlecruiser
Tholian Iktomi (no type!) Tholian Iktomi-class Science Vessel
Engineering Pilot Raptor (no class name!) Qui'Tu-class Engineering Pilot Raptor
Engineering Command Warbird (doesn't mention it's a Battlecruiser) Baratan-class Command Warbird Battlecruiser
Aves Dyson Science Destroyer (doesn't mention it's a Warbird) Aves-class Dyson Science Destroyer Warbird
Negh'Var Heavy Battle Cruiser (Battle Cruiser) Negh'Var-class Heavy Battlecruiser
Negh'Tev Heavy Battlecruiser (Battlecruiser) Negh'Tev-class Heavy Battlecruiser
Voth Bastion Flight-Deck Cruiser (dash) Voth Bastion-class Flight Deck Carrier
Herald Quas Flight Deck Cruiser (no dash) Herald Quas-class Flight Deck Carrier
Advanced Escort (T6) (bare-bones and has the parenthetical of shame) Hestia-class Advanced Escort
Fleet Ha'apax Advanced Warbird Fleet Ha'apax-class Advanded Warbird (T5)
Fleet Ha'apax Advanced Warbird (T6) Fleet Ha'apax-class Advanced Warbird (T6)
Fleet Ha'apax-class Advanced Warbird as a disambig

What does everyone think? DanPMK (talk) 08:15, 27 May 2019 (UTC)

Hey, I support this idea. Just a question - what would a Tactical Pilot Warbird be called? Okhala-class Tactical Pilot Warbird or Okhala-class Pilot Warbird? --PiralDorrm (talk) 19:45, 27 May 2019 (UTC)
The C-Store uses "Tactical" in its name so I would definitely name it "Okhala-class Tactical Pilot Warbird". DanPMK (talk) 06:54, 28 May 2019 (UTC)
Would the original titles also remain, as redirects? Otherwise it may break existing external links (Memory Alpha, Beta) to our articles. Kind regards, Markonian (talk) 21:36, 27 May 2019 (UTC)
Yeah absolutely, no reason not to. Most of them coincide with the C-Store or ship vendor name which should all be redirects anyway. DanPMK (talk) 06:54, 28 May 2019 (UTC)
My concern are lock box and lobi ships - we named ship pages to make them search-friendly on the exchange (in case someone c/p full name). But we could add name of the Special Requisition Pack under notes, for example, but I'm sure visitors will adapt to the new name. About using the Battle Cruiser, instead of Battlecruiser - I think in-game it is always one word, on every source that shows ship name, so it may be better to match what is in-game (then again, not a big issue if it is two words). Some ships like Light Cruiser don't have default class as it depends which costume you choose during the ship customization. This is the reason for a non-class name of the page so some exceptions would be present for lower tier ships. All in all, I like the idea, standardized name format would look better. --Damixon (talk) 07:00, 28 May 2019 (UTC)
I had not considered the Exchange name thing, but I think putting the requisition pack name in the lede will work. As for Battle Cruiser vs Battlecruiser, I checked the ship list and apparently they used "Battle Cruiser" exclusively at first, and then at some point they switched to "Battlecruiser" exclusively, including all T6 ships and a few T5s. So, in the interest of exchange searches, I would use Battlecruiser indeed and have changed it in my suggestion. And, yeah some exceptions for ships like Light Cruiser are fine with me. Not going for absolute uniformity here, just something that gets us to way more uniformity than we have now. DanPMK (talk) 07:19, 28 May 2019 (UTC)
Haven't been on for a week or two. What has been decided? Are you going forward with this? If you are, I'll gladly help if you want. --PiralDorrm (talk) 19:38, 6 June 2019 (UTC)
I pinged two of the other admins, was waiting for their input. DanPMK (talk) 17:53, 7 June 2019 (UTC)
Just for my 2c, using real class names does help identify ships. The various permutations of Cruiser/Escort and so on with just a vague descriptor doesn't really help me recognise what it is meant to be. The class name though does help. However when it comes to canon ships, what I'm really looking for is the canon name. Like, what's the Andromeda class? Oh, the T6 Galaxy, right I know what it is now. What's the Advanced Heavy Cruiser? Oh, the T6 Exclesior, right.Scientifictheory (talk) 06:45, 8 June 2019 (UTC)
Apologies for taking so long to respond. I was pretty ill this week. I'm also afraid I don't have that much to say. My usual advice on this is to follow the game, but when the game's inconsistent, that doesn't help. Coming with consistent rules of your own is the best alternative, and this seems like a good system. The only thing I could add is that it would be optimal to have redirects from all ship names used in the game pointing to the correct article when they don't line up. The same could be done to address Scientifictheory's concern as well, i.e. Galaxy-class (T6) to the Andromeda class article. oOeyes User-Eyes-Sig.png 21:00, 9 June 2019 (UTC)
Yup, my plan is to check what the ship's vendor, C-Store and admiralty names are and put redirects for all of them. In addition, I'll make a host of disambiguation pages... for example, I've made some now: anyone who looks for "Galaxy class" or "Monarch" will be find their way to the Galaxy-class disambig page which will lists all the ships that can use those costumes. Wanna make things as easy to find as possible. And, I hope you feel better! DanPMK (talk) 19:11, 11 June 2019 (UTC)
I've also done the Gemini-class ones as well. Look good? DanPMK (talk) 16:26, 12 June 2019 (UTC)
Looks good. oOeyes User-Eyes-Sig.png 02:08, 13 June 2019 (UTC)

Ship article names 2 - Piezo-Electric Boogaloo[edit source]

After getting some of this work done and speaking to SFC about this, I'm starting to have some second thoughts as to how this is going. There are 3 main issues:

  1. The article names are, of course, longer
  2. Ships on the exchange won't match their article names any longer
  3. We'll need to make a butt-ton of redirects both for general purpose and for our ship templates which are already very large.

As a result I'd like to alter the proposal to instead not add "-class" to the article titles. We'd still add all the class names where appropriate and italicize them as per the system above, so the general idea is the same (class names present and identifiable, will look more consistent and encyclopedic), but with less renaming work and FAR fewer redirects needed. I'd go back and fix all the current ones done in a blitz of editing to get it over with. How do you all feel about this? DanPMK (talk) 14:32, 19 August 2019 (UTC)

I support this. If class name would be italicized I think we can leave out "-class" if it means less hassle, and exchange-search friendlier name. --Damixon (talk) 14:42, 19 August 2019 (UTC)
Yeah, I agree. We've made good progress, but there's still so much work to be done. And some names are comically long now. --PiralDorrm (talk) 06:55, 20 August 2019 (UTC)
I'd be tempted to say drop things like Tholian, Bajoran, Orion and Tzenkethi, although that only aids a subset. Dropping -class doesn't shorten by much but is at least fairly common. Warbird is another option but that is fairly instructive.
Of course they're comically long because some of the compounds they've been given are comical. Perhaps for the page name (but not the other mentions on the page and elsewhere), we could arbitrarily shorten some if they exceed a certain length. For example;
  • Xindi-Insectoid Olaen-class Heavy Strike Wing Escort > Olaen-class Escort
  • Shamshir-class Operations Dreadnought Warbird > Shamshir-class Warbird
  • Universe-class Temporal Heavy Dreadnought Cruiser > Universe-class Cruiser
- Scientifictheory (talk) 15:42, 25 August 2019 (UTC)
I'd rather we return the names to how they were, or use the full designation like DanPMK first proposed. --PiralDorrm (talk) 17:12, 25 August 2019 (UTC)
I don't want to abridge the names, since I do want as much info in the title as possible (long but dense), so I'll start on with the proposal I posted here, which for most ships is the old system. I'll get on that today so I can get this whole darn thing over with. DanPMK (talk) 20:20, 29 August 2019 (UTC)
Good luck! Sorry for just giving you more work with the Romulan ship pages. --PiralDorrm (talk) 22:37, 29 August 2019 (UTC)
Nah it's all good my dude. I actually just spent a while writing up a template (Template:Lede) to help reduce work in the future and am excited to roll that out. Since an edit is an edit, it doesn't feel like any more work :D DanPMK (talk) 22:55, 29 August 2019 (UTC)