Jump to content
Hotmail and Outlook are blocking most of our emails at the moment. Please use an alternative provider when registering if possible until the issue is resolved.

Overview

About This Club

https://forums.homecomingservers.com/clubs/2-unofficial-homecoming-wiki/?do=overview
  1. What's new in this club
  2. BlackSpectre has it covered above but I'll share a couple of keybinds I use in case that might be helpful. You could probably make macros of these as well if you want. The conprint portion gives me feedback as to which type of screenshot I have just taken. COMMA "conprint "UI ON"$$screenshotui 1$$screenshot" CTRL+COMMA "conprint "UI OFF"$$screenshotui 0$$screenshot" I've attached a transparent overlay that I have overlain on screenshots that show a badge marker. I made it myself so it might not be quite as nice as some you see on the wiki, but it might work well enough. It doesn't seem to want to attach as a file, but you can right click and save as to download it. And I just realized you needed one for history plaques, so I created this one
  3. Use the slash command /screenshotui to both disable (0) and enable (1) the UI. https://homecoming.wiki/wiki/Screenshotui_(Slash_Command)
  4. The assemblage of wiki pages that comprise The Players Guide to the Cities is not only huge, not only incomplete and unfinished, but I think the title needs to be changed as well (it's just too long!). In fact, it's such a mess that the whole thing might need to be reworked or eliminated. If we are allowed to post/host the official game guide from NCsoft, that might be a much easier solution. Here's a guide that was published for the Canadian gamers http://www.cityofheroes.ca/game_info/official_guides/official_city_of_heroes_manual.html . I also have another version of the guide released in the US, and also a City of Villains Guide, and maybe even a Going Rogue Guide (not sure about this one). That said, there are many pages in that huge TPGTTC wiki guide that are extremely useful and no matter what should not be removed. In some cases it's the only place at the wiki that the information is mentioned. Proposed title change from "The Player's Guide to the Cities" to simply "Player Guide". Alternate titles could be "Game Manual", "Game Guide", "Player Manual". What do you think?
  5. I thought it being a good idea to add pages for the new Kallisti badges, so I started to add a 'Patron of the Arts Badge' article. No big deal, except I couldn't find any information how to do a screenshot without the UI - so those pictures suck. Any idea? Likewise how those nice crosshair + text were made. Would also be nice to find something about that somewhere. Gruss H.
  6. OK. So from what I'm hearing is... do whatever you like as long as you preserve the history, more or less. Re: changing the wiki policy on player guides -- in the last 4 years I've only seen 1 person with a plan to put a player guide on the wiki (and I don't even think they followed through with that). So I guess it's not much of an issue. Therefore, I'm going to go ahead and change the policy page myself. No-one has offered an objection to eliminating player guides, so I guess it's ok. And I'll go ahead and bring all the player guides into the wiki proper. While I do that, I'll look them over for inaccuracies and data that's no longer current at Homecoming. If there are any player guides that are purely opinion, I'll add a comment at the top of the page noting that. So when free time pops up, I'll start working on this project. Thanks for talking @Doc_Scorpion, @AboveTheChemist amd @Kai Moon. Appreciated.
  7. As for copyright issues, Paragonwiki is GNU FDL, so is Homecoming Wiki. FDL allows copying and modifying, as long as the authors get credit. 1) Forking to a new site, with the same license, and importing the edit histories (credits), was okay 2) Editing a page adds your name to the history, without taking anyone else's off, so is okay 3) Using the Mediawiki "move" function to move a page to a new title preserves its history, so is okay 4) Writing a new page based on an old page, without the old page's history (no credit to previous authors), might not be okay TLDR From a copyright standpoint, just edit and move if needed, it's fine
  8. On mobile, the wiki still looks like this, and my mobile-friendly edits still do nothing. Any updates? $wgVectorResponsive should be "true" for Vector 2022. And mobile anonymous users should be served a responsive skin (like Vector 2022) by default.
  9. Like, it's a wiki. It's weird for anyone to own a page (other than userspace). Everything's fair game for edits.
  10. Can the Search box even be limited so as to not show the old guides? Honestly, your suggestion is a lot more work. By co-opting the guides we merely have to update them. Takes a lot more to write one up from scratch. However, what you suggest could be done in 2 steps, even without limiting the search engine: 1) write a new guide/article 2) delete the old one. That would essentially do the same thing. And there’s no reason to create a link to the old guide. Remember, that same old guide is accessible right now at ParagonWiki.com. Nothing would be lost if we deleted it and replaced the old guide with a new one. The old guide wouldn’t even need to be credited unless the author of the new guide took wording directly from it. Practically speaking, I doubt we could contact the original authors of the guides and ask permission to co-opt and rewrite them. So many players from 20 years ago are just not around anymore. Their email addresses and other contact info we might have could have easily changed in 20 years. we probably don’t have their real names. We could try, but what if there’s no way to contact them? If you want to talk about ownership and copyrights… the original authors gave permission for ParagonWiki to publish their work, not our Homecoming wiki. So we shouldn’t even have the guides, legally… especially since they were not really part of ParagonWiki, and were disavowed by the wiki. I don’t mean to be alarmist, because practically speaking these old guides are abandoned. And even if the authors are still around, I’d bet they wouldn’t have any problems with us co-opting the guides. If, in the event they discover their guide has been co-opted, and are not honored by the reverence we’ve given them, then we could simply remove it and write a new one… but what are the chances of that happening? All this said, @Doc_Scorpion, I’m glad you at least see a need to do something about the guides. In order for me to start doing something, I need our wiki admins to weigh in on the issue. @Michiyo? Do we co-opt the guides and update them (my preference), or do we write new guides and replace them? If the latter, then please delete all of the player guides right away, and change the policy of this wiki to reject player guides in the future (which I think should be done anyway). Official wiki policy: https://homecoming.wiki/wiki/Homecoming_Wiki:Article_Guidelines P.S. Looking over the player guides category I see “player guides” in there that aren’t player guides. Meaning, they’re wiki articles. For example, all of the “Players Guide to the Cities” pages are wiki articles. So we can’t just delete everything in the category. Sadly. We’d need to look each doc over.
  11. You missed option 4 - writing new guides, using the old guides as a reference where appropriate. Once that is done, remove all references to the old guide/point them at the new guide. A link on the new guide's page should be the only way to reach the old page.
  12. There are many player guides at the wiki, nearly all of them are left-overs from the Paragon Wiki days. The players who wrote them are no longer updating or maintaining them. Most contain obsolete information and no longer completely apply to Homecoming. Players are reading them and noticing that there is a lot of incorrect information in them. So... what do we do with them? When I see this notice, it means "hands off" to me. I am not permitted to edit it. It's not mine. It's not even the wiki's. It seems to me we have 3 options: 1) leave it as is and ignore them. Let other players read it and conclude that there is a lot of incorrect information at the wiki, and therefore the wiki itself is not very useful. 2) Delete the player guides. This eliminates the issue altogether in one foul swoop. 3) co-opt the player guides. Bring them into the wiki and within the purview of wiki editors. Make them OURS. Take responsibility for them. Fix them and maintain them. You know my opinion. Ignoring the various player guides is bad mojo for the wiki. It's an easy way for others to unfairly criticize our work here at the wiki. Deleting the player guides will end up erasing a lot of very important information that is only available in these guides. Just look at the Demo Editing guide, or the Chat Bubble guide. The information in these guides is pretty much essential. So deleting them would hurt both us and players who come to the wiki looking for answers. That leaves co-opting the guides as really the only option in my view. What do you think? https://homecoming.wiki/wiki/Category:Player_Guides
  13. It's kinda funny that a new trial was released since I posted this that is Cimerora themed, meaning that now every still-existent Trial Zone has a roughly corresponding trial, now.
  14. OK. I've written up an article for using colors at the wiki. Please check it over and let me know if you have any suggestions, additions, etc. https://homecoming.wiki/wiki/User:BlackSpectre/Testthis2
  15. I found out this is not true! After doing a little research, I discovered that when the wiki goes into dark mode, it INVERTS the brightness (from dark to light, and from light to dark) and changes the colors into their complimentary colors. It then flips the complimentary colors to the opposite side of the color wheel. It results in some weird approximation of the color. So none of the colors we see on in light mode will be reproduced exactly in dark mode. This is why when we make text red, for example, it turns into a weird off-red pink color in dark mode. In general, the lighter the text color, the darker that color will be in dark mode. Conversely, the darker the color, the lighter the color will be in dark mode. So dark blue turns out to be a very bright blue in dark mode. Rule of Thumb: AVOID LIGHT COLORS FOR TEXT Here's what the notes using dark blue looks like in dark mode: Here is a cool contrast checker that might be useful, however it does not use the CSS filter that dark mode uses at the wiki, so the colors will be different than what we see on the wiki. https://webaim.org/resources/contrastchecker/
  16. Oddly, red is the color used when quoting a dev, and you can find it in the various Quote templates. It’s a leftover from paragonwiki but red to me is a warning color. Like “Don’t click this button or your toon will self destruct!” I don’t actually know how exactly dark mode works, which means I’ll need to do a little more research before anything is decided.
  17. Hmm, I think I see what you mean. The heading structure you did makes more sense. I'll give it a shot.
  18. Well it seems like I already got my answer. XD
  19. So I've been rebuilding the Salvage related pages recently, adding in missing items, sorting them by the rarity or special context, adding in item caps, unifying the language between the pages, etc, and I already finished the Event and Special pages. https://homecoming.wiki/wiki/Event_Salvage https://homecoming.wiki/wiki/Special_Salvage I was about to rebuild the Invention page in a similar way until I realized that that page used a ton of DynamicPageList code, same with the Incarnate page. https://homecoming.wiki/wiki/Invention_Salvage https://homecoming.wiki/wiki/Incarnate_Component So my conundrum is should I rebuild the pages and remove the DynamicPageList code, or should I learn how the DynamicPageList code works and rebuild he page with better DynamicPageList pages?
  20. What about Red? Red looks good on both Light and Dark Mode? Unless Red is being used for something else on most pages?
  21. I am in favor of black italics. Visible on both settings without worrying about how a single color looks against either. I definitely agree with OP, the gold on white is really bad. It also doesn't show up that well in darkmode—but a user shouldn't havce to switch to dark mode just to read something regardless.
  22. Scroll all the way down to the very bottom of the wiki. You'll see "Privacy policy About the unofficial Homecoming Wiki Disclaimers" then "Dark mode." Click on that. Italics, or maybe a more neutral color like a green?
  23. Dark mode. Right. That would definitely be true. How would I see the wiki in dark mode? So italics then?
  24. Dark blue would most likely create the opposite problem, where it's hard to read when in dark mode.
  25.  

×
×
  • Create New...