Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
Tags
(1 edit)

there is a bug of bone addon.

you put a lv2 bare skull onto a lv2 bone skull. you got a lv3 bone skull, that's OK.

but if you put a lv2 bone skull onto a lv2 bare skull. you got a lv3 bare skull, I think it's a mistake.

(+1)

What would you suggest to do?

It feels a bit weird, that's true, and it does happen with stats too (when you merge, the one clicked first will have their stats ignored on levelup)

I guesss the idea would be that, if the unit clicked second has no item, the item of the first should be added onto it? But if it has something already, it shouldn't happen?

It feels strange, but it is consistent. If i did the process above, i should also do it with the stats to make it consistent. So the bigger life value and the bigger attack value between both will be chosen for the new merged unit.

Does that feel right? Or it's too confusing? For now it feels bad, but it's consistent and not confusing. That can be changed, of course

(3 edits) (+2)

That's right.

I think the sequence of 1st / 2nd clicked item should not effect the final unit.

which put player focus on the sequence is not that needed and is not shown anywhere.


--------

And, If both items have addon.

I think you can keep the one of the target, which is current logic.

and you can give a hint on the (target) to show that addon is to be kept. (like an green outline of the addon or something) , also a small drop out anim on the dragging unit's addon may be good

I agree that you should probably just leave it as it is. There's also the issue of what to do if both sub-units have different items, and the more intuitive way to deal with that is through the existing system.