Java Edition Classic 0.0.14a 04

Minecraft Wiki article. Categories: Lost_versions, Unknown_al_version, Java_Edition_versions, Java_Edition_Classic_versions, Java_Edition_Early_Classic_versions

📌 Mirrored from Minecraft Wiki

This article is reproduced from Java Edition Classic 0.0.14a 04 on the Minecraft Wiki. Mirrored from revision 3656869. It is licensed CC BY-NC-SA 3.0 by the Minecraft Wiki contributors — not under the Codex’s CC BY-SA 4.0, and it may not be used commercially. Edits belong upstream, not here.

This version is currently lost.
 
While this version is known to exist, it has not been archived in the launcher or elsewhere, and is therefore considered lost.
If you believe you have a copy of this version, please post it on the talk page.
0.0.14a_04

0.0.14a_04[1] is a version of Java Edition Classic released on May 28, 2009, at 17:35 UTC, which added spawn point saving and reloading using the ⏎ Return key.[2]

0.0.14a_04 was reuploaded at 17:43 UTC, 8 minutes after release, to try and fix an issue with mouse control; this fix was unsuccessful.[3]

Additions

Gameplay

Controls

  • Added spawn point saving and reloading using the ⏎ Return key.
  • Pressing R now sends the player back to the world's spawn point.

Bugs

1 bug reported

  • This version had an issue with mouse controlling.[3]

References

  • IRC logs, #minecraft.20090528.log (May 28, 2009, UTC+2)
  1. ↑ "0.0.14a_04 now lets you set the spawn point" (archived) – The Word of Notch, May 28, 2009.
  2. ↑ IRC logs: "(19:35:52) * notch changes topic to: http://www.minecraft.net/ | http://www.mojang.com/forum/ | 0.0.14a_04 is up. You can now set the spawn point with return." (17:35 UTC)
  3. ↑ a b IRC logs: "(19:40:02) <justinforasec> hey notch there might be something wrong with mouse control, mines very... weird" [...] "(19:40:22) <mezo> mouse movement seems very bugged" [...] "(19:43:35) <@notch> is the mouse look fixed now?" [...] "(19:44:02) <mezo> mouse is fixed" [...] "(19:44:09) <mezo> nm no it's not" [...] "(19:45:13) <mezo> doesnt do it", "(19:45:21) <mezo> it's fine for about two seconds then it deteriorates" [...] "(19:45:41) <mezo> it's very jittery, as if it's only reading a few dpi" (17:40 to 17:45 UTC)

Sources