auto-seeder bug when I play with a controller.

[pale fossil]

Reproduction Steps
I have trouble filling the auto-seeder when I play with my controller.
Steps to reproduce the bug:

• I add seeds to my inventory.
• I approach an auto-seeder.
• I press the action button to enter the auto-seeder menu.
• I fill the first auto-seeder correctly, and the cursor appears in my inventory.
• I proceed to the second auto-seeder.
• I press the action button to enter the menu of the second auto-seeder.
• My cursor appears at the bottom right instead of in my inventory.
• I have to move both joysticks randomly until the cursor positions itself in my inventory to fill the auto-seeder.
• After that, the same issue happens with all the other auto-seeders until the next day, when everything resets again.
  Repro Rate (How often does the issue occur?)
  Everytime or every second time I want to fill it with seeds.
  Game Platform
  Steam PC
  Game Version
  1.2b-1245
  Input Mode
  Controller
  Your save file
  Attachment (Save File & Additional Image/Video)

[wispy rivet]

heyas! the developers are gonna need a bit more information! Please follow the pinned post on bug reporting guidelines or check here! #1222877204233584722 message It has a template! Every bit of the information helps the developers out in fixing the issue! Please note that the use of mods or any type of file alteration will result in the developers not being able to assist you!

[pale fossil]

Your save file

[coral ingot]

Hello @pale fossil Thanks for bringing this to our attention

Could you please check the video in this thread https://discord.com/channels/623097219628662784/1447311395946496140 and let us know if it looks similar to the issue you experienced?
That would really help us confirm if it’s the same problem. Thanks!

[pale fossil]

Yes it's the same problema. I need to move the right joystick to put back the cursor where it belongs. Thank Ardian

[coral ingot]

Thanks for confirming — that helps a lot!

If you have some time, could you please try recording the issue and share it in that thread? It would be really helpful for the team to see exactly what’s happening.