I did my research and found a couple answers/solutions, but nothing seemed to work unless I am really overlooking something.

 

I'm following a tutorial and just starting out with modding and it's all going pretty well so far, except when I go to run minecraft from Eclipse. The game works but is slow, laggy, and gives me an error that it is unable to play every sound it tries to find (probably causing the lag). I made sure that the "assets" folder is in my eclipse project path folder and even directed the run configurations to point at the "eclipse" folder, but still no luck. All my modded items are working and all, just no sounds.

 

Forge version: 1.7.2 (haven't found any solid 1.7.10 tutorials. Not sure what the differences would be though either).

 

It's probably something stupid I'm overlooking, but any help is appreciated.

Hate to bump, but does anyone have any ideas at all?

If you have a minecraft client installed on the same machine as you use for development (because you're both a player and a modder), then you can find its assets and point Eclipse at them by passing an extra argument in the run -> configurations dialog. Add something like this:

 

--assetIndex 1.7.10 --assetsDir "C:\Documents and Settings\Jeff Fisher\Application Data\.minecraft\assets"

Note the double quotes used to encapsulate the string that has spaces within it. I think this is throwing some people who imitate an unquoted example but have a username containing a space.

 

If you don't have a client installed on your dev machine, then gradle has an assets folder, but its ~/virtual/legacy folder might be empty, requiring you to go find some contents to copy there before pointing to it. See "C:\Documents and Settings\<user name>\.gradle" or "C:\user\<user name>\.gradle" (adjust to your OS version).