Template talk:AutoServerStatus

The server status displays inconsistent icons sometimes. I just checked again and now they're all on Update. Last time the server icons sere all on Online/Event even though the overall status was Update. Nobody has been changing the wiki status.

As Nexon works on maintenance, they put up/down the servers constantly to check stuffs. I guess it was a coincidence that the server status was refresh at the time of then putting up the servers again.

Yeah, the script is not broken. It reflects the actual state of the game servers. People keep overriding it because they think it's broken. Look at current game status and Login server. Those are always accurate during maint.

I don't think that is a very good user experience. Nobody was overriding the manual status. Why not just set all servers to update during an update?

Because, the script isn't smart enough to know there's an update. And what if the login server goes down, but the game servers are still up?

If "Current Game Status" is set to "Update", set everything else to the same. What situation would occur where the first is true and the latter is not?

Its actually the inverse....

If Login = online
    GameStatus = best of the servers
else
    GameStatus = login status

What's the algorithm for setting update then?

What do you mean by "setting update"?

The script looks at offline override, and uses that if the server is offline. Hence, if the login server is offline, and OfflineOverride is 'Update', the login status will be 'update'. Same with everything else.

So if the login server is offline and OfflineOverride is Update, set all servers to Update.

I guess. People seem to like the 'actual' statuses though. Too bad we can't do a poll on the wiki.

I like the actual statuses though. Cause it helps map down boss timers...

Can you explain how having Update instead of Online helps this?

No i mean when it's showing the ACTUAL statuses. Not an override.

"Online" would be the actual status. Either way, I am still confused as to how this helps.

Aubog looks at the actual statuses. By knowing (more or less) exactly when a server comes online (before the login does!), he can time the boss spawns.

If we set all statuses to update when the logon is update, then he can't time them properly.

I can time them in other ways. But Eh. It's really easier this way.

The widget no longer scrolls, it just gets cut off. No bar either.

And this page isn't semi protected either. Don't do full because I'll need to update the url when we move the script.

It scrolls for me on both Chrome and Firefox when I expand a server. Screenshot? The URL is not in this page anymore because it's embedded directly in the new widget. IJ will have to be around to move the script anyway, so he can edit the widget when the time comes.

Screenshot It only does it on my phone. Not a major issue as few people use their phones to browse the wiki, but we should probably keep an eye on it.

We could create a page at Widget:AutoServerStatus and put this inside: <div class="center" style="width: 358px;"><object data="http://shywreaths.org/MabiServerStat/index.php" type="text/html" style="width: 358px; height: 210px; border-width: 0;" standby="Loading Server Statuses"></object></div>

And then on the homepage we would have {{#widget:AutoServerStatus}}. This removes the XSS risk of allowing anyone to use iframes but also makes the code valid XHTML 1.0 Strict because it uses the object tag instead. It also works on all modern browsers, including IE ~小太郎 ^TALK_CONTRIBS 2011:10:11:05:30 (Tuesday)

So precisely, what difference does it make?

Visually, nothing. Apart from that, "This removes the XSS risk of allowing anyone to use iframes but also makes the code valid XHTML 1.0 Strict because it uses the object tag instead." ~小太郎 ^TALK_CONTRIBS 2011:10:11:08:41 (Tuesday)

i don't think it's needed, the reason we use the Widget extension instead of the Iframe extension is because it's made to be secure against that... http://www.mediawikiwidgets.org/Talk:Iframe#Security_risk.3F

What stops other users from making their own iframe widgets? If nothing, then doing this and removing the iframe widget would be safer. Just because the widget isn't as crazy insecure as the other one mentioned doesn't mean it's not a security hole. Though I'm not sure about the whole object tag thing. MediaWiki is HTML, not XHTML so that part is irrelevant.

Users can create widget instances at will, so I deleted the iframe widget and made a server status widget. When the actual iframe contents are hosted on the wiki, I think we should be ok.

OK, thanks. Just a quick question: How does the AutoServerStatus widget work? I had to include the "target" element in my script's links due to the iframe. Is that still needed?

It works the same as before, so yes.

Thats something to be fixed then, 'Target' is not valid HTML strict... Perhaps we use AJAX instead?

Oh, I guess I was wrong. The wiki is supposed to be XHTML strict. I don't see a point in worrying about it because there are a zillion other errors anyway.

Do what we can in the user code to make the wiki as valid as possible. Even if the wiki code itself is not valid, when they finally do become valid, it would be easier for us since our code is already valid ~小太郎 ^TALK_CONTRIBS 2011:10:11:22:39 (Tuesday)

I don't think it is possible to make it valid using iframes.

Hence my suggestion of Ajax.

Using AJAX defeats the purpose of all of your JavaScript fallback code.

Remember, using my method, we wouldn't be using iframes anymore, but objects ~小太郎 ^TALK_CONTRIBS 2011:10:11:23:03 (Tuesday)

That would make the main page validate but not the included page.

The included page is counted as a completely different page, so it isn't really "de-validating" the wiki ~小太郎 ^TALK_CONTRIBS 2011:10:11:23:31 (Tuesday)

IMO, if you're going to worry about validating in the first place, you should be worried about *everything* validating. But my line of caring has crossed, so it's up to you guys.

It looks like object tags don't respect width/height CSS. See the main page.

Fixed it. Uses width/height attributes just like iframes.

You forgot the standby="Loading Server Statuses" attribute! It shows the text when the page is being loaded ~小太郎 ^TALK_CONTRIBS 2011:10:11:23:32 (Tuesday)

Fixed.

You forgot the standby="Loading Server Statuses" attribute! It shows the text when the page is being loaded ~小太郎 ^TALK_CONTRIBS 2011:10:11:23:32 (Tuesday)

Just tell me when I can remove the target attribute xD.

Try removing the target attribute in firebug on the wiki frontpage and then clicking it. If it works and changes the whole page, then you can safely remove it on your site ~小太郎 ^TALK_CONTRIBS 2011:10:11:23:36 (Tuesday)

Does not work.

Google chrome would also work in place of firebug, would it not? That's my tool of choice.

Yes, that is what I used to test.