MasterShotgun
brazen editing lynx
Zomba13 said:Time until unlock: 71:23:18
The clock doesn't show the right time, the page's source code does however. We are helping.
Nice find. I hope that's true and not some weird error.
Zomba13 said:Time until unlock: 71:23:18
The clock doesn't show the right time, the page's source code does however. We are helping.
Zomba13 said:Time until unlock: 71:23:18
The clock doesn't show the right time, the page's source code does however. We are helping.
That's esentially what was posted in the ARG chat.MrMister said:We've already boosted by 20 hours? What.
Steam only tracks one game at a time.Untracked said:Is it worth having more than one Potato Sack game open at once? Does it help at all?
Or am I just gonna fry my PC?
MrMister said:We've already boosted by 20 hours? What.
MrMister said:We've already boosted by 20 hours? What.
Phantom Limbs said:So this GLaDOS@Home is similar to the PS3's folding@Home I take it?
What exactly was folding@Home, basically the same thing we are doing here? Leaving our games running to combine power and computations to cure diseases?
Thanks!darkressurection said:Steam only tracks one game at a time.
It's probably because of the X next to the number of potatoes. My guess would be that the top bar is progress towards a certain amount of calculations completed and that the total number of potatoes of everyone currently playing one of the games determines the number of calculations completed over a certain period (one minute?) for each CPU (person in one of the games).Teknopathetic said:"But then what's the purpose of the potato multiplier on the bottom of the site?"
Why are you assuming it's a multiplier and not a total of potatoes everyone's collected? At any rate, if you go to the Steam stats you'll see that the number of CPUs per game currently equals the number of people playing that game.
I AM ENTITLED TO DYNAMICALLY CHANGING VALUES BECAUSE I AM A VALVE FAN THAT BUYS GAMES. WHERE IS MY EARLY RELEASE THAT I DESERVE FOR OPTIONALLY TAKING PART IN THY ARG?!Drkirby said:That value is oddly static though.
This is certainly a possibility. Because right now, that End of the World game is very disproportionate. The bar's huge even though only 1200 people are playing.raphier said:I don´'t know....http://forums.steampowered.com/forums/showthread.php?t=1837491 I think this makes more sense.
Zombie James said:71 hours brings it to Monday afternoon, ~12PM EST.
JaseC said:It's not 71 hours. The counter on the page itself is correct.
Has that value in the source changed at all since the countdown page launched, though? Or was it just an arbitrary value in the source that someone quoted once and people assumed was accurate?enzo_gt said:I AM ENTITLED TO DYNAMICALLY CHANGING VALUES BECAUSE I AM A VALVE FAN THAT BUYS GAMES. WHERE IS MY EARLY RELEASE THAT I DESERVE FOR OPTIONALLY TAKING PART IN THY ARG?!
Zombie James said:The page counter hasn't changed at all, though, even though people are playing.
we shaved off 20-30 hrs in about an hour and a halfZombie James said:71 hours brings it to Monday afternoon, ~12PM EST.
Zombie James said:The page counter hasn't changed at all, though, even though people are playing.
Not sure, what if valve is refreshing the page with their own internal calculated values on a time interval? Isn't that a possibility or would the updating bit be in the code somewhere?Blizzard said:Has that value in the source changed at all since the countdown page launched, though? Or was it just an arbitrary value in the source that someone quoted once and people assumed was accurate?
Feep said:I don't know where people are getting this 71 hours number from. Counter remains the same here.
If I had to guess, I'd say the counter will decrease as normal until one of the individual game bars fills up completely, at which point the processing will "speed up" and the time remaining will suddenly drop by a significant percentage.
Just my guess.
<div id="console">
08:57 - Default boot scheduled to finish in <span id="console_clock">71:23:18</span><br>
08:58 - Activating emergency distributed computing grid...<br>
09:00 - GLaDOS@home starting...<br>
09:01 - Recruiting cpus to force faster boot sequence...<br>
SalsaShark said:Might be up for this. I hate how Killing Floor doesnt support dual monitors though, it goes all crazy when i launch in fullscreen :/
It's possible, but unless someone has ever seen a different value in the page source, then I'd assume it's false hope.enzo_gt said:Not sure, what if valve is refreshing the page with their own internal calculated values on a time interval? Isn't that a possibility or would the updating bit be in the code somewhere?
@MT come at me bro.
@Feep people say it's in the page code. Can't check myself, posting from iPhone.
<script type="text/javascript">
var g_endTimeLocal = 332552 + ( Math.round( new Date().getTime() / 1000 ) );
var g_bEnded = false;
function refreshClock()
{
if ( g_bEnded )
return;
var timeCur = Math.round( new Date().getTime() / 1000 );
var secsRemaining = g_endTimeLocal - timeCur;
if ( secsRemaining < 0 )
{
g_bEnded = true;
secsRemaining = 0;
}
var remainHours = Math.floor( secsRemaining / 3600 );
var remainMinutes = Math.floor( ( secsRemaining % 3600 ) / 60 );
var remainSeconds = secsRemaining % 60;
var str = (remainHours < 10 ? '0' : '') + remainHours + ':';
str += (remainMinutes < 10 ? '0' : '') + remainMinutes + ':';
str += (remainSeconds < 10 ? '0' : '') + remainSeconds;
var clock = document.getElementById('clock');
var consoleclock = document.getElementById('console_clock');
if ( clock.textContent )
{
clock.textContent = str;
consoleclock.textContent = str;
}
else
{
clock.innerText = str;
consoleclock.innerText = str;
}
}
refreshClock();
document.getElementById('clock').style.display='';
window.setInterval( refreshClock, 1000 );
</script>
I already played it on the Gameboy Color. S:morningbus said:Hey, if you didn't own Toki Tori before this, that was your fucking fault.
Jubbly said:Really? Works perfectly on my NVIDIA Surround setup.
Well, for anyone who hasn't followed the ARG, now's the time to check it out.Jenga said:i think my real complaint is that they launched the portal 2 special content a bit early
so instead of actually playing the new shit people are just alt-tabbing and idling
JaseC said:At all? Are we looking at the same counter? It hasn't move in a noticeable manner, but it's still moving.
looks like a clock script to me, thats about itIgor Antunov said:Can anybody eek any hints out of this script?
Code:<script type="text/javascript"> var g_endTimeLocal = 332552 + ( Math.round( new Date().getTime() / 1000 ) ); var g_bEnded = false; function refreshClock() { if ( g_bEnded ) return; var timeCur = Math.round( new Date().getTime() / 1000 ); var secsRemaining = g_endTimeLocal - timeCur; if ( secsRemaining < 0 ) { g_bEnded = true; secsRemaining = 0; } var remainHours = Math.floor( secsRemaining / 3600 ); var remainMinutes = Math.floor( ( secsRemaining % 3600 ) / 60 ); var remainSeconds = secsRemaining % 60; var str = (remainHours < 10 ? '0' : '') + remainHours + ':'; str += (remainMinutes < 10 ? '0' : '') + remainMinutes + ':'; str += (remainSeconds < 10 ? '0' : '') + remainSeconds; var clock = document.getElementById('clock'); var consoleclock = document.getElementById('console_clock'); if ( clock.textContent ) { clock.textContent = str; consoleclock.textContent = str; } else { clock.innerText = str; consoleclock.innerText = str; } } refreshClock(); document.getElementById('clock').style.display=''; window.setInterval( refreshClock, 1000 ); </script>
Nothing is of note in this code except the number at the very top of the code when initializing g_endTimeLocal. That number LOOKS hard coded, but that's odd, since doing the math out (332552 / 3600) yields 92 hours and change, which is NOT what the original timer started at (94 hours). It's possible that number is dynamically generated via another script. Finding that script would yield actual results.Igor Antunov said:Can anybody eek any hints out of this script?
Code:<script type="text/javascript"> var g_endTimeLocal = 332552 + ( Math.round( new Date().getTime() / 1000 ) ); var g_bEnded = false; function refreshClock() { if ( g_bEnded ) return; var timeCur = Math.round( new Date().getTime() / 1000 ); var secsRemaining = g_endTimeLocal - timeCur; if ( secsRemaining < 0 ) { g_bEnded = true; secsRemaining = 0; } var remainHours = Math.floor( secsRemaining / 3600 ); var remainMinutes = Math.floor( ( secsRemaining % 3600 ) / 60 ); var remainSeconds = secsRemaining % 60; var str = (remainHours < 10 ? '0' : '') + remainHours + ':'; str += (remainMinutes < 10 ? '0' : '') + remainMinutes + ':'; str += (remainSeconds < 10 ? '0' : '') + remainSeconds; var clock = document.getElementById('clock'); var consoleclock = document.getElementById('console_clock'); if ( clock.textContent ) { clock.textContent = str; consoleclock.textContent = str; } else { clock.innerText = str; consoleclock.innerText = str; } } refreshClock(); document.getElementById('clock').style.display=''; window.setInterval( refreshClock, 1000 ); </script>
Rapstah said:From the page source.Code:<div id="console"> 08:57 - Default boot scheduled to finish in <span id="console_clock">71:23:18</span><br> 08:58 - Activating emergency distributed computing grid...<br> 09:00 - GLaDOS@home starting...<br> 09:01 - Recruiting cpus to force faster boot sequence...<br>
EDIT: And it's also the same number as before... yeah.
Kulock said:Killing Floor updates, the latter is a fairly big one.