Some mods, even though the authors list them for 1.7.2 only, do work on 1.7.10. Some don't work though and crash during preload or just run poorly in 1.7.10. However since this is a version that the author(s) may not support yet, any crashes/issues/spontaneous combustion of their 1.7.2 mod is probably something they would not help fix until an official 1.7.10 version of their mod is released.
You are more than welcome to experiment though. Download the mod, drop it in your mods folder and start a new world. If it runs with no issues, great! Have fun with it. If it doesn't, bookmark or sub to the post so you can check back from time to time to see if there's a new version.
Keep in mind this is a large update - do not ask mod developers for ETAs.
When a 1.7.10 version of their mod is ready to be released, they will update the post accordingly.
Lastly, I can't say anything about WR, for whatever reason that mod doesn't want to work on my computer under 1.7.2 (even with the lib/core files and recommended forge version)... I'm not a redstone fan anyway so no big deal to me
In my experience, most are not. A lot of basic things even have changed, or are not yet deobfuscated.Even if the game doesn't crash, that doesn't mean the mod works - you could get into a world only to find that x days later of playing, the awesome mod item y doesn't do something when it should! Starting Minecraft + genreating a world + can see mod items does *not* mean that the mod is compatible!
Considering Forge for 1.7.10 is still beta, maybe it's best you stay on 1.7.2 for now? Many developers would not release (or even start to update) their mods for 1.7.10 until Forge is out of development stages - Forge for 1.7.10 is still being updated several times a day with bugfixes and stuff. Well so is Forge for 1.7.2 but at least it has a version marked "recommended".
Don't take this the wrong way though - I do encourage you to play with 1.7.10! The mod creators who HAVE updated their mods would value the feedback and testing! But if you want a stable experience to just play and don't have an interest in helping the mod creators, stick with 1.7.2
EDIT: The main issue with mod authors is not so much that it'd take a long time to update and test their mod; development tools are clever - it will tell them if something has changed in 1.7.10 since 1.7.2 (usually, not all the time). Things that use coremods, like NEI, are usually worth updating early because 1.7.10 itself is done and coremods are hard work - but the main issue is as I said previously - Forge/MCP for 1.7.10 is not finished.
Example: I've only been working on a 1.7.10 mod for 3 days and I've already found something that is still obfuscated. "getPlayerForUsername" is a method (a 'command' that a mod can use) that is often used, one place for example is when the server is shutdown (when you save and quit) it can be used to save all the custom data for the players who have joined this world. In 1.7.10, it is still obfuscated as "func_152612_a" - it took me half an hour to find that, I'm a newbie to modding sure but when Forge is finished I will need to change that *again*. And also other things i will probably have to change. This is not a huge issue for me because I am starting from scratch, there isn't too much for me to worry about since it's Forge is probably 90% done anyway (that's a very wild guess). If Forge for 1.7.10 was finished, this would not be an issue at all, and 1.7.2 mods would still work on this particular example. I think even 1.6.4 uses the same getPlayerForUsername method... but I digress.
My point is, it's for this reason specifically to not ask mod creators about an ETA for 1.7.10. Maybe you can politely ask them once 1.7.10 gets a "recommended" release, but each mod author is different
I wish to update my last answer, now that I know more.
I would guess that there is a 50/50 chance that any 1.7.2 mod will work fine with 1.7.10. Only a very few things have changed in regards to the areas that mods work in, so just try it. But, now this is technical, mods which use ASM or Coremods will likely NOT work - these will need to updated. I'm not sure what mods out there use ASM, but a lot of the complicated/awesome ones do e.g. NEI (but that's already got a 1.7.10 version).
So I say try it; but it may break your world! Try it if you want to test and help the mod author. And if you find that it works but has only a couple issues, report them to the mod maker (but of course don't demand they update).
That's a very rough estimate though, it's impossible to say without looking at the code. There are 1.7.2 mods use old 1.6.x code that, while still worked in 1.7.2, were already obsolete for it - and have since been removed completely in 1.7.10.
I downloaded a mod from 1.7.2 but in 1.7.2 there's no spectator mode, i want to go back to 1.8.3 for the spectator mode but im afraid my mods won't work anymore. Will my mods work when i go back to a later version of minecraft?
No, mods are version-specific. If a mod author says their mod only works for 1.7.10, it only works for 1.7.10. If they say it works for 1.6.4, it only works for 1.6.4. If they say it works for 1.8, it only works for 1.8. There are some exceptions, but these are minor updates, 1.7.2 -> 1.7.10, and not all mods are guaranteed to survive the update.
Rollback Post to RevisionRollBack
Author of the Clarity, Serenity, Sapphire & Halcyon shader packs for Minecraft: Java Edition.