Added better downloading system which allows for that progress bar
Added progress bar.
Renamed to Texture Packs + because I'm planning on adding a few of the features I listed in my last post here.
Made downloading a thread, it used to freeze your game but now it doesn't. I still need to put a few other things in a thread, like checking stuff online because if you check, say, a website that's down and won't load, it will never unfreeze. :I
Info!
Quite recently, I have gotten an interest in modding, so this is something I've been working on for the past few days!
It is a Texture Pack Updater mod. View latest post by me in thread for updates, I suppose. :smile.gif:
How it works!
The texture pack creator, or yourself, includes a little "version.txt" file inside of the texture pack Zip file.
In that version.txt file, you add two little lines that help the mod do what it does. The first line states the current version of the downloaded texture pack, and the second line provides a link to a direct text file, (as in, not media fire or any other uploading service that requires you to click a button to download the file) which has the has on the first line the newest version of the texture pack, and the second line has a direct (once again, not like mediafire) link to the most up-to-date texture pack.
Version.txt example:
In this example, the version.txt is provided inside the Zip file, and has a link to the information for the newest version uploaded online, the mytext.txt file.
When minecraft is started up, it analyzes these files and compares the version numbers to figure out whether or not it is up-to-date or not. If it is not, you select the texture pack on the texture pack menu and hit the "Update texture pack" button, which then downloads the file linked to in mytext.txt, and applies it!
Sorry for the huge wall of text, here's a summed up version:
1. Add a version.txt file in your pack Zip folder that has the version and the update text URL.
2. Upload an update text file which has the newest version number and the URL for the newest texture pack.
3. The game compares the versions and tells the user if it is outdated or not.
4. If so, user presses update button and it downloads the zip and applies it!
Pictures!
Please note that the descriptions on those texture packs are from the pack.txt file, and the descriptions for texture packs are NOT modified by this mod.
Current progress!
It is working! You are able to check if your packs are outdated or not AND you are able to update them! I might get a few people to test out the mod and such if I can fix some things. But, there are a few bugs and the fact that I can't get it to work when I inject the class files into an unmodded minecraft.jar! Which brings me to the next section...
I need help!
When I run recompile.bat on MCP, I am able to run the client and everything via runclient.bat, BUT, when I put the class files from reobf.bat into an unmodded minecraft.jar inside of the appdata folder, and I launch the game from Minecraft.exe downloaded from online, I press "update texture pack", and nothing happens! It doesn't update anything! I don't get it. Does anybody have any idea how to fix this? If I cant fix it, this mod will never be released to the public!
Lastly, I am open to suggestions, in fact, I WANT them!
Please, PLEASE suggest any thing for the mod! How it works, how to make it easier to use, added functions for the user, anything! I want to make this mod great.
So please, post your thoughts and suggestions here! Thanks!
Do you think you could make it able to update mods too?
No, definitively not. Mods run on class files injected into the minecraft.jar file, which as far as I know cannot be modified when the game is running, and would be far to advance for me.
Actually, it could be possible to update mod zip files that are in the mods/ directory, but I don't know.
I hate to bump this, but I still need help regarding injecting the class files. PLEASE if you can provide help regarding this tell me!
Also I'd like some suggestions too.
This is officially updated to 1.8.1, and I've also made a few changes. :biggrin.gif:
Changes include:
Working changelog system
Fixed overlapping with second description line, I forgot you can have two lines for that.
Pictures:
(Using Coterie Craft as an example, it's a great pack though. Go check it out :tongue.gif: )
Planned features:
If a lot of these features come to be, I might change the name to "Texture Packs Plus Mod" or something along the name of that.
Info page for texture pack (Instead of the update button, an info button that shows info about the texture pack. Version, changelog, info, previews.)
The preview part might include the ability to cycle through all the blocks in the game to preview their looks.
Of course, there could be a lot more also. Keep in mind this is not the final version, or my final list of ideas!
[ Insert your suggestion here ]
Seriously, I want suggestions! :biggrin.gif:
I'm serious.
SUGGESTIONS. NOW.
There's quite a few bugs still, one major one being with the new "Yes/No" gui feature it doesn't seem to update the pack. The second major one being after injecting the class files it doesn't work on native Minecraft. Don't worry, I'm sure I'll get them ironed out. Hopefully. please help me
Added better downloading system which allows for that progress bar
Added progress bar.
Renamed to Texture Packs + because I'm planning on adding a few of the features I listed in my last post here.
Made downloading a thread, it used to freeze your game but now it doesn't. I still need to put a few other things in a thread, like checking stuff online because if you check, say, a website that's down and won't load, it will never unfreeze. :I
Hey, this is a pretty good idea. But it falls apart when the texture pack author makes a mistake. What if the author uploads a wrong or corrupted version of his pack? There should be a 'revert to previous version' option for that. That does mean that you eventually end up with two versions of every updated texture pack, but that shouldn't be that big of a problem, right?
For that matter, what happens if the update is something other than a .zip file? Someone might get the idea to redistribute someone else's texture pack with a modified version.txt which then downloads a malicious file to your computer when you want to update it. Automatically downloading a file from a source unknown to the player is extremely, extremely risky. You better have some security measures in place to prevent abuse.
Also, I don't know if many texture pack authors are prepared to put there texture packs on direct download links that anyone can just pull from the version.txt. Have you considered simply making the update button redirect to the appropriate hosting site, where the player downloads the new version himself? It'd be a lot safer than automatic downloading, although I'm not sure if your method of determining whether a pack is outdated will still work that way.
Hey, this is a pretty good idea. But it falls apart when the texture pack author makes a mistake. What if the author uploads a wrong or corrupted version of his pack? There should be a 'revert to previous version' option for that. That does mean that you eventually end up with two versions of every updated texture pack, but that shouldn't be that big of a problem, right?
For that matter, what happens if the update is something other than a .zip file? Someone might get the idea to redistribute someone else's texture pack with a modified version.txt which then downloads a malicious file to your computer when you want to update it. Automatically downloading a file from a source unknown to the player is extremely, extremely risky. You better have some security measures in place to prevent abuse.
Also, I don't know if many texture pack authors are prepared to put there texture packs on direct download links that anyone can just pull from the version.txt. Have you considered simply making the update button redirect to the appropriate hosting site, where the player downloads the new version himself? It'd be a lot safer than automatic downloading, although I'm not sure if your method of determining whether a pack is outdated will still work that way.
There are many measures put in place to make sure nothing malicious is downloaded. It must be a zip that is downloaded. It also makes sure all the links are valid and are .txt files, nothing else. It is literally impossible to download anything other than a zip with this. If the zip contains a malicious exe per say, the said exe would not under any circumstances be automatically ran. It's like downloading a texture pack regularly, if the zip contains an exe, report it to the appropriate moderator on the forums.
Second of all, if the texture pack creator messes up a release, all he has to do is upload a new zip for the user to download. If he messes up the .txt in the texture pack's zip, that's his fault. He needs to get his things together. I cannot prevent people from making mistakes. I can only try to be clear enough so they don't make them. I might add a button that will open up the user's browser to the texture pack's thread, in case the creator messed up the release, the user can manually re-download it. If the creator royally messes up the release, to the point where none of the information about the texture pack is correct, then that's his fault.
If the update button just redirects to a website to download the zip, it pretty much gets rid of the whole idea of an in game texture pack updater. The point is so that the user can very easily install/update his texture packs without having to go to an external website and open up his texture pack folder just to update his texture pack.
I could add a backups folder and can add a "revert to previous version" button on the info menu when that is implemented. That is very possible.
Also, if you saw the pictures of the change log, that has been removed temporarily until I can find out a way to do it better. The way I was doing it was absolutely silly and redonkulous.
Okay, good to hear you've got the security part covered. Although I do think having a texture pack updater that opens a web browser isn't entirely useless. For me, the most useful feature of this mod would be to know when a texture pack update is available, without needing to go to every mod's individual forum page or otherwise. Besides, allowing texture pack updates to open web browsers would allow you to support texture packs with customizers as well, such as Painterly.
It is a Texture Pack Updater mod.
View latest post by me in thread for updates, I suppose. :smile.gif:
In that version.txt file, you add two little lines that help the mod do what it does. The first line states the current version of the downloaded texture pack, and the second line provides a link to a direct text file, (as in, not media fire or any other uploading service that requires you to click a button to download the file) which has the has on the first line the newest version of the texture pack, and the second line has a direct (once again, not like mediafire) link to the most up-to-date texture pack.
Version.txt example:
Mytext.txt file example:
In this example, the version.txt is provided inside the Zip file, and has a link to the information for the newest version uploaded online, the mytext.txt file.
When minecraft is started up, it analyzes these files and compares the version numbers to figure out whether or not it is up-to-date or not. If it is not, you select the texture pack on the texture pack menu and hit the "Update texture pack" button, which then downloads the file linked to in mytext.txt, and applies it!
Sorry for the huge wall of text, here's a summed up version:
1. Add a version.txt file in your pack Zip folder that has the version and the update text URL.
2. Upload an update text file which has the newest version number and the URL for the newest texture pack.
3. The game compares the versions and tells the user if it is outdated or not.
4. If so, user presses update button and it downloads the zip and applies it!
Please note that the descriptions on those texture packs are from the pack.txt file, and the descriptions for texture packs are NOT modified by this mod.
But, there are a few bugs and the fact that I can't get it to work when I inject the class files into an unmodded minecraft.jar! Which brings me to the next section...
So please, post your thoughts and suggestions here! Thanks!
<3
Thank you! :ohmy.gif:
Awww, thanks. <3
No, definitively not. Mods run on class files injected into the minecraft.jar file, which as far as I know cannot be modified when the game is running, and would be far to advance for me.
Actually, it could be possible to update mod zip files that are in the mods/ directory, but I don't know.
Really awesome <3
Also I'd like some suggestions too.
Changes include:
(Using Coterie Craft as an example, it's a great pack though. Go check it out :tongue.gif: )
Planned features:
please help me
When I, in fact, added Herobrine in v2.1! :laugh.gif:
For that matter, what happens if the update is something other than a .zip file? Someone might get the idea to redistribute someone else's texture pack with a modified version.txt which then downloads a malicious file to your computer when you want to update it. Automatically downloading a file from a source unknown to the player is extremely, extremely risky. You better have some security measures in place to prevent abuse.
Also, I don't know if many texture pack authors are prepared to put there texture packs on direct download links that anyone can just pull from the version.txt. Have you considered simply making the update button redirect to the appropriate hosting site, where the player downloads the new version himself? It'd be a lot safer than automatic downloading, although I'm not sure if your method of determining whether a pack is outdated will still work that way.
There are many measures put in place to make sure nothing malicious is downloaded. It must be a zip that is downloaded. It also makes sure all the links are valid and are .txt files, nothing else. It is literally impossible to download anything other than a zip with this. If the zip contains a malicious exe per say, the said exe would not under any circumstances be automatically ran. It's like downloading a texture pack regularly, if the zip contains an exe, report it to the appropriate moderator on the forums.
Second of all, if the texture pack creator messes up a release, all he has to do is upload a new zip for the user to download. If he messes up the .txt in the texture pack's zip, that's his fault. He needs to get his things together. I cannot prevent people from making mistakes. I can only try to be clear enough so they don't make them. I might add a button that will open up the user's browser to the texture pack's thread, in case the creator messed up the release, the user can manually re-download it. If the creator royally messes up the release, to the point where none of the information about the texture pack is correct, then that's his fault.
If the update button just redirects to a website to download the zip, it pretty much gets rid of the whole idea of an in game texture pack updater. The point is so that the user can very easily install/update his texture packs without having to go to an external website and open up his texture pack folder just to update his texture pack.
I could add a backups folder and can add a "revert to previous version" button on the info menu when that is implemented. That is very possible.
Also, if you saw the pictures of the change log, that has been removed temporarily until I can find out a way to do it better. The way I was doing it was absolutely silly and redonkulous.
Thanks man! I'm having some issues currently but I'm trying to get them fixed.