Sure EmuGod, I have the file downloaded, so I’ll give it a check over. The file is NOT the same as the previous one though, the wording is different, it refers to the previous one, and as you can tell the checksum is different.
EDIT:
I guess seeing as Jake has written his transcript, I’ll just start decoding.
EDIT 2:
Weird, my decoding software doesn’t seem to like this one. Anyone got a good piece of software that could do it?
Ok, so I think this is where we are with alert message: #1 warning was because of resonant cascade, and everyone should evacuate because of warning #2 #2 warning was because g-man detonated thermonuclear bomb (hence warning about hair loss and others)
If we take HL: Opposing Force storyline, then g-man reactivated thermonuclear bomb, and by that time, original half life storyline has already ended.
EDIT: Just figured something. If Tempus omnia revelant means Time will reveal all, then now we got actual timer, along with Terminal BMRF being down, then when timer goes down, we might get:
A) something releated to Black Mesa, like Xen update
B ) Terminal BMRF opening again
C) both (obviously)
Also, take a look at Storm’s profile, he has :bms: emoticon on his profile description.
Also: https://imgur.com/0o3dtvp
[code=html,‘bmrf.us’]unction init() {
camera = new THREE.PerspectiveCamera(55, 1080/ 720, 20, 3000);
camera.position.z = 1000;
scene = new THREE.Scene();
//init video texture
videoTexture = new THREE.Texture(video);
videoTexture.minFilter = THREE.LinearFilter;
videoTexture.magFilter = THREE.LinearFilter;
videoMaterial = new THREE.MeshBasicMaterial({
map: videoTexture
});
//Add video plane
var planeGeometry = new THREE.PlaneGeometry(1280, 720,1,1);
var plane = new THREE.Mesh(planeGeometry, videoMaterial);
scene.add(plane);
plane.z = 0;
plane.scale.x = plane.scale.y = 1.45;
//init renderer
renderer = new THREE.WebGLRenderer();
renderer.setSize(1280, 720);
document.body.appendChild(renderer.domElement);
//POST PROCESSING
//Create Shader Passes
renderPass = new THREE.RenderPass(scene, camera);
badTVPass = new THREE.ShaderPass(THREE.BadTVShader);
rgbPass = new THREE.ShaderPass(THREE.RGBShiftShader);
filmPass = new THREE.ShaderPass(THREE.FilmShader);
staticPass = new THREE.ShaderPass(THREE.StaticShader);
copyPass = new THREE.ShaderPass(THREE.CopyShader);[/code]THREE
That’s ain’t funny anymore.
In cases like emergency broadcast beeps like this being used as an attention signal to get everyone listen to message
Military use signals like this as information space filler and somewhat test signal
The beeps include information about the message, and the locations which are important in this regard. I can take a screenshot of how it shows up in my decoder in a minute. However, in the case of this one, the beeps are just a generic Florida test.
This is probably the Actual Black Mesa app. It has the same number as the workshop page and the trading cards. It is also bundled in with the Dedicated server.
Bit late to the party there CPU - already decoded the header and transcribed, but it just seems to be like the previous, nothing out of the ordinary at all.
EDIT: Here’s the header return for any interested groups: decoded
I just remembered that EAS alerts contain some data,in the form of beeps at the beginning, which are headers of text encoded using SAME. Usally it’s just location and misc. information, but you could have a message in it. I’m pretty sure that the BMRF EAS broadcast has a SAME header.
Edit: It appears that the SAME header is taken from a EAS test in flordia as this is what I get from decoding :
05/04/15 21:14:50 UTC
ZCZC-EAS-RWT-012057-012081-012101-012103-012115+0030-2780415-WTSP/TV-´
Message from EAS Participant
Required Weekly Test
. FLORIDA - Hillsborough
. FLORIDA - Manatee
. FLORIDA - Pasco
. FLORIDA - Pinellas
. FLORIDA - Sarasota
Message valid for 30 minutes from the issue time of 04:15 UTC (00:15 local time) of the day: 5 .
So this event is expected to last until 04:45 UTC (00:45 local time) at least, or longer.
EDIT 2; Nevermind, it seems that someone else decoded it on the last page.
Now see I think that a third broadcast would be the nuke.
My understanding that around 2 pm the military looses control of the situation (Hence the last one expiring at 12pm) And another thing I thought of is that the Xenians are teleporting further and further away from Sec C during the entire story so I believe it has something to do with that.
I think the nuke has already been detonated, hence the warnings about hair loss, etc. etc.
Oddly enough, I’m wondering if Horn had predicted all of this, seeing as how he apparently had the HALOS project moved after the resonance cascade. Remember the “PRIMESITECOMPROMISED” clue?
I’m betting that these next stages are simply the next stages of the ARG, and we will probably still need to solve the HALOS.txt file before starting these stages. As Storm himself noted in his PM, this is likely a holding puzzle to give them time to work on whatever is behind their nondisclosure etc. etc. The good news is, the fact that he has some extra time to work on this could indicate the Xen will be on its way relatively shortly (read: soonish).
Personally, I think that we can have no fucking clue where this is in relation to the time of nuke detonation (Is that even canon now?) and that when the nuke goes off, everything already had went to hell. Given all the experimental weapons, biological weapons, and literal aliens invading (Especially since they figured out headcrabs can already make zombies) It’s understandable for those precautions, because the government wants to make sure a plague doesn’t start steamrolling humanity. For all I know, CEDA went down their with their wimpy hazmat suits. The point is, after the government nukes their own top secret research lab, I’d say the Godzilla threshold has passed, and they have a lot more pressing matters on their doorstep than hopeless evacuations.
As for the ARG itself… GL HF
Just saying the warning you cited doesn’t really nail down the nuke had hit the fan.
Soooooo… Hi all again. I was being haunted by one of stormseekers old “hints” in regards to the 752 Hex Code…
“It’s everywhere you look.”
Has anybody tried using PIZZA as the decryption key? Again, I’m pretty dumb with all this stuff, but we are all staring at a pizza code mystery chat room, thread, or wiki when we’re dealing with this. Pizza is everywhere in regards to this stuff.
Brackets are finished - which leads to thought that this is meant to be some kind of twisted text in which we should read something
Also “БОЙСFC” is very similar for me to “БОЙСЯ” - “do fear (of something)” in russian
But this may be just a coincidence and my theory is more that crazy
In any case has anyone tried to use OTR?
EDIT: BMRF.US changed once again, now featuring no message, and showing gman glimpses again
It has; on previous occasions we’ve also found a headcrab and … some thing I can’t pronounce. HL1 final boss, I believe? I dunno, it’s on the wiki somewhere.
In case you’re wondering: if you check out the source code for those pages, the long big mess of hex codes and escaped ASCII (?) characters at the bottom is what is used to generate these. =)
Founded in 2004, Leakfree.org became one of the first online communities dedicated to Valve’s Source engine development. It is more famously known for the formation of Black Mesa: Source under the 'Leakfree Modification Team' handle in September 2004.