User talk:StockholmSyndrome

I noted you found what seems to be a universal variable for the Buddah engine which disables intro videos. The question I'd like to pose to you, though, is this: why keep around the inferior solution? (If it's "I'm a new user and I don't want to get in trouble", fair enough.) Regardless of the reason, though, I can tell you your method, so long as it actually works on all Buddah-based games, won't get you as it's superior should replace all previous solutions. So don't be afraid to replace the previous "disable video" solutions.

It's still nice to know which files you'd have to delete if you wanted to do it manually.
Doing it the launch parameter way is just faster and survives a file integrity check (which would destroy your efforts if you manually deleted or renamed those files).

True, but it's not the same as with, say, the fix for AMD graphics cards and Darkstone, whereby there are people who own AMD graphics card, can play the game, yet don't have DirectX 10.1 compatibility for whatever reason. With your fix, anyone can use it, regardless of their hardware, drivers, OS, etc., and it works more reliably than the manual version (survives an integrity check as you said).

People should just learn how to use the command line parameters (when they can be used). Whenever I put up a command line argument I always use this as a template.

See [[Glossary:Command line arguments|Command line arguments]].
Use <code>command</code>

However I have no idea if this confusing in any way. http://pcgamingwiki.com/wiki/Glossary:Command_line_arguments I have no idea as to how many people actually open the images, or take their time to read the page. This stuff could probably be a bit clearer.

Yes, but is there any kind of remotely considerable advantage in doing so?

Also, it's gonna be a shitload of work to comb through all Unreal engine games and add this skip intro method.
I'm gonna do it on a case by case basis when I'm actually playing that game and look up the PCGW page.

Huh? Your commit specifically states it works on all Buddha-based games, not all Unreal Engine-based games. If you did mean the Buddha engine, it won't be much work at all since PCGamingWiki currently only lists 8 games using the engine.

Simple.
I started by adding the launch parameters for Unreal games, later I asked an Iron Brigade developer if there are launch parameters for Buddha engine games as well.

The parameter for the Buddha engine only works on Brütal Legend and Iron Brigade.

Huh. That implies Buddha is a fork of Unreal Engine....

It just occurred to me that since this is a universal improvement, you don't initially need to put the complete fix on every page - just put it on the applicable engine pages instead (see the Source Engine article for examples). Not only does it dramatically simplify adding this improvement, there's the potential it can be automated; thus, it can potentially added to the site's resident fixbot, Garrbot.

Also, do note PCGamingWiki has separate pages for all the official iterations in the Unreal Engine family of game engines, so Unreal Engines 1, 2, 2.5, 3, and 4; be sure to put the improvement only on the iteration(s) which this command works (obviously including Buddha).

No it isn't. Buddha and Unreal are 2 separate engines.

Who in their sane mind goes to the Unreal engine page if all you want is to know how to skip those intro videos in Game X?

Good point.

Imo, fixes in engine pages are only useful for say, any random undocumented new game that somebody may create today or tomorrow.

For example, all those mods running on UE3 or perhaps source SDK.
Now, I don't know if Buddha is that open, but I guess that if something can be said almost surely to apply to the whole engine it may find a mention even in its page.

The same people who wrote up the Issues fixed section for the Source Engine games, such as Portal, and linked them there instead of duplicating the information across all the articles.

I had a look at this awful mess (Portal).
It features non-tips like "verify file integrity"... something so generic, unspecific and unhelpful that it applies to every single game on Steam. Ever.

Sure, an article can be blown up to XXXL super-size if you shovel trueisms like those in there.

These Source based game pages are incredibly outdated. No new real fixes have been added for them in a while anyway, most of these issues don't pop up too often anyway.

Excellent point. To that end, I think you should keep an eye on this thread so you can correct anyone who inevitably claims you don't know what you're talking about.