Jump to content

About This Club


  1. What's new in this club
  2. Would it be possible to allow .ogg files to be uploaded to the hcwiki? Mainly so the Music page can be brought up to date. Currently we can only upload .png, .gif, .jpg, .jpeg, .webp.
  3. Hooray! Thanks very much for the swift response!
  4. "No False Pages found" I grabbed a snapshot of the DB, and ran a query to delete all pages between the 2 indexes you indicated above. Thank you for the investigative work!
  5. Okay, apologies for the travelogue writing style, but this post was originally written as an edit to the above post while I was figuring this out, but I just kept finding issues so it's a new post. Basically, this isn't just relegated to a handful of Tip missions as I originally thought. As a mini conclusion: Every page in the "Mission:" "Mission talk:" and "Property:" Namespaces on the wiki at time of original import has an invisible, un-editable duplicate page, with the same title but differing Page ID, found outside of their respective Namespace. They were created as a result of the import from the Paragon Wiki and it's screwing up Categories throughout the wiki making them very inaccurate. Admin intervention will be required to extract and delete these. @Michiyo This appears to cover Page IDs 47140 to 48373. Part 1 - Curid Looking up the manual to dpl has led me to find what I believe to be the root of the issue. I thought the Category was at fault, when actually it's the pages themselves. By using the dpl parameter 'showcurid=true' on the Alignment Missions page it can be seen that these listed pages appear to have two Page IDs. For instance 'A Long Line of Spirits' has two IDs 48057 and 49308. 49308 is the correct working page, and is properly part of the Mission: Namespace, which we'll call here the 'True' page. Whereas, 48057 has the same Page Title, but is not under the Mission: Namespace and thus doesn't display the Infobox template (as it checks for a Mission: Namespace so it doesn't show if the page is transcluded) and has not been updated by minor edits in 2020, which we'll call here the 'False' page. Attempting to edit these False pages using the edit button on the page makes you redirect and start editing the True page. And editing the False page directly by adding '&action=edit' to the curid in the address bar causes any changes made to instead affect the True page, making these False pages unmodifiable by normal users, since I assume the system applies edits based on Page Title not Page ID. By adding '&action=info' to an address with a curid, you can view the Page Information for a False page without being redirected to the True page. For instance here is the page information for 48057, and you see it has a longer Sort Key, since it isn't in the Mission: Namespace, compared to the True Page's information, which has the truncated Sort Key, and a more recent edit history. So my theory for potentially fixing this issue is, if the function exists, to either merge the False Pages with the True Pages, or to delete these False Page IDs directly rather than by Page Title. The list of False Page IDs for Rogue Isles (Villains and Rogues) missions is as follows: 48070 48074 48078 48093 48129 48142 48166 48167 48172 48191 48057 48059 48077 48094 48097 48105 48131 48137 48139 48169 48173 48181 48039 48044 48054 48082 48087 48110 48111 48113 48114 48130 48132 48147 48162 48164 48174 48175 48189 48193 Part 2 - The Issues Most unfortunately, having had a look about at other mission categories such as Shauna Stockwell Missions, you'll see the same issue of twice as many pages counted as there should be, compared to its Paragon Wiki counterpart. It looks like this is an extremely widespread issue where most Mission pages have a duplicate non Mission: Namespace page that shares it's title, created when the pages were imported. Oof. Which brings us to the true cause of this bug in the case of missions. From what I have observed, it looks like any page in a Namespace that had only a <noinclude>[[Category]]</noinclude> appears to also have a Main Namespace False Page equivalent also in that category, which is basically every mission on the wiki. This is why the other Tip Missions Categories are fine, since they use the conditional Infobox to specify the category, not a <noinclude> tag, so their duplicate pages are uncategorized. At time of Import all of the Rogue Isles Villain/Rogue tip missions had the standard <noinclude> tags method in addition to their infobox. Edit: Actually it appears unrelated to noinclude or categories. I suspect it is simply any page that was in "Mission:", "Mission talk:" and "Property:" namespaces, copied and not put in the correct namespace, and copied again into the correct namespace slightly later. It looks like nowhere else on the wiki uses a lookup to display categories in the way Alignment Missions does so its at least a mostly hidden problem to standard users. With this information, it's a simple matter of adding "namespace=Mission" to the Alignment Missions pages DPLs to only show True Pages, thus fixing my initial issue. However, the true problem lies with Categories which can't do such omissions. It makes it impossible to update existing Mission categories correctly, with False pages with old information left inaccessible and polluting the categories. It also substantially messes with tracking of these pages in Categories like Missing Dialogue, Work In Progress and Incomplete. These will in their current state, never be able to be brought to 0 without these Fake Pages being removed. For instance, here is a False Page of a mission I moved and updated just days ago to instead reference the 5th Column. False Page. True Page. True Page moved. The False Page will remain forever standing in for it's True Page in categories, even when that True Page has been deleted. An extreme case demonstrated by Mission: Common - Take Package to Stephanie Peebles, a deleted page that remains in the category Candidates for Deletion, as it has a False Page still there with the delete template that had been applied back on Paragon Wiki, keeping a dead page in an important category. If you search Common - Take Package to Stephanie Peebles, this False page shows up as the second result. Part 3 - Root Them Out So to go even further than those IDs above, any Page ID with Mission: in the title that is not in the Mission: Namespace needs to be deleted, without removing it's corresponding same-titled Page that is in the Mission: Namespace. One way these can be distinguished is by their Sort Key. True Pages will have a truncated Sort Key that excludes 'Mission:', whereas False pages have a long Sort Key that starts with 'Mission:'. Interestingly this prevents them showing up in Searches that start with "Mission:", as that assumes you are then looking within the Mission: Namespace, only showing those results. Using DPL with "namespace=", "showcurid=true" and a "titlematch=Mission:%" shows pages with Mission: in the title, but only in the Main namespace. This can reveal the first 500 of these False Pages IDs in the linked urls since DPL seems to only be able to show 500 results at a time. Here is a link to a test page with the below dpl running. {{#dpl: |namespace= |resultsheader=There are %PAGES% False Pages in Main Namespace displayable on this page. |titlematch=Mission:% |allowcachedresults=false |shownamespace=false |showcurid=true |noresultsheader=''No False Pages found'' }} Edit: Part 4 - Range Since the pages seem to have been ported in alphabetical order, it's looks like all Page IDs from 47142 to and including 48333 may be these False Mission Pages 48334 to and including 48373 seem to be False Mission Talk: pages that are duplicates in the Main namespace. These had no category at all, since they shouldn't ever be categorised, perhaps the reason why they were also duped. Also IDs 47140 and 47141 are dupes of the Property Namespace. So it looks like 47140 to 48373 could be safely deleted to fix this issue completely. Edit: Having run some quick tests, that's all I can find. Three False groups, all within 47140 to and including 48373. All the other namespaces seem unaffected.
  6. Thanks, added to the slash commands list!
  7. Just wanted to mention I noticed that the slash command /buildsave is not included on the list of slash commands page.
  8. Speaking as the angel of cynicism I quite like the idea that people who want to change them have to get set up to edit the Wiki, because we could really use more people who are. (The more I think about this the more I think, yeah, just keep them as a gateway edit...)
  9. Would it not be better to link to the Google Docs spreadsheets where these lists are maintained and updatable by the community as they are built?
  10. I like it. The list for Everlasting is LONG but being the RP server that doesn't surprise me. As long as new entries are put in the right categories I don't see any issues, but if folks don't abide by that then making it sortable might be worthwhile. That bridge is a ways down the road though. As far as which wiki it is on, I don't have strong feelings one way or the other. I would assume the HC wiki has more registers users that could potentially edit the lists, so it might be better to house it on the HC wiki and just link to it from the FBSA wiki. I have spent almost no time on the FBSA wiki though so I might not have the best grasp of the kind of content that is best suited for the FBSA wiki.
  11. GM Kal has been creating https://hcwiki.cityofheroes.dev/wiki/Indomitable_Base_List (and the four obvious equivalents). I feel a bit ambivalent about whether it should be done here or on the FBSA Wiki. What do other people think?
  12. Thanks for these tables @Bopper. I intend to add the per-card breakdown tables into a new section below the existing drop tables on each super pack page, though I'll be changing the 'Cards' heading to 'Weight' as I feel that's a more accurate description of the value in that column. For the existing main drop tables, the value I'd like to add to them is the overall percentage chance of receiving that specific card, per pack opening. Unfortunately I'm a maths dunce, and have no idea how to figure that out, so I'd need some help there! Edit: Finished adding the breakdown tables. Thanks very much!
  13. For the big tables, it used to have a column called Repeatable. If it's easy enough to add back in, you could re-title it as Count and then enter the amount for each card.
  14. There is a ton of good info in this thread, based on info that came from Faultline, about super pack drops and rates. I incorporated some of it into the Super Pack page, but incorporating the info from some of the bigger tables into the specific super pack pages will require a bit more effort. If anyone wants to tackle this, feel free. If no one else can, I will try to get to it eventually, but I've already got a couple of wiki projects that I have neglected that I need to wrap up before I start on another.
  15. Getting an error when uploading images, they then fail to display any thumbnail images on the site: Error creating thumbnail: /bin/bash: /usr/bin/convert: No such file or directory Error code: 127 See the error here: https://hcwiki.cityofheroes.dev/wiki/File:Winter_Forest_1.jpg Working file here: https://hcwiki.cityofheroes.dev/images/8/8b/Winter_Forest_1.jpg Worried to upload anymore in case I fill the place with dead images! Edit: Unrelated to uploading. Simply new thumbnails cannot be created. Edit 2: Resolved!
  16. I had a little heartburn over how to handle the updated Melee and Ranged AoE set category names (formerly PBAoE and Targeted AoE, respectively) on the powersets pages so I wanted to note my rationale here. For instance, this power can use Ranged AoE enhancements: The name displayed there where I put the red arrow is actually controlled by a template called Template:Set Targeted AoE Damage. I modified that template to display 'Ranged AoE' rather than 'Targeted AoE', then moved the template itself to a new page called Template:Set Ranged AoE Damage. That way, existing powerset pages that still contain the call to the Targeted AoE template will be redirected to the new Ranged template, and any new powersets pages that get created can use the new Ranged template. I went through the same process for the Melee AoE/PBAoE templates. Ideally, I think each existing powerset page that contains calls to the old Targeted or PBAoE templates should be edited so that the template calls use the new templates, but that would be a time consuming and somewhat tedious process. In the meantime, I think the edits I have made are a fairly simple fix to get the updated AoE category names to display correctly. And if the consensus is that the old template calls are OK as-is, then I won't worry too much about editing the existing powersets pages. Edited to add that if there is some unknown-to-me bit of wiki wizardry that can be invoked to change the old template calls automatically, I would be all for such a solution.
  17. Please ignore the request in my previous post. I finally figured out where to look in the leaked game data and I was able to track down the drop information for Unbreakable Guard, Reactive Defenses, and Preventive Medicine. Looks like they all follow the same schedule as Annihilation (A & B are set, C & D are SA, and E & F are TF), which makes sense considering all four were introduced in i24. Thanks again for the help! Edit: The wiki has been updated with this info as well now.
  18. I've added this info to the wiki now, thanks again Faultline! If I could trouble you for one more bit of info, do you mind checking the drop pools for Unbreakable Guard (Damage Resistance), Reactive Defenses (Defense), and Preventive Medicine (Healing)? Those three sets came in with Issue 24 (along with Annihilation) and as of now they all show up as 'Set' (Pool A) drops. I suspect some members of those sets might be be from the other pools. Or, if that info is viewable in the piggs via a pigg viewer, I am happy to look it up myself if you can just point me to the right place to look. I've checked a few places but haven't had any luck so far. Thanks again! Edit: Slight clarification, Preventative Medicine does show different drop pools on the main enhancement sets page but I suspect that it was probably just an edited copy of Numina's Convalescence. I don't necessarily know that it is wrong, but I suspect that it is, and the individual enhancements within Preventative Medicine all show as Pool A on their respective pages.
  19. Fantastic, thanks so much for the info! I'll take a look at the drop pools and see if I can find the correlation to the notation you provided. My hunch is that "SA" corresponds to pool B (mission drops) and "TF" corresponds to pool C & D (random rare recipe rolls).
  20. Internally the reward tables are called "Set", "SA" (Story Arc) and "TF" (Task Force). There's also the PVP tables. I'm not sure what letters they all correspond to. Annihilation, Bombardment, Synapse's Shock: A & B are Set. C & D are SA. E & F are TF. Sudden Acceleration: A, B & C are Set. D & E are SA. F is TF. Power Transfer: A, B, C & D are Set. E is SA. F is TF. Artillery, Preemptive Optimization: A, B, C, D, E & F are all Set. Experienced Marksman: A, B, C, D, E & F are all PVP.
  21. Great points @Aberrant, thanks for posting that. Point #2 had (briefly) occurred to me previously, but the rest had not. I just started last night to work on implementing my idea and still have some work to do but I'll definitely take these thoughts into account and will likely be back for more discussion once I've gone a little further.
  22. Was just thinking about this, and just wanted to rattle off a few other potential issues. I know this is the case with the procedural repeatable missions of papers/police band, but may also be the case with some regular missions and arcs. Missions can be pulled from a pool of environments (similar to how they're categorised in Architect based on tileset and size), so any attempt to document all the potential map images for these may be an insurmountable task. This is likely more common with older contacts. For these and most other missions, the displayed maps are not a single static texture, but are generated on the fly based on the tiles used. As far as I'm aware, basically any map that displays in the yellow-orange-brown style is generated in this way, even unique maps like you'd find in the interiors of the Lambda Complex I-Trial. The only way to get suitable images of these maps would be to take a screenshot of them in game or manually cobble them together from the dozens of textures that make them up (not recommended!). Many missions have multiple map images usually separated as floors and some consisting of a static texture exterior and a multi-texture interior, that would then likely have to be combined into one composite image vertically. To prevent huge numbers of red missing files all over the wiki where they are unlikely to be fulfilled, it may be sensible to add an {{ifexists}} to the map image call, similar to how it's handled for the small contact image in Template:Mission Briefing, so if no image currently exists on the wiki, it will just display the small text stating the map name as it was before.
  23. Ah ok, I was not aware of that, thanks for the heads up. I'll still give it a shot but I will definitely not get my hopes up!
  24. Hidden can be a pain in the arse as it by default spans the width of the page. I spent ages trying to get the NPC Text template to shrink if there's something right aligned and I'm still not happy with it, so I wouldn't recommend it for this personally, but if you can make it work go for it! Edit: Finally fixed my issues with NPC Text funnily enough! Now looks near identical to the old Paragon Wiki version. The secret is nesting it in a table so it will properly squash if there's something in the way.
  25. Fantastic, thanks for the feedback! I spent some time this afternoon looking through the missions for about 150 contacts and while I saw plenty of instances of map name displayed as they are in the mission I linked above, I didn't see any instances of an actual map. So given that plus your input I feel reasonably safe that I can tinker and not break anything existing. On a side note, I was thinking about how to display the map, and it occurred to me that I might want to put it in a 'hidden' box to avoid spoilers, such that the user would click 'Show' to display the map. So, I may try to do that if I can, but I am not totally convinced that it's not overkill so if I can't get it to work then I'll just display it as a normal image.
  26. Nope, that's all it does, just puts the map name aligned right at a small size. Here's the relevant part of the template: {{#if:{{{Map|}}}|<div style="float: right; font-size: 75%; margin-left: 2em;">Map: {{{Map}}}</div>}} It displaying the map image as well would be a great change I think!

  • Create New...