Jump to content

Aemony

Administrator
  • Content Count

    227
  • Joined

  • Last visited

  • Days Won

    34

Everything posted by Aemony

  1. @BuckoA51 can you upload a new version of the archive that contains the necessary DLL file as well?
  2. If you want to you can upload an archive without the password protection. Password protected archives are mostly for executable related codes that triggers false positives, which files like this .ttarch typically don't.
  3. Basically any specs for any computer released within the last decade would most likely do for those titles. The most "demanding" title of those are Half-Life 2, and even that one is playable on most systems nowadays.
  4. Version 1.0.0

    376 downloads

    Description: The mod replaces the intro video with an empty video file. Installation: Simply extract the archive to the game folder. Additional information: This is an archive that combines two other mods in one archive: Loose Files Loader by reg2k / registrator2000 Link: https://www.nexusmods.com/control/mods/11 Files: .\iphlpapi.dll No Intro Screen by reg2k / registrator2000 Link: https://www.nexusmods.com/control/mods/12 Files: .\data_pc\textures\videos\intro\startvideos.tex
  5. I've renamed your user on the wiki. You should notice the change the moment you visit the wiki again.
  6. The wiki doesn't follow the SSO account due to various reasons. We are able to change it for you, however. What is your old username on the wiki?
  7. Please remove the executable file without Steam Stub. It is against PCGW policy right now to provide such a copy, as well as instructions on how to bypass it. See the information from the below section of the wiki policy: https://www.pcgamingwiki.com/wiki/PCGamingWiki:Editing_guide/Wiki_policy#Bypassing_copyright_protection_and_fixes
  8. Okay, then everything's fine. I've approved the file. ๐Ÿ‘
  9. Hi! Am I correct in assuming this acts as a crack and effectively disables Steam API related features as well as the ownership check of the Steam copy? PCGW attempts to distance itself from cracks, so the use of steam_api64.dll as the DLL injection point makes it currently questionable whether we should approve the upload or not. If possible, then I highly recommend using some other DLL as the injection point such as D3D12.dll or DXGI.dll.
  10. Thanks for mentioning this -- I've moved the warnings section to be shown below the seriesbox. The change will be visible on pages after they've been purged. The warnings section is a fully automated section that dynamically changes its contents based on the rest of the page. Any additions should preferably match that, and be designed around automatic population so that they're added to all other articles as well were such a warning is applicable. What editors can do, however, is exploit the fact that the warnings are added to the very bottom of the infobox by, well, merely adding new bullets that they want to appear as part of the warnings list below the infobox. This, however, isn't technically supported nor established, so no guarantees are given -- such an approach might very well break in the future.
  11. This CheatEngine FOV table is dated 2017-02-08 and so predates the fourth patch for the game that was released in 2018 and updated the game engine to Unreal Engine 4.18. As such it is incompatible with an updated copy of the game.
  12. Though you need to note that this would only apply for persistent availability, where the game is available any time and not merely limited to short periods of time interspaced with unavailability. And you need to figure out how we would cover a game like Crucible, that was initially available to everyone but then turned around and went closed beta where only "existing" players could still play it and new players were granted access in waves like a regular closed beta ๐Ÿ™‚ https://store.steampowered.com/app/1057240/Crucible_Beta/
  13. Mhm, I'd prefer it if I found another solution than that one. The thing I like with Special:PrefixIndex is that it allows for non-standard subpages, such as https://www.pcgamingwiki.com/wiki/SimCity_(2013)/Bugs, which would allow the community to create custom pages if they so desired. Yes, that's the direction that my own thoughts are going in right now -- to basically have a table akin to the input table that automatically hides or shows different subsections of the table according to the filled out rows.
  14. Of course MediaWiki loves to throw a god damn curveball at you when you least expect it... Why do I even still expect it to function within expected parameters?! (โ•ฏโ€ตโ–กโ€ฒ)โ•ฏ๏ธตโ”ปโ”โ”ป So the Special:PrefixIndex call itself isn't an issue -- determining whether to show the sidebar or not is. In a logical, perfect, world, a simple IF statement to check whether the Special:PrefixIndex call outputs anything would suffice, but in a MediaWiki world that isn't possible. Because even on pages where there's no actual subpages to list, that command still evaluates as 'true' on such statements and so the sidebar still appears even though it's intended to be hidden. I've tried various ways of working around the issue but no dice, so far. Dunno if I will be able to figure this one out, as I have basically nothing to go on.
  15. On the subject, the RGB lighting middleware page has a lot of examples of third-party stuff that we could add to the table. I'm going to contemplate the subject a few days more or something, and will probably then throw up a draft we can test. That should actually be relatively easy to achieve using {{Special:PrefixIndex/{{FULLPAGENAME}}/|hideredirects=yes|stripprefix=yes}} That call creates an alphabetically ordered list of all subpages below the specified prefix (the page name in this case) and lists it in an ordered list. See https://www.pcgamingwiki.com/wiki/User:Aemony#Pages for an example. It would be rather easy to create an automatic inclusion of a seriesbox/categorybox containing such a list where appropriate and add it to the bottom of the infobox game template. Although I'd recommend not keeping it collapsed by default until we've seen how many subpages got used.
  16. We'd probably preferably want a solution that combines dedicated subpages (in those cases they're necessary) with an actual "Third-party support" table, below the "Other information" section. Imagine that we made use of a new table on the game pages where we tracked support among all kinds of third-party tools, such as ReShade, Special K, dgVoodoo 2, DXVK, Logitech's G Hub-whatsitcalled, etc, etc, etc that we can semi-easily extend by adding new parameters if a part of the community wants to track something new. If the relevant information for e.g. ReShade or Special K was only "basic", then it would be situated in that table on the game page itself, and nowhere else. However if a subpage existed and was required for further instructions or details, a link would be added to that subpage, along with whatever else was entered in the relevant parameters. For example, based on our ReShade page right now, for that particular third-party tool we would have to have three different parameters in that table: reshade status reshade render api reshade notes For Special K, we would be looking at some more, such as: special k status special k render api special k version special k injection special k notes For more 'basic' tools like dgVoodoo 2 or DXVK or OEM's lighting software suites, we would be looking at a typical 2 parameter combo: dxvk dxvk notes dgvoodoo dgvoodoo notes So just based on those, the table would look something like this: {{Third-party tools |dgvoodoo = |dgvoodoo notes = |dxvk = |dxvk notes = |logitech hub = |logitech hub notes = |reshade = |reshade api = |reshade notes = |special k = |special k api = |special k version = |special k injection = |special k notes = |steelseries engine = |steelseries engine notes = }}
  17. The discussion on the PCGW Discord was quite heated when the proposal was raised, I'll admit ๐Ÿ™‚ Though it mostly concerned whether there was a need of tracking third-party tools in general through a separate table, as opposed to just continuing to keep track of them through a separate page. While the proposal haven't been closed yet, I've gone ahead and set up a separate page that can be used to keep track of Special K support, based on the ReShade compatibility table: https://www.pcgamingwiki.com/wiki/List_of_games_compatible_with_Special_K Feel free to add or edit entries as desired.
  18. Sorry about the delay in approving the file, but it has now been approved.
  19. It's a known limitation of the current SSO functionality of the wiki system. Our sysadmin is aware of the issue, however to fix it I believe he needs to rework it or something like that, something he have yet have had time to do. But yeah, we're all basically affected and it will be solved eventually ๐Ÿ™‚
  20. Well, that turned out to be easy. I've changed it so it acts as a link on the profile page as well, and that it uses the Steam icon as well. I want to add functionality for those without a custom URL set on Steam, but it seems there's no simple way of adding that functionality beyond adding an entirely separate field -- so for now I guess we'll just use the custom URL instead. The edit profile page though has been updated to easily provide a way to be taken to the page where one can view or change the custom tag. Thanks for bringing it to our attention that the Steam profile wasn't properly linkified on the profile pages ๐Ÿ™‚
  21. Hmm, weird -- that's the same field alright. I dunno why it doesn't get linkified on the profile page itself. I'll have to take a look at it. I'm also reworking it a bit and adding more information about it so it's easier to fill out.
  22. This: Results in this: So I'm not sure what functionality is missing? Edit: On that note, our current implementation can't handle regular Steam IDs, so that's a downside. A user such as e.g. https://steamcommunity.com/profiles/76561197980016871 can't input 76561197980016871 in that field as it will fail, since https://steamcommunity.com/id/76561197980016871 is not valid.
  23. In general, rather minimal amount of information. The few times we mention physical stuff it's typically under the Version differences section and only in passing to cover all differences between that edition and others. See for example Borderlands 3 (all digital editions), Ion Fury (one retail edition), or Doom Eternal (mixes digital editions with one physical collector's edition with extra goodies).
  24. Changed the article: https://www.pcgamingwiki.com/w/index.php?title=Counter-Strike%3A_Source&type=revision&diff=980594&oldid=966541
  25. Differences between editions themselves are usually listed under the "Version differences" header below the Availability category, see e.g. https://www.pcgamingwiki.com/wiki/Doom_Eternal#Version_differences. The reason why availability rows list editions are to highlight the different ones available for purchase on each storefront. Beyond that, game code-wise PCGW does not really keep track of versions of the game per se (v1.0, v1.1, v1.2 etc) as the article is meant to (unless stated otherwise) target the latest available version of each game.
×
×
  • Create New...