Solution: Commit -> Navigate to file on curseforge -> change version from Alpha to Release.
This is what I'm now doing. ;D It's infinitely better than messing around with zips. However there are still a few things I'd like to improve.
1) Skip the screen where I have to put in a message, or at least auto-fill the message. I certainly don't care about change logs, and I'm certain the end-users don't.
2) Automagically change the version # inside the .toc file. A lot of mods have the version number appearing somewhere within WoW, usually at the options screen or somewhere in a corner of their mod. How did they do this? I find it difficult to believe they do this by hand.
You don't. If you want every commit to be release, there is no point in using version control at all other than locally - you'd be better off uploading zips on CurseForge.
Oh really? Lets play 'what if'.
How to upload new versions to Curseforge.
Method 1: Right click on my addon folder, select 'commit'.
Method 2: Right click on my addon folder, click 'archive'. Set archive type to 'zip', type in a name, hit ok, wait. Open up Firefox, navigate to my project page. Click the file tab, click file management, click upload file. Type in a title that is supposed to be incrementing from the last title you typed in. Scroll down, type in a pointless (to me) message, scroll down some more, click 'upload file'. Navigate to your zip directory, find your recently created zip amongst the 700 other zips you have there. Select it, click ok, scroll to the bottom, click upload, and pray you don't get an error message because that means you have to do it all over again.
You're suggesting I use method 2, which is what I currently use and don't like it. I was told method 1 is doable with Subversion. Was I lied to?
Just put beta anywhere in the version string. Like: 1.0.9 beta
What do you call a 'version string'?
Here's what I've discovered. If I right-click my folder, tortoiseSvn->Commit (Which I assume is the correct way to upload a project), a new alpha file is created named rXX where XX is the version number (eg. r12)
If I right click, go to tortoiseSVN->tag/branch and in the 'to URL' line, change the last directory /trunk/ to /tag/Something, A beta file named 'Something' is created. I do not need to have 'b' or 'beta' anywhere in there.
If I right click, tortoiseSVN->tag/branch and in the 'to URL' line, change the last directory /trunk/ to /tag/Release or /tags/12345 (anything with all numbers), a Release file is created with the name Release or 12345
Does this sound right?
Here's my questions:
How do I make the default commit (the one where I dont have to go to branch/tag or see a URL box where I have to edit it each time) a Beta or Release?
2nd question: How do I bypass the part where I have to put in a message? I dont want to have to type anything, ever, and besides I don't know what I'm supposed to put there, and I keep getting commit failure Because I forgot to type something. I usually just mash the keyboard for a second (adfadf adsf a) and that seems to work.
3rd question: How do I make a release (or beta) that is automatically named vXX (or rXX) where XX is the version number?
I understand I have to edit a pgkfile or something like that, but..... /confused
Last question - how do I upload my mod as a beta? I read the documentation - vXX or Release makes it a Release version, and anything else is classified as alpha - but what about beta? I set the Curseforge repository to only accept Beta and release, but it didnt seem to like that.:o
I notice more and more addons seem to have nice little version numbers, both in-game somewhere, and somewhere on the curse page. eg. v1.6.3916 , or .r1234 in the filename, or something like that.
I tried doing that manually, but it was difficult to edit the .zip file, the curse title, and the .toc file for each version. Now that I have a dozen addons, Its almost impossible. I lose track. So now I just give everything the same title - whatever version of WoW it runs on. So I have a lot of MyAddon 3.1 files in my project. I want to do better.
Then someone mentioned something called Subversion. So I'm trying to get it set up, and I'm stuck. I have read all the forums and instruction manuals, and they're kind of generic. I don't need to know how Subversion completes its merging process or what the hooks folder is for. I need step-by-step instructions to get the bugger working.
Here's what I have done so far, step-by-step, as thoroughly as I dare.
1. Downloaded and installed Slik Subversion v1.6.1-win32, TortoiseSVN 188.8.131.5213 and a file it needed, gdiplus.dll.
2. Went to my curse project and clicked on the repository tab and set it to Subversion. It asked me to put in the name of My addon as it appears in the .toc file. The name as it appears in the .toc file is TooManyAddons, not Too-Many-Addons. So I changed that and hit ok and it gave me a bunch of URLs. Here's the public one: svn://svn.curseforge.net/wow/too-many-addons/mainline/trunk. Notice how it didn't use the name I specified. Instead it kept the hyphens.
3. I Tried to run TortoiseSVN. It popped up a message saying I have to do everything through the windows explorer. Fine, ok.
4. Went to my Addon in my wow/interface/addon directory and right clicked it and tried to 'create repository here'. It gave me an error saying it had to be empty. 'That's dumb' I though. I want to use my existing mod as it is, not create it anew or move it somewhere else. I need to use the folder /interface/addons/toomanyaddons.
5. I went back to the forums. I found this site http://kb.wowace.com/repositories/repository-faq/ and this site http://www.curseforge.com/home/repository-authorization/edit/. I follows the instructions and created a password. Still no help.
6. Went to my curse development URL, svn://email@example.com/wow/too-many-addons/mainline/trunk, and - finally - TortoiseSVN opened. There's an empty directory with one folder called trunk. I fiddled with it a bit. I created a new folder. I even managed to add a .txt file to it. Here's a screenshot. http://i212.photobucket.com/albums/cc100/dax006/Tortoisesvn-1.jpg
7. Now I tried adding a folder. I get an error about no message. Here's a screenshot. http://i212.photobucket.com/albums/cc100/dax006/precommitfail.jpg Again, dumb. How do I (assuming I ever get this working) add a folder without having to type in some message?
8. I tried again. I added a message ("This is a Message"). Now I get a new error, about setting some property to native. Again, a screenshot. http://i212.photobucket.com/albums/cc100/dax006/precommitfail1.jpg
9. I go to the forums again. Apparently I have to right-click on the folder In My Windows Explorer and set something, Before I try to add it. But I don't see any properties option. I again turn to the forums - apparently it's because I am using the win32 version of TortoiseSVN.
10. I give up and write this.
Is it supposed to be this complicated? I was envisioning opening up an app on my computer, clicking the folders I want to zip up and send to curse, setting a setting like 'auto-increment version numbers in the .toc file' and putting in my curse name and password and then clicking a big fat 'Update project' button. Instead I get errors, errors, error and no tutorials or instructions.