Jump to content

PCGamingWiki will use a Single Sign On (SSO) system to bridge wiki and forum accounts which is ready for testing. You may login using the 'Login with PCGamingWiki' button on both the wiki and the forum, which will soon be the only option.Β If you have any issues please message Andytizer on Discord.

Aemony

Administrator
  • Content Count

    91
  • Joined

  • Last visited

  • Days Won

    14

Everything posted by Aemony

  1. Most likely due to the report being a bit unfocused and not clear on the details, and possibly not providing them with a good POC that showcased how it easily it can be used to obtain elevated privileges. Luckily making the vulnerability public helped it gain exposure, prompting Valve to take action and solve the issue.
  2. Aemony

    Tomb Raider Mouse Helper (for TR1-5)

    A new recompiled version of the script have been uploaded by @Suicide machine to clear the false positives of the file. If it where to trigger false positives in the future yet again (which I sorta expect, seeing how it's using AutoHotKey to monitor the system for key presses to enable its functionality), users can follow the instructions in the Modification section of the file description to recompile the executable file themselves, which might clear the false positives.
  3. Of the below three possibilities, which one do you find most likely to be the case? A nefarious actor have obtained access to Epic's internal systems. Instead of going crazy and making big bucks of all of the millions of accounts they have access to, they only make charges against a few random accounts at a time. A nefarious actor downloads a publicly available password dump and tries known email and password combinations against Epic's sign-in page, and finds a couple of accounts that reused their password across multiple services. A nefarious actor sends phishing links to potential victims to a custom webpage that has been crafted to look like a legit sign-in page for Fortnite, instructing users to sign in using their Epic account to obtain free "V-bucks" (or whatever they're called), and users fall for it and hand their accounts and passwords over. Personally, I'd say the second or third ones, as a lot of users still fall for phishing attempts and password reuse is extremely common and few users (even technical minded ones) applies proper password management for their accounts and services. This is probably even more true for Fortnite in particular, which have repeatedly been mentioned to have a lot of young players. Epic Games is not responsible for either the second or third possibilities. They're only responsible for the first one. An argument can be made, however, that the situation of the hacked accounts might have been partially influenced by Epic's lack of forcing some basic protections unto their users earlier. For example, EGS did not require email verification on sign-up for the longest of time. While this by itself isn't an issue, it does mean that multi-factor authentication in the form of sign-ins requiring an randomized access code sent to the mail address wouldn't be possible on a newly created account, and therefor additional protection for the account wouldn't be available. But that is sorta true for most services or websites, and if that alone was enough to shift the blame from the users (whose bad password management allowed it to happen) to the service provider, then that sorta can set a dangerous precedence for other services and websites, I think... Yeah, that's the tweet I was thinking of. I tried to find it myself but couldn't, so thanks for finding it! πŸ™‚
  4. I am still waiting for more details about this lawsuit coming out since... well... it seems as of this moment to be baseless. Nowhere from what I can tell have neither Check Point nor Epic Games concluded that the vulnerability they found and fixed was ever exploited by anyone (I believe Tim Sweeney on Twitter mentioned the opposite, in fact), which makes the number of affected users by that vulnerability in specific a big 0. Fixing security vulnerabilities before they're found and exploited "in the wild" should never result in a class action lawsuit, as it seemingly have done here... Even Check Point's own report on the vulnerability uses phrasing such as "could have allowed a threat actor" as they also seemingly did not find any indications that the vulnerability was actively being used and exploited by bad actors. Beyond that, users whom have lost access to their accounts most likely lost that access due to a lack of appropriate security on their own part, through e.g. reusing passwords, or being affected by malware on their PCs, etc, which all are outside the ability of Epic to prevent. Honestly speaking, in terms of preventive action, Epic Games takes a much more active approach that I've publicly seen from organizations. Checking accounts against known password dumps online and resetting the password for those affected is a slowly growing occurrence in IT, but I am not aware of any corporation within the video games industry that does this yet, except for Epic. So yeah... We'll have to see where this goes, but I don't expect it to go anywhere since seemingly nobody have actually been affected by the vulnerability this whole class action lawsuit seems based around...
  5. Version 1.0.0

    6 downloads

    This is a mirror of the official patches available on http://patches.ubi.com/myst_4_revelation/ as that site can at times fail to load.
  6. Nah, you would've seen it here if that were the case: https://pcgamingwiki.com/w/index.php?title=Glossary:VorpX&action=edit&section=1 This row: |?vorpX modes=Modes would've said something like this instead: |?vorpX modes=Modes|+order=asc
  7. I think the sysadmin have also performed various backend changes that might've contributed. I've forwarded your comment to the relevant Discord channel though. Re. vorpX, I finally figured out how to sorta achieve a manual sort. It's cumbersome, but works, however due to the way MediaWiki caches property assignments, adding new values (e.g. SBS later down the line) will just add it to the end of the modes on the list of games until the values are entirely removed from the article and then re-added back again... so that would require _another_ manual sort to be added as well, solely for the list... 😐 I'll bench that idea for now, but may revisit the idea sometime in the future.
  8. I'm... not sure this is doable in its current implementation. MediaWiki (the base wiki system) and Semantic MediaWiki (what's being used to build the list of games table) is insanely limited in their functionality, where even the most basic of stuff is difficult or even impossible to do. There's probably a way I can separate the different modes so when they're displayed on the list of supported games each mode has its own column and a green tick or red cross, but this wouldn't have any affect on the game articles themselves, where the order would be up to every random editor that came along and changed it, so it wouldn't be reliable. I'd in general recommend rethinking the use of that column/parameter, and decouple the prioritization from it, by rephrasing the relevant bullet on the glossary page to something else and only treat the column as "confirmed modes". The only other thing I can do is add a sort override to the list of vorpX games table that always either sorts the values by ascending or descending alphabetical order. But that's basically it. It would cause the column to either be ordered "Z3D, SBS, G3D, DirectVR, 2D", or "2D, DirectVR, G3D, SBS, Z3D". There doesn't seem to be a way to utilize a custom order for this, though, hence we're limited to an alphabetical order.
  9. Looks great so far! I've made a few tiny changes to improve readability. The glossary page can be used to add all sorts of information you feel is relevant, so feel free to add whatever you think is missing. When the next header ("==Two equal characters creates a main header==", "===Three creates a subheader===") is added to the page it will automatically get a table of content added to the top of the page as well.
  10. Yeah, sorry, updating the table is either performed automatically by the backend, which may take a while, or can be forced by clicking More -> Refresh, which will purge the cached version of the page and process it all anew. Thanks for mentioning the visual editor, as I had forgotten we have a VR table in that one. I'll add the code to it, and then see how I can improve the list of games to better fit in to other lists on PCGW
  11. Yeah, the "vorpx notes" field supports basically everything the wiki does. It can be used to e.g. have a link to a section below the VR table with more instructoins as well, as I updated the "hackable" example with: https://pcgamingwiki.com/wiki/User:Aemony/Sandbox/VorpX#Hackable_.28aka_Unofficial.2FUser-created.29 I've published the changes so they're live right now on the wiki. I've also set up an initial variant of a glossary page, along with an auto-populating list that will update and reflect the level of support as well as modes (so no notes/links to download there, sadly): https://pcgamingwiki.com/wiki/Glossary:VorpX As soon as a game or two have been filled out with the new parameters, I'll be able to adjust and customize the table on the glossary page so it looks pretty (right now it'll end up looking barebone with no styling, since I have no examples to work with).
  12. Aemony

    is this normal? (updating embedded image)

    Should be fixed now. What typically happens is that the cached versions of the previous image isn’t cleared in the backend, or possibly your own browser. So the solution is to clear the cache (aka refresh the content) in the following order: 1. On the image page (File:Starbound - options.png) click More > Refresh. This should clear the cache of the image in the backend. 2. On the article page, click More> Refresh. This should clear the cache of the article. 3. If the issue persists, hit F5 or Ctrl+ F5 in your browser to clear its local cache.
  13. Sorry for the delay. Life got in the way πŸ™‚ I've taken some further look at this and believe I am finished with another draft of the implementation in my sandbox: https://pcgamingwiki.com/wiki/User:Aemony/Sandbox/VorpX PCGW sees "hackable" as the state to use for everything that isn't supported "natively" or "officially", so to follow the rest of the VR template and site, "hackable" in this case would mean that a profile is unofficial or user-created. That would leave us with these parameters: |vorpx = true/hackable/limited/false/unknown |vorpx modes = G3D, Z3D, 2D, DirectVR |vorpx notes = Here be a note! Or a [https://www.vorpx.com/ downlaod link], etc... The "modes" are simply shown on its own line as part of the notes field when displayed on articles for convenience's sake.
  14. @Brownd There's no need to password protect the archives if the installers doesn't trigger many AVs on VirusTotal, which these installers don't seem to do. If you want to, you're free to upload them without archiving them or password protect the archive. https://www.virustotal.com/gui/file/8f42e6b0f9058360ce497363cbcbc022fd9d4385a84606db9b0d65a2abcdb5f7/detection https://www.virustotal.com/gui/file/30f5273d7e6c6d50e61169c369e1d8e2a84d8e5afa1bf8f9a7e9bd40d43c948f/detection
  15. Aemony

    Time limit between edits

    Click on "X changes" on your watchlist to see a combined diff from all the latest changes made. In this case the user basically didn't use the Preview option properly, and was new to the wiki, and experimented to see what worked until finally giving up. There actually are edit limits configured already, and the time difference between each tiny edit (approx. one minute for each) shows that they most likely hit those as well.
  16. I would imagine most games with matchmaking have something of this nature. For example, League of Legends have for years matched disruptive or negative players together, so that their negative attitudes does not affects as many other players as it would otherwise do. This kind of individualized matchmaking is just another way of preserving the integrity of the game as much as possible.
  17. It's available to all users since we don't have a specific "News" category any more. The general PC gaming category doubles as the news category. The only thing limited to accounts with higher rights is the ability to "feature" a thread, which means it'll also show up in sidebars etc. This typically isn't an issue as Andy usually goes through and features posted threads if they look fine, and even if he didn't they'll still get featured on the front page of PCGW as part of the "Forum" section.
  18. In an attempt to minimize the chance of this happening, PCGW now recommends users who create archives containing such files to password-protect the archives using a standardized password. This should prevent browser-based automated filters from triggering on the archives as they will be unable to scan their contents. Post-download it is expected that regular AVs will scan and flag relevant files accordingly during or after the extraction of the archive. As part of this change, a relevant disclaimer about PCGW not guaranteeing the safety of any files hosted on the site have been added below the download button as well, to better reflect the proper community-contributed nature of files hosted here.
  19. The news section is mostly community-driven, with no direct guidelines on content other than what is required to get featured. While "should be more focused on what this Wiki is like fixing games, compatibility issues and that kind of stuff" is a nice idea to have, it doesn't mean much if the community contributors aren't aware of the subject matters you speak of. I am fine with the current way the news section is handled as it ensures PCGW's news contributors cover current ongoing events within the PC gaming space, which always gets a nice exposure on social media which further expands the reach of PCGW. While we shouldn't dismiss posts about fixes or compatibility issues, I don't think making it the sole subjects of news submissions on PCGW is healthy, as it wouldn't ensure a steady flow of news contributions and most of it wouldn't be very engaging to readers. I do think though that we could add a provision in the "required to get featured" guidelines to allow for some sort of preferential treatment to submissions about fixes or compatibility issues. This might result in more submissions of the sorts you speak of, and allow those submissions to be more easily featured on the front page of the wiki and whatnot.
  20. https://pcgamingwiki.com/wiki/List_of_anti-aliasing_compatibility_flags_for_Nvidia If you could confirm the direct link ( https://docs.google.com/spreadsheet/pub?key=0AnHpuYHx21sjdENRSHg1ZkhndWF5R05tQjhCbTFNUVE ) points to the same document, that'd be great πŸ™‚
  21. This should be possible nowadays. I am not at a computer atm but I can throw up a page for this in an hour or so.
  22. That Steam policy weren't exactly hidden, but is a consequence of Valve's years old policies regarding those keys: https://partner.steamgames.com/doc/features/keys Valve doesn't see a cut from the sale of Steam keys at all, so allowing publishers and developers to give Kickstarter backers Steam keys for free while also having a one-year timed exclusive release on another platform means Valve is paying infrastructural costs etc for free for a year without getting paid for it. Color me surprised they didn't agree on doing that. It is part of why Valve actually gets less than 30% of Steam game sales, after all.
  23. Calling it plagiarizing is a bit too much. A tardigrade did feature in like 2-3 episodes of Destiny's first season but the story eventually replaced the creature with a human, and since then none have been featured again. While making for an interesting side story, it basically wasn't important enough in the long run for the way Destiny's instantaneous space-travel works. The tardigrade they found and made use of in a few episodes aided them in navigating the mycelial network, but wasn't critical to its continued use. I think this article goes through it best: Understanding the Star Trek: Discovery Plagiarism Allegations Similarities do seem to exist, and it's possible some inspiration was taken from that game, but then it could also equally be that the series and the game are each a result of their time more than anything else. Calling it plagiarizing, though, seems a bit too much.
  24. Aemony

    Proposal: Add Communities Sub Section

    To make a long story short, there's a ton of ongoing undercurrents that your proposal touches upon πŸ™‚ To give you a tiny glimpse into it, I'll just quote myself from another ongoing thread regarding the removal of unofficial wikis in the general information section: I think the idea of a separate communities section or community-based resources is overall good, and am glad that we have an official proposal thread for it to keep track of it. We just need to figure out how to fit it into what PCGW wants to be and balance it with the various factors involved. For the moment the "other information" section sounds the most appropriate due to its general "everything goes" nature. It is, of course, also possible we can find a solution to feature it higher up the page in an appropriate manner, e.g. collapsed by default to prevent even massive lists of community resources and sites from overtaking the rest of the page.
  25. Aemony

    Proposal: Add Communities Sub Section

    Adding a section just below the General Information section doesn't really solve any of the current issues, and will only result in even more wasted space at the top. In another thread and in previous discussions the removal of e.g. stuff like community-driven wikis have also been mentioned as possible changes. I can see a benefit in having a general "everything goes" community section at the bottom of articles in Other Information, as that have generally been considered the place for non-technical stuff like mods or info not applicable to any of the other sections, etc. It would also serve as a general acceptable place to list however or whatever community members would feel beneficial, and the lack of prominently being featured on the articles would also prevent edit wars. So in short: General information - Official game resources Other information -> Communities (or however it would be called) - "everything goes" community section filled with links and whatnot to unofficial resources and stuff. To bridge the two, we could add a link in the general information taking visitors down to the bottom (e.g. "See community-oriented links" or something similar).
×