Socketing a stack of gems into alchemist golem

[Lazlo]

[CHAT] selected I want to change your second gem. function: 096086E0 nil
26 frames in 1.032 seconds = 25.1938 FPS (32 keyframes)
25 frames in 1.008 seconds = 24.8016 FPS (30 keyframes)
addTmpValTable table: 09E862C0 all 2
addTmpVal table: 09E862C0 all 2 :=: 0 46
[LOG] AoE sockets golem (servant of AoE) with a #FFFFFF#10 #UID0#zircon#LAST#.

I selected a stack of ten gems when putting in a second gem for the golem. Imagine my surprise when it put in all ten. This does not seem to have had any effect beyond what putting in only one would do.

Sorry, this was version 21.

[Frumple]

Game version? I was under the impression this had been fixed in either 20b or 21.

[jenx]

This is still badly buggy in b21. I can't change my golems gems anymore, they are stuck on zircon and opal, and no matter what I do, I can't change it.

[jenx]

Further investigation shows that this is tied to the stacking of gems problem discussed above. A whole stack is placed in the first time. and then each refit, reduces the number in the slots by one.

I'm not sure what happens when you get to zero, as I don''t want to put another stack in!

[hops]

You can make it less buggy by changing the line

Code: Select all

local old = golem:removeObject(gems, gemid)

in data/chats/alchemist-golem.lua to

Code: Select all

local old = golem:removeObject(gems, gemid,  true)

Thus, you put in a stack, and can replace it with another stack.

[jenx]

I've done that. Do I need to recompile it somehow, or will it just work?

[jenx]

This is still hopelessly buggy. It makes playing an alchemist endlessly frustrating! I changed the code as you said, and then loaded what I thought was 1 of my 7 emeralds into the golem. But instead, all 7 went into the @!$#% golem.

Please, can this be fixed!

[hops]

This is still hopelessly buggy. It makes playing an alchemist endlessly frustrating! I changed the code as you said, and then loaded what I thought was 1 of my 7 emeralds into the golem. But instead, all 7 went into the @!$#% golem.

I said it only make it less buggy ...
Anyway now you can replace the stack with stack, and has apparently no risk of losing gems. This will not affect your alchemist imbuing gems and creating alchemist gems, which are the only two ways for an alchemist to utilize the gems imho.

[darkgod]

fixed