Essentially, Step 3 is where the project structure and configuration (including the imports) is prepared for eclipse, while Step 4 decompiles Minecraft, providing the imported libraries. I think in your particular case you most likely need to revisit those particular steps if your imports are giving you errors.

If you’re unfamiliar with this feature I recommend using Eclipse’s auto-suggestions to populate the needed imports, it’s as simple as a right-click on the class you need to import and there’s no digging in the package explorer required! If Eclipse is not auto-suggesting the imports for you, you’ll need to double-check that your project was initialized (via gradle) and imported correctly as it’s most likely that a library containing that class has not been included in the project.

The process of renaming files you describe is known in programming as “refactoring” and I incorporated it here as the goal of this tutorial is not to teach “future proof” naming conventions, it’s intended to be a simple introduction of some of the modding concepts piece-by-piece and to help familiarize beginners with the mod architecture by navigating them through making changes as they go.

I can confirm the tutorial does work, as it’s been completed by many readers in the past year and a half or so, so I would encourage you to investigate and cross-reference another tutorial if your imports are still giving you trouble.

All the best!