Treb consumed but no treb created

[Lynee]

When people are trying to set trebs simultaneously at the same spot only one gets created, the other disappears from backpack.
I remember this also happened to me with a catapult before. Don't recall any incidences with rams though.

To recreate the bug: start deploying trebs with 1 sec of difference on two chars. Only the first one gets created.

Suggested solution: only consume when area check (not too close to siege) doesn't fail

Screenshots:
1. starting to craft, my treb circled in my backpack
2. first treb is up, second is still in the making
3. craft fails and treb is consumed from my backpack (red circle)

[Lynee]

Correction: rams are afflicted too - if two deploy ram timers are running the first will produce the ram, the second will just consume the ram from the backpack without deploying.

[Karen]

Could you please include combat log in your screenshot?

[Lynee]

Screenshots with chat log included (for orientation boxed on the bottom one)

[Hotte]

I would like to second that regarding rams.
Steps to reproduce:

• 2 Players (A and B) standing at a Keep or Tower (doesn´t matter)
• Both players are standing close to each other
• Both players start to build a ram apparatus
• Both player start the siegecraft task to deploy the crafted ram at the (almost) same time
• Both players get the progress indicator for the deployment
• Let´s assume Player A is finishing first
  • Ram of Player A is deployed successfully.
• Player B is finishing the deployment task second
  • Player B gets error message, that only 1 ram is allowed
  • Player B lost his ram apparatus from inventory
  • Player B also doesn´t get the ingredients (wood/ metal) back (which makes sense because crafting the apparatus was successful)
  • Player B cannot try another location at the same or other keep/ tower because the ram is not in inventory anymore

Suggested fix:
The second player should stil have the ram apparatus in his inventory if the deployment fails for some reason

[Karen]

Did some changes in this area, please feedback here if you see any improvements/degrades.

[Lynee]

Tested with field ram and fiel treb and whatever was done fixed it - thanks for that
So this can be closed.

(Only thing that's new apart from is when you move siege they get some sort of proximity warning that they cannot be moved towards other siege weapons, however the move can be forced by using the move button repeatedly.)

[Karen]

Thank you for confirming, and pointing out the residual bug, it will be fixed by next reboot. Closing this.