Perhaps; maybe another way to do that would be to have songs that play "in sunlight", songs that play "in moonlight", songs the specifically play in darkness (when the light is below a certain level), and songs that play when in unnatural (for example torch) light.
Sounds like a very flexible approach to me, and probably not that difficult to implement, too. I actually forgot you can check for moonlight as well as sunlight, so I was thinking about altitude checks and other crazier ideas instead of keeping it simple and to the point.
I just noticed this post...how did I miss this? Anyhow, I personally used some more of C418's work in the End. From Minecraft-Volume Beta, I used "Ki" for survival and "Flake" for creative. From One, I used "imposter syndrome" and "swarms" for survival, and "cliffside hinson" and "danny makes chiptune" for creative. I also used "When you don't know what to do, just steal the amen break" from Life changing moments seem minor in pictures for the WitherBoss's theme.
By the way, what happens to default music tracks (calm1.ogg, piano1.ogg, etc) when the mod is enabled? Can they override the mod's music or they are being fully ignored by the game in favor of the mod's custom playlist settings?
By the way, what happens to default music tracks (calm1.ogg, piano1.ogg, etc) when the mod is enabled? Can they override the mod's music or they are being fully ignored by the game in favor of the mod's custom playlist settings?
They are still the defaults. If there are no music tracks that could apply to a certain situation, say for instance in a custom dimension, where you haven't added any music, then it will play that music instead.
If you want them to play with your custom music, you'll have to add them to the folders too. =)
They are still the defaults. If there are no music tracks that could apply to a certain situation, say for instance in a custom dimension, where you haven't added any music, then it will play that music instead.
If you want them to play with your custom music, you'll have to add them to the folders too. =)
Good to know, thanks for the explanation. I just hope you'll have no troubles updating to upcoming 1.8. I already spent hours on preparing music folders for the mod I don't even have installed on my 1.7.2 test version, heh-heh.
Good to know, thanks for the explanation. I just hope you'll have no troubles updating to upcoming 1.8. I already spent hours on preparing music folders for the mod I don't even have installed on my 1.7.2 test version, heh-heh.
Yeah, well even updating to 1.7 might be difficult. As I've discovered while I'm trying to update another mod (Sound Filters), they changed the sound system and made a bunch of the variables private, so I can't use them anymore. It could take a while find a workaround and update.
so, for now could you focus on 1.6.4 for the time being?[ ...] i'm glad you're gonna try to support 2 versions instead of just dropping support for one of them, like most modders do.
What about supporting 1.5.2? 1.4.7? 1.2.5? Even earlier versions? When does it stop? 1.8 is a vast improvement over 1.6 in several regards. It's worth (and certainly much easier for everyone) to update your server for the performance optimizations alone, let alone the fact that (considering how easy it is to update 1.7.2 mods to 1.8) in a month or two into 1.8, the 1.6 version will be all but forgotten. The same people who begged mod authors not to update will be wondering why it takes so long to get past 1.7 (possibly the most mod-devastating update in Minecraft's history) and begging mod authors to hurry it up and update to 1.8.
Sorry if I get too emotional here, but I have a long list of mods I expect to install when 1.8 comes out (my last server version was 1.5.2, so there's a lot of new stuff to experience there, no doubt). There are only few mods on that list that haven't updated or aren't in the process of updating beyond 1.7 yet, and this mod is one of them. Considering that this "small" mod is easily in the top ten of my most desirable and most immersive mods for the game—a list that includes established behemoths like Biomes O'Plenty, Mo' Creatures, Optifine, etc—I really don't want some shortsighted detractors to convince Tmtravlr to divert his precious time on maintaining a version that for all intents and purposes will become obsolete in a few months at the most.
What about supporting 1.5.2? 1.4.7? 1.2.5? Even earlier versions? When does it stop? 1.8 is a vast improvement over 1.6 in several regards. It's worth (and certainly much easier for everyone) to update your server for the performance optimizations alone, let alone the fact that (considering how easy it is to update 1.7.2 mods to 1.8) in a month or two into 1.8, the 1.6 version will be all but forgotten. The same people who begged mod authors not to update will be wondering why it takes so long to get past 1.7 (possibly the most mod-devastating update in Minecraft's history) and begging mod authors to hurry it up and update to 1.8.
Sorry if I get too emotional here, but I have a long list of mods I expect to install when 1.8 comes out (my last server version was 1.5.2, so there's a lot of new stuff to experience there, no doubt). There are only few mods on that list that haven't updated or aren't in the process of updating beyond 1.7 yet, and this mod is one of them. Considering that this "small" mod is easily in the top ten of my most desirable and most immersive mods for the game—a list that includes established behemoths like Biomes O'Plenty, Mo' Creatures, Optifine, etc—I really don't want some shortsighted detractors to convince Tmtravlr to divert his precious time on maintaining a version that for all intents and purposes will become obsolete in a few months at the most.
Like I said above, I'm only going to support 1.6 until I feel it's obsolete, and only if porting the changes between versions is easy.
=/ Sorry to burst your bubble, but even after 1.8 comes out, it could be 6 months before forge updates, and even longer before most forge mods update. Just look at how long it took for them to update to 1.7, and then how long it took to work out the major bugs, and finally then how long it took individual modders to update their code (and let me tell you, it wasn't easy. So much changed. When updating, my code was basically nothing but red error messages). But maybe that won't happen with 1.8; maybe updating will be simpler. And plus, this mod shouldn't be hard to update regardless, since not much will change with sound. =)
Like I said above, I'm only going to support 1.6 until I feel it's obsolete, and only if porting the changes between versions is easy.
=/ Sorry to burst your bubble, but even after 1.8 comes out, it could be 6 months before forge updates, and even longer before most forge mods update. Just look at how long it took for them to update to 1.7, and then how long it took to work out the major bugs, and finally then how long it took individual modders to update their code (and let me tell you, it wasn't easy. So much changed. When updating, my code was basically nothing but red error messages). But maybe that won't happen with 1.8; maybe updating will be simpler. And plus, this mod shouldn't be hard to update regardless, since not much will change with sound. =)
i think that for this mod, 1.7 is gonna be a extremely massive challenge, after all, the entire sound system was rewritten
What about supporting 1.5.2? 1.4.7? 1.2.5? Even earlier versions? When does it stop? 1.8 is a vast improvement over 1.6 in several regards. It's worth (and certainly much easier for everyone) to update your server for the performance optimizations alone, let alone the fact that (considering how easy it is to update 1.7.2 mods to 1.8) in a month or two into 1.8, the 1.6 version will be all but forgotten. The same people who begged mod authors not to update will be wondering why it takes so long to get past 1.7 (possibly the most mod-devastating update in Minecraft's history) and begging mod authors to hurry it up and update to 1.8.
Sorry if I get too emotional here, but I have a long list of mods I expect to install when 1.8 comes out (my last server version was 1.5.2, so there's a lot of new stuff to experience there, no doubt). There are only few mods on that list that haven't updated or aren't in the process of updating beyond 1.7 yet, and this mod is one of them. Considering that this "small" mod is easily in the top ten of my most desirable and most immersive mods for the game—a list that includes established behemoths like Biomes O'Plenty, Mo' Creatures, Optifine, etc—I really don't want some shortsighted detractors to convince Tmtravlr to divert his precious time on maintaining a version that for all intents and purposes will become obsolete in a few months at the most.
No modder in their right mind would try to recode their mod for every version of Minecraft to-date, I don't care how simple it is. I may love playing Hexxit, but I'll use BattleMusic's biome plugin before I go bothering Tmtravlr to backport Music Choices to 1.5.2. She has enough on her slate working out new features and trying to update Music Choices to 1.7.
Now then, as to 1.8, it will be fairly simple to update Music Choices to that version. Almost nothing has changed between 1.7.10 and 1.8 relative to the sound libraries, as far as I know. The biggest challenge will be updating a mod that has to do with rendering, such as GLSL Shaders and such.
And as to your comment of maintaining a mod for an "obsolete" version, that's really pointless to say. Most popular mods are still in the process of updating to 1.7.2, and the vast majority of mods exist for 1.6.4, even today. 1.6.4 is going to be the major modding hub for some time to come, not in the least because of the fact that Forge broke things when they decided to switch to gradle.
And your lunacy about asking for backports is hogwash, plain and simple. The mod was built in 1.6.4. It's not as though she made a mod for 1.7.2, and everyone bothered her to backport it. I asked her if she could make a mod for my 1.6.4 modpack, she did it, and has been expanding it ever since.
Now then, hopefully this sorts some things out for you, and you can calm down a bit about the fate of your favorite mods. Music Choices is in no danger of going extinct, and will be kept current so long as Tmtravlr has the patience to deal with updates.
would it be possible to try and make this mod override other mods that add main menu music, like the aether 2, for example?
Well, Aether 2 isn't updated yet, but when it does Music Choices should override the menu music, if you have installed any menu music yourself. If you don't have anything in the Menu folder, the Aether's menu music should play.
=/ Sorry to burst your bubble, but even after 1.8 comes out, it could be 6 months before forge updates, and even longer before most forge mods update. Just look at how long it took for them to update to 1.7, and then how long it took to work out the major bugs, and finally then how long it took individual modders to update their code...
Sounds like you joined the modding scene after 1.6 came out. As far as I know, updating to a newer version never was nearly as time-consuming as it was with 1.7 and updating to 1.8 won't take a fraction of the time it took us to update beyond 1.7.
The 1.7 patch (which was officially called "The Update that Changed the World") was unique in the fact that the vast changes in its code broke almost every single thing imaginable and we had to wait for first (buggy and barely functional) MCP and Forge updates for at least several months. It was highly irregular. To compare, working Forge builds for versions 1.6, 1.5, and 1.4 were all released at the same day or sooner (based on pre-release code) as official Minecraft updates. That's right, not even a few days or weeks after. The same day.
Unless soon-to-be-released 1.8 suddenly decides to change everything we know about it based on the latest snapshot, it doesn't seem at all that any of the dire expectations about 1.8 are true. Considering how easy it was to update from 1.7.2 to 1.7.10 (a lot of mods didn't even have to update their code to keep working), it's very reasonable to expect a working 1.8 Forge build within a few weeks at most (and probably much sooner than that), and many mod authors being able to update their 1.7.10 mods to 1.8 without almost no effort at all. As as I said, the 1.7 update was mostly an aberration, not a pattern.
No modder in their right mind would try to recode their mod for every version of Minecraft to-date, I don't care how simple it is. ... And your lunacy about asking for backports is hogwash, plain and simple.
I was obviously being sarcastic. The point is that there is a clear and continuous pattern with many of the users (most of them probably young, but still) on this forum, where they beg mod authors to stay from updating or keep up-to-day backports for older versions of the game, only to be first to start begging them to update as soon as they themselves switch to a newer version. Updating the client is at least 100 times faster and easier than updating the mod, so they may want to give mod authors some advance time in order to keep up with their personal needs. It's a reasonable view.
As for 1.6 staying viable for a long time, you're partly right, but the vast majority of more popular mods already have working 1.7.2+ builds, and if Tall Worlds beta will come out for 1.8 and its authors manage to make it compatible with Forge, no one will ever look at pre-1.8 versions because of the modding revolution it'll bring. That last one is a very big "IF", I know, but hey, let me dream about it a little bit
I track a lot of mods' progress myself, and although many small or older ones still haven't been updated past 1.6, there's almost no reason to care about them enough to stay away from updating, especially if you consider the quality and amount of content being developed for 1.7+ right now. Once again, the best analogy is to look at 1.4.7 and see how many users and mod authors still cling to that version and use the same arguments against updating to 1.5+ some people are trying to use with 1.7+.
(the answer: not a lot)
EDIT: Anyway, the last thing I want is to argue with you for the sake of arguing or somehow pressure someone into doing something they don't want to do. I did mentioned my desire for the mod to be updated to not-even-currently-released 1.8 (so, obviously, at the author's convenience) and some facts about 1.7's code changes and effects they had on the modding community, but as long as this discussion goes, I'd rather prefer to concentrate on something more productive than that.
Sounds like a very flexible approach to me, and probably not that difficult to implement, too. I actually forgot you can check for moonlight as well as sunlight, so I was thinking about altitude checks and other crazier ideas instead of keeping it simple and to the point.
I just noticed this post...how did I miss this? Anyhow, I personally used some more of C418's work in the End. From Minecraft-Volume Beta, I used "Ki" for survival and "Flake" for creative. From One, I used "imposter syndrome" and "swarms" for survival, and "cliffside hinson" and "danny makes chiptune" for creative. I also used "When you don't know what to do, just steal the amen break" from Life changing moments seem minor in pictures for the WitherBoss's theme.
They are still the defaults. If there are no music tracks that could apply to a certain situation, say for instance in a custom dimension, where you haven't added any music, then it will play that music instead.
If you want them to play with your custom music, you'll have to add them to the folders too. =)
Good to know, thanks for the explanation. I just hope you'll have no troubles updating to upcoming 1.8. I already spent hours on preparing music folders for the mod I don't even have installed on my 1.7.2 test version, heh-heh.
Yeah, well even updating to 1.7 might be difficult. As I've discovered while I'm trying to update another mod (Sound Filters), they changed the sound system and made a bunch of the variables private, so I can't use them anymore. It could take a while find a workaround and update.
I'll definitely focus on 1.6 (as 1.6 was the whole reason I created this mod, for different music in other dimensions). Don't worry about that. =)
I do want to update this to 1.7 though, so 1.7 users can have the other features.
Yep. Any update I make for 1.7 I would also make for 1.6, at least until 1.6 isn't used much anymore.
What about supporting 1.5.2? 1.4.7? 1.2.5? Even earlier versions? When does it stop? 1.8 is a vast improvement over 1.6 in several regards. It's worth (and certainly much easier for everyone) to update your server for the performance optimizations alone, let alone the fact that (considering how easy it is to update 1.7.2 mods to 1.8) in a month or two into 1.8, the 1.6 version will be all but forgotten. The same people who begged mod authors not to update will be wondering why it takes so long to get past 1.7 (possibly the most mod-devastating update in Minecraft's history) and begging mod authors to hurry it up and update to 1.8.
Sorry if I get too emotional here, but I have a long list of mods I expect to install when 1.8 comes out (my last server version was 1.5.2, so there's a lot of new stuff to experience there, no doubt). There are only few mods on that list that haven't updated or aren't in the process of updating beyond 1.7 yet, and this mod is one of them. Considering that this "small" mod is easily in the top ten of my most desirable and most immersive mods for the game—a list that includes established behemoths like Biomes O'Plenty, Mo' Creatures, Optifine, etc—I really don't want some shortsighted detractors to convince Tmtravlr to divert his precious time on maintaining a version that for all intents and purposes will become obsolete in a few months at the most.
Like I said above, I'm only going to support 1.6 until I feel it's obsolete, and only if porting the changes between versions is easy.
=/ Sorry to burst your bubble, but even after 1.8 comes out, it could be 6 months before forge updates, and even longer before most forge mods update. Just look at how long it took for them to update to 1.7, and then how long it took to work out the major bugs, and finally then how long it took individual modders to update their code (and let me tell you, it wasn't easy. So much changed. When updating, my code was basically nothing but red error messages). But maybe that won't happen with 1.8; maybe updating will be simpler. And plus, this mod shouldn't be hard to update regardless, since not much will change with sound. =)
i think that for this mod, 1.7 is gonna be a extremely massive challenge, after all, the entire sound system was rewritten
No modder in their right mind would try to recode their mod for every version of Minecraft to-date, I don't care how simple it is. I may love playing Hexxit, but I'll use BattleMusic's biome plugin before I go bothering Tmtravlr to backport Music Choices to 1.5.2. She has enough on her slate working out new features and trying to update Music Choices to 1.7.
Now then, as to 1.8, it will be fairly simple to update Music Choices to that version. Almost nothing has changed between 1.7.10 and 1.8 relative to the sound libraries, as far as I know. The biggest challenge will be updating a mod that has to do with rendering, such as GLSL Shaders and such.
And as to your comment of maintaining a mod for an "obsolete" version, that's really pointless to say. Most popular mods are still in the process of updating to 1.7.2, and the vast majority of mods exist for 1.6.4, even today. 1.6.4 is going to be the major modding hub for some time to come, not in the least because of the fact that Forge broke things when they decided to switch to gradle.
And your lunacy about asking for backports is hogwash, plain and simple. The mod was built in 1.6.4. It's not as though she made a mod for 1.7.2, and everyone bothered her to backport it. I asked her if she could make a mod for my 1.6.4 modpack, she did it, and has been expanding it ever since.
Now then, hopefully this sorts some things out for you, and you can calm down a bit about the fate of your favorite mods. Music Choices is in no danger of going extinct, and will be kept current so long as Tmtravlr has the patience to deal with updates.
Well, Aether 2 isn't updated yet, but when it does Music Choices should override the menu music, if you have installed any menu music yourself. If you don't have anything in the Menu folder, the Aether's menu music should play.
Sounds like you joined the modding scene after 1.6 came out. As far as I know, updating to a newer version never was nearly as time-consuming as it was with 1.7 and updating to 1.8 won't take a fraction of the time it took us to update beyond 1.7.
The 1.7 patch (which was officially called "The Update that Changed the World") was unique in the fact that the vast changes in its code broke almost every single thing imaginable and we had to wait for first (buggy and barely functional) MCP and Forge updates for at least several months. It was highly irregular. To compare, working Forge builds for versions 1.6, 1.5, and 1.4 were all released at the same day or sooner (based on pre-release code) as official Minecraft updates. That's right, not even a few days or weeks after. The same day.
Unless soon-to-be-released 1.8 suddenly decides to change everything we know about it based on the latest snapshot, it doesn't seem at all that any of the dire expectations about 1.8 are true. Considering how easy it was to update from 1.7.2 to 1.7.10 (a lot of mods didn't even have to update their code to keep working), it's very reasonable to expect a working 1.8 Forge build within a few weeks at most (and probably much sooner than that), and many mod authors being able to update their 1.7.10 mods to 1.8 without almost no effort at all. As as I said, the 1.7 update was mostly an aberration, not a pattern.
I was obviously being sarcastic. The point is that there is a clear and continuous pattern with many of the users (most of them probably young, but still) on this forum, where they beg mod authors to stay from updating or keep up-to-day backports for older versions of the game, only to be first to start begging them to update as soon as they themselves switch to a newer version. Updating the client is at least 100 times faster and easier than updating the mod, so they may want to give mod authors some advance time in order to keep up with their personal needs. It's a reasonable view.
As for 1.6 staying viable for a long time, you're partly right, but the vast majority of more popular mods already have working 1.7.2+ builds, and if Tall Worlds beta will come out for 1.8 and its authors manage to make it compatible with Forge, no one will ever look at pre-1.8 versions because of the modding revolution it'll bring. That last one is a very big "IF", I know, but hey, let me dream about it a little bit
I track a lot of mods' progress myself, and although many small or older ones still haven't been updated past 1.6, there's almost no reason to care about them enough to stay away from updating, especially if you consider the quality and amount of content being developed for 1.7+ right now. Once again, the best analogy is to look at 1.4.7 and see how many users and mod authors still cling to that version and use the same arguments against updating to 1.5+ some people are trying to use with 1.7+.
EDIT: Anyway, the last thing I want is to argue with you for the sake of arguing or somehow pressure someone into doing something they don't want to do. I did mentioned my desire for the mod to be updated to not-even-currently-released 1.8 (so, obviously, at the author's convenience) and some facts about 1.7's code changes and effects they had on the modding community, but as long as this discussion goes, I'd rather prefer to concentrate on something more productive than that.