this = new Planet(gravity = Ø, existence = Ø): \\TODO coloring and formatting for .verse scripts\\
  this.delete(this); \\in order to keep from existing on start\\
  this = makeCopy(Earth.vplanet); \\Use Earth as a baseline (a common move for habitable terrestrial planets)\\
  mass = inherit; \\TODO fill in inherit with real values\\
  existence = !Ø; 
  mineralAbundance(Iron) = Mars.vplanet.mineralAbundance(Iron) \\Make the planet red\\
  parentStar = Mèna_Qaròsz.vstar
  if(this != this):    \\Fixing bug of planet corrupting\\

  "Why would I want to create a planet that doesn't exist and then delete it immediately afterwards. Well,  the way vplanet files work is that they can't run copy commands until the planet is created. However, some problems can arise if you try to make a copy of a planet onto another (existing) planet. The reason for such a bug is that the makeCopy function is meant to be run by the star, to copy planets. However, some clever planet makers wanted to make a habitable planet and copy Earth to do it but didn't have access to the star file. So, what did they do? They wrote code to copy the planet in the actual planet script, and now it is standard practice for habitable planets."
Community content is available under CC-BY-SA unless otherwise noted.