I've just updated the HeroMachine 3 Alpha so any custom colors and swatches your character has will now be both saved and loaded. Old characters saved prior to this release will not be affected in any way.
If you have a bunch of custom colors active, then you load a previously saved character, your current custom colors won't be overwritten with white -- only non-white custom colors from the saved character get applied. In other words, your custom palette doesn't get wiped out by loading a save.
What that means is, you could in theory set up a whole suite of custom colors that you use a lot, and then save that "character" as something like "Jeff's Custom Colors". When you start a new session and character, the first thing you could do would be to load "Jeff's Custom Colors", and all the colors you'd saved would now be active. It's a way of saving your palette between sessions.
I also changed the default size for "Save as JPG/PNG" to 500x750.
The "Save" box now goes away when you click "OK".
Finally, I implemented a small bug fix where the custom color picker was showing on top of the save/load dialog box.
Please let me know if you have any problems with the release, and enjoy, all you custom color creators!
Ooh, now I can make my special purple queer tube!
@Spidercow2010: Thanks for the laugh. I almost snorted the coke I was drinking.
Great news!
@Jeff: In the future could you make that bigger? or have it so we could select a size? I’m not trying to be a pain, just trying to stop with the cut and paste, but that is getting me about 900×1300 or so right now….
Worf, yes, a dialog box where you can select different sizes for the “Save as JPG/PNG” feature is probably the next thing I will work on.
YIPPIE!!!!! (or however it is that you write that!)
YIPPEEEEE!!!! I use about 5 custom colors, and not only will I not have to rmemorize them or write them down, but neither will i have to enter them ALL before I load any one character! A life-saver!
Can we have a comb over hairstyle?
Olly, I’m not adding any more new items for the time being.
Shame
I find all the hair dont suit some things, butt ill make do
Great stuff Jeff. I have a selection of greens i like to use, now I will be able to keep them without typing them in everytime, most helpful!!
Fantastic news on you working on the jpg/png sizes next, that really has me stoked!! To be able to just click on the png button and have the choice to save it high quality is going to save me so much time! (And I will be able to use the shaded items too).
These are great updates Jeff.
Regards
Scorp
This will be quite helpful for saving characters with custom colors. But the color picker is still showing up over component picker box.
Also, could you make it so that when you select any custom color swatch you’ve saved, it shows you that color’s hex and RGB value, instead of the most recent one?
I’ve uploaded the most recent file again (the one that hides the custom color swatch); I think maybe you guys are getting the cached version that immediately preceded that one.
Alright! This is great news Jeff! Thank you!
Hey, Jeff, is there a set date for the release of HM3?
zaheelee: Nope, I’m not that organized. With the realization that I’m not going to have to completely rewrite the code, though, and instead have been able just to tweak it to get rid of the bugs, the hypothetical date got a lot, lot closer.
As a highschool level programmer myself, I can understand how relieved you must feel. Rewriting code sucks. Anyways, I wish you luck with the debugging process and I am looking forword to the release. Happy typing 🙂
I love the new updates Jeff thanks a ton! 🙂 But i have a quick question: Do you have any idea when the winner’s prizes will be posted?
The only outstanding confirmed contest prize left is PapaKrok’s “next item on the replacement prize list”, which I think is a tapered tail.
Are there some other ones I am unaware of? There ARE a ton of unclaimed prizes, though.
not that i can think of…when will the unclaimed ones be up for grabs?
Alright, it’s bug time again – this time it’s about when posts from the dropdown menus get stuck. This bug is fairly harmless and very rarely encountered in normal use, but there is an easy way to demonstrate it, might as well document it. Reproducing this bug requires kind of precise mouse cursor movement, as mousing over the wrong areas can defuse the process.
Swap til you drop 1
¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯
-Start hm3 clean (I’ve only tested with the version that’s live as of this writing).
-Open the Slot dropdown menu by clicking the arrow thing.
-Move the cursor straight down and click the ‘Background’ post.
-Move the cursor straight up and open the Slot dropdown menu again by clicking the arrow thing.
-Move the cursor straight down and click the ‘Backplane’ post.
-Move the cursor straight right until you’re mousing over the ‘Standard’ post in the Set dropdown menu.
-Move the cursor straight down until you clear the entire dropdown menu. The dropdown menu closes, but some graphics will remain on the screen.
This version of the bug is merely annoying since all functions are still available. The dedicated hero machinist can still finish the current drawing, save it, and restart. It has a big brother though…
Swap til you drop 2
¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯
-Start hm3 clean.
-Load Background-Standard.
-Open the Slot dropdown menu by clicking the arrow thing.
-Move the cursor straight down and click the ‘Belt’ post.
-Move the cursor straight up and open the Slot dropdown menu again by clicking the arrow thing.
-Move the cursor straight down and click the ‘Background’ post.
-Move the cursor straight right until you’re mousing over the ‘Standard’ post in the Set dropdown menu.
-Move the cursor straight down until you clear the entire dropdown menu. The dropdown menu closes, but will get broken.
If the Set dropdown menu is again opened, all buttons will be grayed out as usual and the menu cannot be closed. It would appear as though any unsaved changes are doomed, but the ‘Save Character’ button is actually still available by tabbing to it and pressing space (I can’t guarantee that tabbing works with all browsers).
In version 1, the problem appears to be that two dropdown menus are open at the same time. Vice versa in version 2, where I’m guessing the program tries to close a dropdown menu while there is none open. This is of course pure speculation.