To Do List

[RobinHood70]

For wGC 1.1 release

• Finish putting recipes in (done: 904a635)
• Solve some GES problems outlined in To Do List #21 (comment) (done: 0fc2c96)
• Shorten combo boxes to fit inside client area (done: 64cdeaa)
• Implement "amp" specs by altering name only (e.g., 000004 use with mg000032 (growth))
  • Finish polishing names (initial version done: 3ce4083)
• Verify sorting of base gem list - sometimes 1B comes before 1A (a8f080c)
• Change parse button to parse to equations or parentheses (defaf9d)
  • Double button implemented (43f998c)
  • Backend method for 2nd button (already existed on Gem object)
• Add * at the end of the slots number, to mark combines that had needed to be condensed (done: ebdf6a1)
• Finish the help (42ff61f)
• Release v1.1

Consider for Future Versions

• Better alignment of variable gems names on main dropdown
• Have combines with ETA > 30mins (or something similar) show up only in DEBUG mode
• Allow combines to start with N base gems (all equal) for ease of folding more gems in one
• Advanced menu option that re-does current menus to allow combines, amps, and omnias (lots of coding involved)
• Auto-throttle based on ARGB/HSL of small rectangle/X points under cursor (wait for empty From on combine and non-empty To on Dupe)
• Mouse calibration for stretched or otherwise unusual window sizes (request click in 1A and 12C, then do calculations)
  • Bonus: allow for screwup of clicking in 1C and 12A (not hard, just use Abs math for most of it)
  • Super-insane bonus: if auto-throttle empty detection is ever implemented, only click in 1A (or even not at all) and use similar type of logic to detect where the slots are and how big they are
• Use empty buildings as extra slots (not as easy as it sounds, since we have to consider what we can Dupe to and what we can't, would also have to re-add Move option)

[CooLTanG]

The mouse calibrations for stretched windows should already be implemented.  Although doesn't account for people putting mouse cursor over gems in 1C instead of 1A
On Dec 11, 2015 12:13 PM, Robert Morley notifications@github.com wrote:To Do

Shorten combo boxes to fit inside client area
Implement "amp" specs by altering name only (e.g., 000004 use with mg000032 (growth))

Bonus: follow color/effect choice when linking to amp gem (e.g., use with oc000004 or lc000004)

Consider for Future Versions

Advanced menu option that re-does current menus to allow combines, amps, and omnias (lots of coding involved)
Auto-throttle based on ARGB/HSL of small rectangle/X points under cursor (wait for empty From on combine and non-empty To on Dupe)
Mouse calibration for stretched or otherwise unusual window sizes (request click in 1A and 12C, then do calculations)

Bonus: allow for screwup of clicking in 1C and 12A (not hard, just use Abs math for most of it)

—Reply to this email directly or view it on GitHub.

[12345ieee]

Survey for GES specces, if you have some data, please post there: http://steamcommunity.com/app/296490/discussions/0/487876568227032402/

[12345ieee]

Updated top post

[RobinHood70]

@CooLTanG: I’ve had it fail at least once using the Flash Projector, where it was clearly the slot positions that were the problem. I want to do more research to determine exactly when it fails, but the manual calibration would be for the edge cases like the one I encountered.

[CooLTanG]

Ah yes flash version would fail, steam one works
On Dec 11, 2015 2:51 PM, Robert Morley notifications@github.com wrote:@CooLTanG: I’ve had it fail at least once using the Flash Projector, where it was clearly the slot positions that were the problem. I want to do more research to determine exactly when it fails, but the manual calibration would be for the edge cases like the one I encountered.

—Reply to this email directly or view it on GitHub.

[12345ieee]

Updated top post

[RobinHood70]

Me too! :)

[12345ieee]

GES recipes status:

The first batch is in (1687e8f), the file format will be the same as any other spec.

gemforce internally finds them by setting damage of bbound and red to 0 and then going on normally. This grants the same results of an enhancement of x10 onward, and I liked it more than setting an arbitrary enhancement factor.
gemforce also forces the red to be added in a (b+r) gem, to allow folding of the hitfarming gem.

ISSUES THAT HAVE TO BE SOLVED:

1. The power is not the same of an ordinary killgem, even going with the same choice of gemforce will need us to change some values in the basegems. Same goes for all the derivatives of the base stats, but that should be automatically taken care of.

2. Every spec has a (b+r) subgem, but the player will put in A3 a br gem already made. Can we change (o+b) in x on the fly? And add some meaningful names for x?
   Clearly, we'll need an help page for GES things.

[BenjiIsNotAmused]

Hey guys, signed up here to let you know - when using latest release (1.0.8) and low delay (50) in a windowed fullscreen (windowed game, but maximised) the combiner acts erratic - resulting gems cost much more than their counterparts done when game window is either maximised and fullscreen OR when its windowed and with its default size. Oddly enough, raising delay to 250 seems to fix the issue
One more thing - have you guys considered using amps/towers/traps for recipes bigger than 36 as an external memory of sorts? Putting 6 by 3 amps in the game area would grant additional 18 slots for bigger recipes to run without forcing additional moves and thus elongating the process - Ive heard from Bilbo that the next release will squeeze 70 slot recipe into 36 slots, at the expense of recipe taking 2 hours to complete :P Using amps for extra slots could prevent that. I imagine you could configure them by selecting bottom right and top left amp to let the program know where youve put them, and how many of them there are. It would require some toying with translation from the build-in 36 slots to external slots, plus duped gems would still appear in the original slot area.
Just something to consider, if anybody can be arsed to code that.

[RobinHood70]

Hi BinjiIsNotAmused,

Using buildings as extra slots is on our list for future consideration (#21), but is a bit harder than it seems for the very reason you mention: duping gems is no longer straight-forward, and you have to make sure you leave base slots open to duplicate to, then move those gems into buildings before you need to duplicate something else.

We’re aware of the issues with 1.0.8 and have fixed most of them for 1.1, which should be out shortly. If the delay is the only issue you’re having, then you’re probably setting the delay too low. Steam, especially, requires fairly high delays once you’ve got a lot of things on screen, though even the web versions can require some fairly high delays themselves. For Steam, I’ve sometimes set it as high as 500ms as a precaution. That puts a lot of the really high-level gems out of reach, but when you get right down to it, the difference between a mid-level gem and a high-level gem isn’t all that large anyway. If you took a look at the link above, you’ll also see that an auto-throttle is on the list, which, if I can get it working, would pretty much eliminate the need for a delay and would ensure that the combiner goes as fast or slow as it needs to. I don’t know how viable that is, though.

From: BenjiIsNotAmused [mailto:notifications@github.com]
Sent: December 16, 2015 8:51 AM
To: gemforce-team/wGemCombiner wGemCombiner@noreply.github.com
Cc: Robert Morley robinhood70@live.ca
Subject: Re: [wGemCombiner] To Do List (#21)

Hey guys, signed up here to let you know - when using latest release (1.0.8) and low delay (50) in a windowed fullscreen (windowed game, but maximised) the combiner acts erratic - resulting gems cost much more than their counterparts done when game window is either maximised and fullscreen OR when its windowed and with its default size. Oddly enough, raising delay to 250 seems to fix the issue
One more thing - have you guys considered using amps/towers/traps for recipes bigger than 36 as an external memory of sorts? Putting 6 by 3 amps in the game area would grant additional 18 slots for bigger recipes to run without forcing additional moves and thus elongating the process - Ive heard from Bilbo that the next release will squeeze 70 slot recipe into 36 slots, at the expense of recipe taking 2 hours to complete :P Using amps for extra slots could prevent that. I imagine you could configure them by selecting bottom right and top left amp to let the program know where youve put them, and how many of them there are. It would require some toying with translation from the build-in 36 slots to external slots, plus duped gems would still appear in the original slot area.
Just something to consider, if anybody can be arsed to code that.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/21#issuecomment-165111190.

[RobinHood70]

Oops, just noticed now that I'm on the thread on the web, that I was actually replying to the very thing I linked to. :)

[12345ieee]

Not really a problem.
@RobinHood70 you were silent for several days, is everything alright?

[RobinHood70]

Yeah, just going through a bit of a bad spell. I've been watching replies, but had nothing to say to them, really. :)

[RobinHood70]

I added combo handling in the last commit. It's a bit rough, but the basic concepts are there. Not sure if this is the best approach or not, but it seems better than shuffling off different recipes to different locations. We can change if need be. Also need to deal with the fact that we have duplicate recipes deliberately now (e.g. "y").

[12345ieee]

I'll have a look.
Reach me in chat if you want to discuss.

On an unrelated topic, deleting the user's input just because they wrote "ob" seems a tad harsh.