User talk:Chieftainalex

From PvXwiki
Jump to: navigation, search

Rate tab

Is there a way to restrict the rate tab's appearance to pages with {{Real-Vetting}}? It currently shows up on pages such as Build:Team - 7 Hero Beginner Team/Assassin. --Krschkr (talk) 03:00, 15 December 2019 (UTC)

I assume that its adequate to assume anything in the "Build" or "Build talk" namespace that is not a subpage (i.e. does not contain a forward slash) is therefore a real-vetting build.
I'd propose the following, which also shows the rate tab when you're on the build_talk pages.
RLQ.push(function () {
    /* Trigger on Build (ns 100) or Build_talk (ns 101), but only if not a subpage (/) */
    if ( ( mw.config.get('wgNamespaceNumber') == 100 || mw.config.get('wgNamespaceNumber') == 101 )
         && mw.config.get('wgRelevantPageName').replace('Build_talk:','Build:').substring( 'Build:Any/'.length ).split('/').length == 1
       ) {
        addRateButton();
    }
});

function addRateButton() {
    var caHistory = document.getElementById('ca-history');
    if (caHistory != undefined) {
        ratelink = document.createElement('li');
        ratelink.id = 'special-rate';
        ratelink.innerHTML = '<span><a href="/index.php?title=' + mw.config.get('wgRelevantPageName').replace('Build_talk:','Build:') + '&action=rate" title="Rate the build">Rate</a></span>'
        caHistory.parentNode.insertBefore(ratelink, caHistory);
    }
}
If that is not the case and I've missed something and you really need to only show the rate tab when you're using the {{Real-Vetting}} template...
then I would add a hidden category via {{Real-Vetting}} (e.g. "Category:Real-Vetting builds", and tag that category with __HIDDENCAT__) such that all pages using that template end up in the hidden category. The category is then accessible from mw.config.get('wgCategories'). This would enable the Rate tab on pages in that category but would prevent a rate tab from talk pages.
RLQ.push(function () {
    /* Trigger on Build (ns 100) or Build_talk (ns 101), but only if not a subpage (/) */
    if ( mw.config.get('wgNamespaceNumber') == 100
         && mw.config.get('wgCategories').indexOf('Real-Vetting builds') != -1
       ) {
        addRateButton();
    }
});

function addRateButton() {
    var caHistory = document.getElementById('ca-history');
    if (caHistory != undefined) {
        ratelink = document.createElement('li');
        ratelink.id = 'special-rate';
        ratelink.innerHTML = '<span><a href="/index.php?title=' + mw.config.get('wgRelevantPageName') + '&action=rate" title="Rate the build">Rate</a></span>'
        caHistory.parentNode.insertBefore(ratelink, caHistory);
    }
}
Hope this helps. -Chieftain Alex (talk) 11:12, 15 December 2019 (UTC)
Mhm, the solution with a hidden category sounds promising as adding the rate tab to talk pages would be a worse side effect than the fixed subpages rate tab barely anyone will notice anyway.--Krschkr (talk) 12:21, 15 December 2019 (UTC)
Adding it to the talk page would link to the build's rate page, not give ratings to the talk pages. We actually used to have it set up that way for quick navigation. Also, I'm pretty sure our local Large Removal filter can be disabled since there's a global Large Removal filter for all gamepedia wikis. Ours is probably too strict for current activity levels. -Toraen (talk) 12:24, 15 December 2019 (UTC)
Oh, if the talk page rate button would work properly it'd actually be an improvement. --Krschkr (talk) 12:25, 15 December 2019 (UTC)
I think the && mw.config.get('wgRelevantPageName').split('/').length == 1 line needs to check for length <= 2 though, since otherwise some professions won't get the rate tab. -Toraen (talk) 12:33, 15 December 2019 (UTC)
(Hmm how does that actually work, where we have subpages using the same character as the delimiter as the build profession delimiter?) revised the above a bit.
Also fwiw I've pasted the gww/gw2w's "large section removal" abusefilter onto User:Chieftainalex/sandbox. -Chieftain Alex (talk) 12:41, 15 December 2019 (UTC)
It's more that we're using the mediawiki default delimiter for subpages as our profession separator because that's how it looks in game and no one anticipated the need for build subpages. Thankfully mediawiki's smart enough to not actually classify every build as a subpage of something that doesn't exist. -Toraen (talk) 12:55, 15 December 2019 (UTC)

Be cursed with me!

Kwaaah! -Toraen (talk) 12:04, 16 January 2020 (UTC)

Squawk? -Chieftain Alex (talk) 18:50, 16 January 2020 (UTC)
Some serious head-scratching going on when trying to get to the bottom of the pvxcode extension. -Chieftain Alex (talk) 20:26, 25 January 2020 (UTC)
There's reasons I've refused to learn it in any deep capacity. -Toraen (talk) 11:17, 26 January 2020 (UTC)
I'm going nuts with the deletion spree atm. Might need to figure out how I can test the output though, as I am making rather a lot of changes. -Chieftain Alex (talk) 11:39, 26 January 2020 (UTC)
(EC) Your gitlab activity feed fills me with joy. Also I have a code branch of my own that has the mysticism function added (though you may want to proofread it, it's been a while since I've looked at it). -Toraen (talk) 11:52, 26 January 2020 (UTC)
As for the large number of changes, you might want to create individual branches for each group of related changes, and merge request them to the master one at a time. I don't think they'll approve a fully gutted PvXCode in one fell swoop. At one point I did set up a test wiki on my computer and get the rating extension running on it, so you might be able to do that for testing. -Toraen (talk) 11:52, 26 January 2020 (UTC)
Well I'm down to *just* (lol) the monolith file to modify. I've had a decent review of what the functions roughly do, and I think I've not left anything in there that isn't used so far.
I will need to create a wiki-on-a-stick to test it or some equivalent as I think I'm past the point of a readable branch (a long time ago I once used XAmp... it was crap).
I am wondering about whether or not to keep some of the lesser-known functions that I've documented in my sandbox. There's oodles more from what I can tell. -Chieftain Alex (talk) 20:30, 26 January 2020 (UTC)
Parse error: syntax error, unexpected '=', expecting ';' or ',' in D:\Programs\XAMPP\htdocs\wiki\extensions\PvXCode\gwbbcode\gwbbcode.inc.php on line 34
Well X-AMPP is 7 fully fledged versions later on than when I last used it and is thankfully less crap. Install of mediawiki worked. Debugging has started... -Chieftain Alex (talk) 21:25, 26 January 2020 (UTC)
No fatal PHP errors, only javascript now. :) -Chieftain Alex (talk) 21:37, 26 January 2020 (UTC)
https://gitlab.com/Chieftain_Alex/pvxcode/blob/master/gwbbcode/gwbbcode.inc.php#L1086
It doesn't seem to like this line - i guess I copied over the proposed change from the curse noticeboard incorrectly.
CURSE ACTUAL VERSION
				foreach ($regs as $fork) {
					list($all, $val_0, $val_15) = $fork;
					$desc = str_replace($all, fork_val($val_0, $val_15, $attr_lvl), $desc);
				}
PHEN PROPOSED VERSION (with variable names corrected)
				foreach ($regs as $fork) {
					list($all, $val_0, $val_15) = $fork;
					$pos = strpos($desc, $all);
					$desc = substr_replace($desc, fork_val($val_0, $val_15, $attr_lvl), $pos, strlen($all));
				}
--Chieftain Alex (talk) 21:59, 26 January 2020 (UTC)
When I typed in Phen's version correctly it doesn't throw errors. Currently I can display a build without any php errors. Yay? Real testing and curse noticeboard issues begins tomorrow or later in the week. -Chieftain Alex (talk) 00:09, 29 January 2020 (UTC)

Build Creator

The wayback machine got an exemplary team. [Link]. Not that it'd be much of a help to us now, but I consider the general layout of the build creator well-done. Thought it'd be better to hand this example in late rather than never. --Krschkr (talk) 20:19, 22 January 2020 (UTC)

It's a bit mangled but I think that I get the idea.
In a kind-of-related vein, I wrote a really basic equipment template decoder this evening. If we wished to replace the extension that provides the pvxbig tag with a hybrid template (static images, names, links)/javascript (popups, gwbbcode stolen from smiley, build encoding) solution, then I'm sure it could be done. -Chieftain Alex (talk) 00:28, 23 January 2020 (UTC)
Had another think about the above and there aren't that many bugs to fix listed on Curse noticeboard, and none look too bad tbh. I've left probably-working-but-not-tested fixes for most of them.
A massive disadvantage (imo) to replacing the existing extension with Smiley php stuff would be having to rewrite the build packs scripts that Toraen has on his github. -Chieftain Alex (talk) 14:18, 25 January 2020 (UTC)
It wouldn't take that long to rewrite the relevant sections. As long as the new method (whatever form it takes) displays the template code in a consistent format, it's trivial to write a regex to grab it. -Toraen (talk) 11:01, 26 January 2020 (UTC)

PvXCode 2.0

Making some progress on this. Today I eliminated all of the log errors and cornercases on the three Special pages. Also progressed the tooltip js debugging -Chieftain Alex (talk) 22:22, 27 January 2020 (UTC)

Lolpvxcode.png
I knew there was some cruft in that code, but that was slightly more than I expected. -Toraen (talk) 05:27, 28 January 2020 (UTC)
Spent most of my time hacking the mediawiki version I'm testing on today - XAMPP isn't providing a bunch of memory usage information which was giving me a full screen worth of php errors. Hopefully I can actually address the Curse noticeboard issues now that I've mostly ironed out the cleanup bugs. -Chieftain Alex (talk) 23:03, 28 January 2020 (UTC)


(Reset indent) Ok after optimising some segments, I'm down to the last two Curse noticeboard bugs to iron out, plus a few more I've found/introduced.
  1. PvP Skills and Template Codes - can't use the (PvP) version for ingame templates → pretty sure I can fix this.
  2. Yes Leadership on tooltips - it has been so long that I've played a paragon, I will actually need to go ingame and research how shouts behave vs energy gain (particularly: self-target P/W shouts, P/R shouts for their pets - this is probably what is within static $leadership_skills but I want to verify it).
  3. Yes Rounding on PvE only skills such as Summon Spirits - turns out its not linear! Shouldn't be too difficult now that I know why the values were wrong.
After that I will probably do a pass for obviously inefficient sections (saved 32 seconds on [rand players=10] by using a native php array_filter function instead of a loop earlier) -Chieftain Alex (talk) 22:04, 30 January 2020 (UTC)
Updated to do list. Progressing solving the pvp/pve id template issue. -Chieftain Alex (talk) 22:46, 31 January 2020 (UTC)
Ok everything is done I think. I will do a final pass tomorrow to look for anything else, but I've addressed all the known bugs and a few more besides. I guess I need to assemble a changelog for the bug fixes, then figure out how to convince curse to load it... Also i suspect there is a "desc" parameter that originally had a function... -Chieftain Alex (talk) 23:29, 31 January 2020 (UTC)
I will also take a look at PvXRate since there are a few overlib items hidden on the ratings page. -Chieftain Alex (talk) 14:43, 1 February 2020 (UTC)
You're doing incredible work, thank you so much! Do you have a link to a good guide for setting up a wiki-on-a-stick? I'd like to see the changes in action myself (and maybe contribute a little on PvXRate). I'll at least throw in my support for your changes when you do a merge request. -Toraen (talk) 11:00, 2 February 2020 (UTC)

(Reset indent) Basically follow mw:Manual:Installing MediaWiki on XAMPP. I didn't bother giving it any admin rights even though XAMPP does suggest its a good idea.

  • I used MW 1.33
  • I had to modify quite a few of the mediawiki base files because XAMPP doesn't pass the memory reading server stats correctly to the page (you end up with php errors even without extensions).
File / line number Suggested hack
in \includes\profiler\ProfilerExcimer.php , I've made the function on line 52 return blank.
	public function getFunctionStats() {
		return ''; // FIXME - XAMPP
	}
in \includes\profiler\ProfilerSectionOnly.php at line 49 and 54, I've made both functions return blank.
	public function getFunctionStats() {
		return ''; // FIXME - XAMPP
		// return $this->sprofiler->getFunctionStats();
	}

	public function getOutput() {
		return ''; // FIXME - XAMPP
		// return $this->getFunctionReport();
	}
in \includes\profiler\Profiler.php at line 215, I've stopped it logging outputs:
	/**
	 * Log the data to the backing store for all ProfilerOutput instances that have one
	 *
	 * @since 1.25
	 */
	public function logData() {
		$request = $this->getContext()->getRequest();

		$timeElapsed = $request->getElapsedTime();
		$timeElapsedThreshold = $this->params['threshold'];
		if ( $timeElapsed <= $timeElapsedThreshold ) {
			return;
		}

		$outputs = [];
		foreach ( $this->getOutputs() as $output ) {
			if ( !$output->logsToOutput() ) {
				$outputs[] = $output;
			}
		}

		// if ( $outputs ) { // FIXME - XAMPP
		// 	$stats = $this->getFunctionStats();
		// 	foreach ( $outputs as $output ) {
		// 		$output->log( $stats );
		// 	}
		// }
	}

	/**
	 * Log the data to the script/request output for all ProfilerOutput instances that do so
	 *
	 * @throws MWException
	 * @since 1.26
	 */
	public function logDataPageOutputOnly() {
		$outputs = [];
		foreach ( $this->getOutputs() as $output ) {
			if ( $output->logsToOutput() ) {
				$outputs[] = $output;
			}
		}

		// if ( $outputs ) { // FIXME - XAMPP
		// 	$stats = $this->getFunctionStats();
		// 	foreach ( $outputs as $output ) {
		// 		$output->log( $stats );
		// 	}
		// }
	}
in \includes\profiler\SectionProfiler.php at line 97, I've made the function return false
	public function getFunctionStats() {
		return false; //FIXME - XAMPP
	}
in \includes\profiler\ProfilerXhprof.php at line 131, I've made the function return false
	public function getFunctionStats() {
		return ''; // FIXME - XAMPP - GOOD LUCK PROFILING MATE.
	}

also at line ~202

	protected function getFunctionReport() {
		return ''; //FIXME - XAMPP - NOPE
	}
Folder structure
  • Download the pvx extensions off gitlab. Pop them in the /extensions folder. Name them with the correct folder names to match the localSettings lines below.
  • In localsettings.php you need to make the following changes after you've installed MW.
# Roughly line 52 - change this from true to false, since you won't have an email server to authenticate yourself..
$wgEmailAuthentication = false;

# Add to the end
wfLoadExtension( 'PvXCode' );
wfLoadExtension( 'PvXRate' );

# Debugging assistance
$wgShowExceptionDetails = true;

Should work after that. -Chieftain Alex (talk) 12:12, 2 February 2020 (UTC)

Also if you want images to work, a wiki on XAMPP doesn't seem to get the image urls correctly - just do find+replace for /extensions/ and replace with http://localhost/wiki/extensions/. -Chieftain Alex (talk) 12:19, 2 February 2020 (UTC)
Also for ratings, you'll need to open http://localhost/phpmyadmin/ , open the wikidb folder you created in the left-hand folder structure, go to Import on the right, and paste in the SQL code from "\XAMPP\htdocs\wiki\extensions\PvXRate\install\sql\table_rating.sql" Otherwise ratings throw a set of red warnings about no "rating" table. -Chieftain Alex (talk) 12:22, 2 February 2020 (UTC)
idk enough about buildmasters to know if that should still be in the extension or not, there doesn't even seem to be a way of setting that user-right, but there's quite a bit of exception code in there. -Chieftain Alex (talk) 12:42, 2 February 2020 (UTC)
I've installed everything, and oddly I didn't have to mess with any of the base mediawiki files like you did to get everything working. However, the rate extension is throwing an error any time I try to access a rating page: File:ToraenRateError.PNG. I also can't get images to load even after doing the url replaces on all the extension files. Is there somewhere else I need to do that? -Toraen (talk) 06:52, 3 February 2020 (UTC)
Excellent.
  • For images, can you screenshot the folder path where an example image is located / and maybe a screenshot of the browser console when inspecting the missing images
  • Is this the first time you've tried to access the rate page? Did you add the rating database first using phpmyadmin?
  • Did you also go for MW 1.33 to match pvx? (or did you choose 1.34) - might affect database access, who knows.
-Chieftain Alex (talk) 07:47, 3 February 2020 (UTC)
Oops, reinstalled with 1.33 (realized shortly after posting) and I can now access rate pages. Images still aren't showing up though and now pvxbig isn't parsing stuff correctly, let me see that I've added the extensions correctly and I'll get some screenshots. -Toraen (talk) 08:08, 3 February 2020 (UTC)

(Reset indent) Hopefully this is what you need:

gwbbcode.tpl and pvxcode.css had their relative paths modified to http://localhost/toraenwiki/extensions/ from /extensions/

The enchantment arrows (and cost/cast/recharge icons) load on that first image when using absolute paths, but nothing else does, which is weird. None of the images work with relative paths. -Toraen (talk) 08:58, 3 February 2020 (UTC)

Uhh, disregard maybe? After I tested a template in PvXDecode all images decided to start working. The download link on a build throws a 403 Access Forbidden error though. -Toraen (talk) 09:21, 3 February 2020 (UTC)
e.g. http://localhost/wiki/index.php/Special:DownloadTemplate?build=OQGjUllMaS8Ezg1YhiKYxgtbAhA&name=P/W%20Soldier%27s%20Fury%20Spear
I think the download link won't work unless you stick "/index.php/" in the download url for the gwbbcode.tpl file. I think you wouldn't need that on pvx since you have the url rewrite rule. -Chieftain Alex (talk) 18:42, 3 February 2020 (UTC)
Let's see what happens if I tick the maintainer option instead of developer. -Chieftain Alex (talk) 00:02, 4 February 2020 (UTC)
That worked, I'll do my best to not make you regret that! (I'll still do merge requests for large changes so you can test) -Toraen (talk) 00:09, 4 February 2020 (UTC)
Anything is revertable. Do what you like, I have a mostly working local copy anyway, even if gitlab gets deleted. -Chieftain Alex (talk) 00:26, 4 February 2020 (UTC)
Did you find any more bugs btw? -Chieftain Alex (talk) 19:24, 11 February 2020 (UTC)
Haven't, though I didn't do much with it this weekend. I have been a bit of a slacker. I do find it odd though that the name parameter that can be passed with the build tag is ALWAYS stripped and replaced with the page name though. -Toraen (talk) 20:50, 11 February 2020 (UTC)
Yeah that behaviour is kinda weird, i'll look into it. Basically if we set a [build name="xyz"][/build] bit, we want to use name=xyz rather than xyz={{pagename}}? -Chieftain Alex (talk) 22:53, 11 February 2020 (UTC)
Yeah, that would make sense. It would only affect the download link on the generated build, but that's fine. -Toraen (talk) 05:47, 12 February 2020 (UTC)
(I had forgotten the name=xyz request) Names for build templates now work too. -Chieftain Alex (talk) 22:25, 20 February 2020 (UTC)
Bit late to the party, but you can eliminate code related to the old buildmaster policy. It's inactive and buildmasters won't return. --Krschkr (talk) 00:23, 13 February 2020 (UTC)
Thanks for confirming; I caught up with the PvXwiki:Build Masters page yesterday so agree that I might as well try and remove any references to those bits (explains why i couldn't even set those permissions on my test wiki). -Chieftain Alex (talk) 17:55, 13 February 2020 (UTC)
(Reset indent) Pushed a few more changes:
(1) removal of buildmasters from classes/RateAction.php, and
(2) addition of vote_rollback rights through extension.json
Currently wondering:
(A) If I should try and setup Special:UserRatings such that I can specify the user to review the ratings of, e.g. by doing Special:UserRatings/Toraen. I think this would be useful.
(B) How hard it would be to add voting rollback notifications to the targeted user when rolling back a vote (mw:Extension:Echo/Creating a new notification type#Walkthrough: Creating a new notification type.
-Chieftain Alex (talk) 20:30, 13 February 2020 (UTC)
(A) is done (just accepts the User parameter into the URL, doesn't display an "enter username in this box" thing but it works).
(B) I've changed my mind on, it looks annoying to code, and apparently Extension:Echo isn't bundled by default anyway. -Chieftain Alex (talk) 21:41, 13 February 2020 (UTC)
If possible, changing the display of rating pages when logged out to show the existing votes would be helpful. Currently I cannot get a bot script to actually read ratings pages because the botpasswords method of logging in is apparently not recognized by the rating extension. I have not tried to use a clientlogin method but it seems complicated with how there's an auth chain from twitch/fandom>gamepedia>pvx.
PvX does have an equivalent to echo installed (Reverb) otherwise the ThanksMeToo extension wouldn't work, though I understand if it seems too annoying to code (and we can't be sure that it works exactly like echo for the cases we'd need it - there's no documentation link). -Toraen (talk) 03:56, 18 February 2020 (UTC)
Changing the display of rating pages in the way you're requesting is actually trivially easy. I've got a proposed set of responses in mind, it would be worth agreeing these:
Case Ratings display Ability to submit ratings Ability to moderate ratings Additional
Wrong namespace No No No Error message
Trying to rate a build page
that does not exist (id==0)
No No No Error message
Anon Yes No No Info message
New user with insufficient rights
(no "ratebuild" permission)
Yes No No Info message
Blocked user
("ratebuild" permissions but blocked)
Yes No No Error message
User with sufficient rights
("ratebuild" permission)
Yes Yes No N/A
Admin
("ratebuild" and "sysop" permissions)
Yes Yes Yes N/A
We could choose to hide all the ratings for blocked users, but I don't think that's worth doing if we want to display the ratings for logged out users. -Chieftain Alex (talk) 19:23, 18 February 2020 (UTC)
Those behaviors look good. I agree that hiding votes from blocked users wouldn't make any sense. They could just log out to see the votes and there's no real reason to hide them anyway. -Toraen (talk) 05:33, 19 February 2020 (UTC)
Source updated. -Chieftain Alex (talk) 20:45, 20 February 2020 (UTC)
I spotted the faded profession image in the tooltip on PvXwiki:PvXcode#About - we still have those around on gw:File:Assassin-faded-large.png or gww:File:Assassin-faded-large.png so I'll probably add those to the extension tomorrow, albeit increase the opacity so that the text is readable. (Also fixed some other image resource url issues) -Chieftain Alex (talk) 00:05, 4 March 2020 (UTC)
I've added the complete merge requests for (1) pvxcode and (2) pvxrate to gitlab. Depending on whether Curse has the ability to host a stage version of the extension or not, the sheer number of changes might frighten them. In any case I have confidence they'll be able to confirm that we know what we're doing... -Chieftain Alex (talk) 21:29, 4 March 2020 (UTC)
Noted for them that the PvXcode rewrite fixes an issue on their tracker. All that's left to do is wait. Also told them to get rid of PvXVote. Maybe having one less extension to maintain after all this will endear them to us? -Toraen (talk) 17:35, 5 March 2020 (UTC)
Good suggestion on removal of PvXVote. I believe the two rewrites should address all issues currently identified on the Curse noticeboard. -Chieftain Alex (talk) 18:18, 5 March 2020 (UTC)
Out of the blue, PvXCode just got merged into the master branch. PvXRate might be soon. I really hope nothing breaks because after the 2 months of persistent chipping away at php, I can't remember much now ;) -Chieftain Alex (talk) 19:19, 31 March 2020 (UTC)

PvXCode: Live

PvXCode 2.0.0.0
It's nice to see the new functionalities and fixes to so many old issues. Will you take care of the curse noticeboard? I've found three minor issues that have been introduced with PvXCode 2.0, see here. --Krschkr (talk) 23:25, 1 April 2020 (UTC)
We'll need to remove all the crap on MediaWiki:Common.css to fix the display bug, since i rolled the CSS into the correct sheets. The hard bit will be remembering which CSS is from the other extension which has not yet been updated (I envisaged updating both at once). -Chieftain Alex (talk) 23:44, 1 April 2020 (UTC)
CSS fix applied. Requested patch for the broken downloadtemplate link (image and wiki resource urls are a pain in the butt to test).
I assumed the curse dev wiki link would be used as a test a bit longer before pushing everything live. -Chieftain Alex (talk) 00:02, 2 April 2020 (UTC)
PvXCode 2.0.0.1
  • Whitespace bugs are fixed as far as I can tell.
  • PvP download codes are working for the 8 pvp skills which were missing from the database.
  • If anyone sees any display weirdness on tooltips, the page might need a null-edit or a purge (this will reload the CSS provided by Extension:PvXCode) - I've run a bot to purge all pages in the Build and Archive namespace so they should display correctly.

-Chieftain Alex (talk) 20:34, 21 April 2020 (UTC)

PvXRate: Live

The patch to PvXRate 2.0.0.0 is live.

Main points
  • Anonymous users can now also view build ratings. They can't submit them afaik.
  • There is now a link to your personal Ratings when you hover over your username in the toolbar in the top-right.
  • We can now search by other user's ratings by sticking their name on the end of Special:UserRatings, e.g. Special:UserRatings/@DeletedUser5344.

I've sadly spotted a bug such that the extension provided "Rate" tab has been hidden on build pages for the moment, I'm sure we can figure out a fix though, and we've got the old fallback still live. -Chieftain Alex (talk) 20:30, 21 April 2020 (UTC)

I've set up a project page for this so we can coordinate better, since we appear to have a third person now and this talk page is getting a little bloated with the extension update chat. Feel free to expand the contributing guidelines and/or add goals to the page. -Toraen (talk) 15:33, 24 April 2020 (UTC)

Congratulations!

Your RFA was successful and you've been given Administrator user rights. I'll get in contact with you soon when I meet you ingame to talk about a few things. --Krschkr (talk) 01:37, 18 February 2020 (UTC)

Blimey thanks mate! -Chieftain Alex (talk) 18:17, 18 February 2020 (UTC)
I haven't had any luck seeing you ingame. Would you be so kind to contact me? --Krschkr (talk) 20:48, 3 March 2020 (UTC)
Sent a quick mail over. I'm on discord way more often than ingame (ChieftainAlex#8818). -Chieftain Alex (talk) 21:23, 3 March 2020 (UTC)
Have you had time to look into the build page case(s) I've sent you? --Krschkr (talk) 01:28, 30 March 2020 (UTC)
I hadn't set any time aside, but I found a nice documentary to watch whilst figuring out half the story. I've looked at Build:Team - 7 Hero BiP Melee Support and will look at Caster Support some time later this week. Findings at User:Chieftainalex/sandbox2. -Chieftain Alex (talk) 23:23, 30 March 2020 (UTC)

Stuff

  • This is pretty much what I wanted to do to replace the main page category links but was too bad at DPL to accomplish. I was going to have one page each for each gametype like that (with pretty much those filtering options). Only things I'd maybe want to add at some point is stuff like filtering on the requires-cons, mercs, zei ri, or flux categories (not sure how difficult this would be).
  • Is there anything else needed before [[my revision]] is pushed to the real template? I'll need to bot replace all of the 'provisional/meta=yes' to 'status=provisional/meta' ofc. -Toraen (talk) 16:44, 3 March 2020 (UTC)
  • The requires zei-ri/merc/flux categories would be a bit trickier to display because it isn't set in Template:Real-Vetting.
  • Your revision including the whole "all new categories for every build etc"? Might need to think about what the Main page looks like before pushing everything in that proposal live. -Chieftain Alex (talk) 21:22, 3 March 2020 (UTC)
The new category scheme can be commented out/removed for now if you copy it over. All the old categories are still applied. I just want to deprecate archived-build and make meta & provisional exclusive like they're supposed to be. -Toraen (talk) 21:41, 3 March 2020 (UTC)
Alright it's all live. At the moment I've left the old and new category schemes in parallel so that we can muck around with DPL queries. If you could go ahead with your bot account and update "provisional=yes" to "status=provisional", and "meta=yes" to "status=provisional" that'd be good. Until then the meta and provisional categories will be empty.
Something I missed though is that some of the category names are a bit crappy per the markup comments in the template. -Chieftain Alex (talk) 22:20, 3 March 2020 (UTC)
Also wondering about whether the pages in the Archive namespace should receive new categories too. -Chieftain Alex (talk) 22:42, 3 March 2020 (UTC)
Made placeholders for now. Also it appears the template isn't correctly handling things when 7 or more types are on the build: see anything in Category:Using unknown type. -Toraen (talk) 22:59, 3 March 2020 (UTC)
Cough. My bad! -Chieftain Alex (talk) 23:05, 3 March 2020 (UTC)
tbf that one was probably my fault at some point. Not diving into edit history if you won't though! -Toraen (talk) 23:08, 3 March 2020 (UTC)
At the moment both Build and Archive pages both land in the same new categories. I'm thinking the archived pages probably should not be in these categories. Maybe duplicates of all of the categories with "_archive" at the end? -Chieftain Alex (talk) 21:35, 4 March 2020 (UTC)
DPL queries can filter by namespace so I intentionally did that, as I planned to also use the same categories for relevant guides. That way whatever portals we design to show builds can also show guides (we have a few that are worth increased visibility). I actually intended to do away with the category tables on the main page, overwrite the currently useless portal pages, and have them linked in place of the table (maybe in a grid/button format to look pretty, sorta like this). The archives don't have to show on those pages, but sortable archives portals could be made. -Toraen (talk) 17:16, 5 March 2020 (UTC)

[1] + [2]

Don't worry, I am also drunk. Took me way too long to figure out this as a result. Good news is that my bot can now verify ratings and I'm pretty sure it won't make any errors! Except that meta builds with 2-4 votes will get Good/Great applied, but we should probably change the policy to that anyway. -Toraen (talk) 10:11, 26 April 2020 (UTC)