MS Paint Adventures Wiki
Advertisement
Archives
Archive 1 May 2009 - July 2010
Archive 2 June 2010 - March 2011

2013

Main page improvements

There are some minor issues on the main page, I have been steadily dealing with them but I would like the input of others.

The contents table - The articles listed under each section should probably be ones that deal with a lot of general and important information. The adventures and characters sections are fine, rather it is the locations, items and concepts that need to be revamped.
For example: Just a couple of months ago the locations for Homestuck were; John's house, Land of Wind and Shade, and Skaia, as of the present, Land of Wind and Shade has been replaced by the general article on planets, being as it is more general and has a broader scope. So an opinions on further additions, or outright replacements, for locations in Homestuck and Problem Sleuth?
The inventory sections was worse for Homestuck, the items a couple of months ago were; fake arms, smoke pellets (both of which were redirects to the magic chest article), and hammer, as of the present they have all been replaced. Any opinions on the replacements, plus further replacements, or additions, including the Problem Sleuth inventory?
And of course concepts, no changes yet but any ideas?

Helping out section - I've removed some stuff from here because it was more stuff to help when starting up a wiki, but any thoughts or opinions on removing, adding or rewriting the section so it may actually help people find ways to help the wiki?

- The Light6 (talk) 12:22, March 19, 2013 (UTC)

It may be worth considering rearranging the main page entirely, and putting a more thorough contents section in the main column. We could have things like the news in the sidebar (since entries are usually pretty short). Hell, if we wanted to, we could have additional features like a quote generator or featured image actually I dunno about a featured image we have enough trouble getting input on featured articles.
As to the helping out section, the single most useful thing I can think of to be included in that is a link to the projects thread. That is, after all, a pretty solid list of what things are in need of improvement -- Sorceror Nobody, 13:02, March 19, 2013 (UTC)

Gigapause Countdown

I think that the gigapause countdown should not show up if you don't have javascript. Otherwise, it just looks weird saying "the last update." I think a way to do this is by using a different countdown code below, and by typing in the other code below that.

// **************************************************
// Experimental javascript countdown timer (Splarka)
// Version 0.0.3
// **************************************************
//
// Usage example:
//  <span class="countdown" style="display:none;">
//  Only <span class="countdowndate">January 01 2007 00:00:00 PST</span> until New years.
//  </span>
//  <span class="nocountdown">Javascript disabled.</span>
 
function updatetimer(i) {
  var now = new Date();
  var then = timers[i].eventdate;
  var diff = count=Math.floor((then.getTime()-now.getTime())/1000);
 
  // catch bad date strings
  if(isNaN(diff)) { 
    timers[i].firstChild.nodeValue = '** ' + timers[i].eventdate + ' **' ;
    return;
  }
 
  // determine plus/minus
  if(diff<0) {
    diff = -diff;
    var tpm = '';
  } else {
    var tpm = '';
  }
 
  // calcuate the diff
  var left = (diff%60) + ' seconds';
    diff=Math.floor(diff/60);
  if(diff > 0) left = (diff%60) + ' minutes, and ' + left;
    diff=Math.floor(diff/60);
  if(diff > 0) left = (diff%24) + ' hours, ' + left;
    diff=Math.floor(diff/24);
  if(diff > 0) left = diff + ' days, ' + left
  timers[i].firstChild.nodeValue = tpm + left;
 
  // a setInterval() is more efficient, but calling setTimeout()
  // makes errors break the script rather than infinitely recurse
  timeouts[i] = setTimeout('updatetimer(' + i + ')',1000);
}
 
function checktimers() {
  //hide 'nocountdown' and show 'countdown'
  var nocountdowns = getElementsByClassName(document, 'span', 'nocountdown');
  for(var i in nocountdowns) nocountdowns[i].style.display = 'none'
  var countdowns = getElementsByClassName(document, 'span', 'countdown');
  for(var i in countdowns) countdowns[i].style.display = 'inline'
 
  //set up global objects timers and timeouts.
  timers = getElementsByClassName(document, 'span', 'countdowndate');  //global
  timeouts = new Array(); // generic holder for the timeouts, global
  if(timers.length == 0) return;
  for(var i in timers) {
    timers[i].eventdate = new Date(timers[i].firstChild.nodeValue);
    updatetimer(i);  //start it up
  }
}
addOnloadHook(checktimers);
 
// **************************************************
//  - end -  Experimental javascript countdown timer
// **************************************************
<span class="countdown" style="display:none;"><div style="padding-bottom:10px">
{|style="border:ridge 4px #000; background:#fff; text-align: center; color:#000; font-size:125%; border-radius:15px; padding:5px; line-height:1.50em" width="100%"
|<span class="countdown" style="display:none;"><span class="countdown" style="display:none;">'''HOMESTUCK GIGAPAUSE duration tracker:'''<br /><span class="countdowndate">16 Oct 2013 07:32:27 UTC</span> since {{HS|8752|the last update.}}.</span></span> </span>
|}
</div>

I made a version on a wiki that has this code enabled, if you want an idea of what it would look like. I had to remove the MSPA quote part on that version, however.

**EDIT** FUCK I FORGOT MY SIGNATURE Ylimegirl (talk) 20:30, February 2, 2014 (UTC)

2014

Redundancy

The wiki about MS Paint Adventures that anyone can edit. You put the redundancy of "wiki that anyone can edit" out of your mind.

Can we just remove this part? It isn't redundant. Some wikis have limited editorships, a wiki is simply something designed for collaborative, but wikis are not inherently universally collaborative. It is even possible to have wikis which are editable by only 1 or 2 people. +Yc 02:54, March 20, 2014 (UTC)

Advertisement