Steve [hollasch]:
For each new file that students will write, enumerate the import statements they'll be using. This way we don't have to reference types like net.minecraft.world.World, and can just say World.
Connor [chollasch]:
It is quite possible that the majority of their imports will be via the net.minecraft package so we could even wildcard import all of the net.minecraft classes with the following:
import net.minecraft.*;
Michael [hawkerm]:
It won't grab subpackages that way though so in the example above they'd still need to import net.minecraft.world.* still too. We run into this with Space Battle too, but only have three packages they need at most throughout the project.
Steve [hollasch]:
Three packages should cover us as well, then.
[Imported from original tealsMC repo]
Steve [hollasch]: For each new file that students will write, enumerate the import statements they'll be using. This way we don't have to reference types like net.minecraft.world.World, and can just say World.
Connor [chollasch]: It is quite possible that the majority of their imports will be via the net.minecraft package so we could even wildcard import all of the net.minecraft classes with the following:
Michael [hawkerm]: It won't grab subpackages that way though so in the example above they'd still need to import net.minecraft.world.* still too. We run into this with Space Battle too, but only have three packages they need at most throughout the project.
Steve [hollasch]: Three packages should cover us as well, then.