Commerce bots to C# after changing the API platform

We are looking for an experienced Unity developer to help complete the game development. About the game: Genre: farm simulator. The game is already being developed in Unity. Initially, it was created for mobile devices, but later it was decided to release it for Steam (PC). What needs to be done: Finish the game according to the completed technical specification. Adapt the existing functionality for PC and Steam. Implement the already planned mechanics and interface. What we provide: Detailed technical specification. All necessary materials (models, graphics, objects, etc.). Photos, videos, screenshots, and recordings of the original game. A ready implementation plan. We are recreating a game that successfully operated over 10 years ago, so there is no need to invent or design from scratch. All mechanics, interface, and logic are already defined — they need to be implemented in Unity with quality. For project familiarization, we provide a link to one of the game video reviews: Insert link here. Requirements: Experience working with Unity. Experience in developing or adapting games for PC/Steam will be an advantage. Ability to work according to the provided technical specification. In your response, please indicate: examples of your work; experience working with Unity; estimated hourly rate or cost of execution. One of the video reviews: https://www.youtube.com/watch?v=5_wKoX7zRc0

An independent service handler for Excel files is required for the existing microservices system. The task involves creating a reliable pipeline for receiving, validating, and transforming data from tables into a structured database format. Functional tasks: Development of an API based on gRPC for receiving processing commands and returning execution statuses. Implementation of file parsing logic: reading large volumes of data (XLSX), cleaning, type checking, and mapping to business models. Implementation of a data access layer (Repository/Unit of Work) for saving results in PostgreSQL via Entity Framework Core. Ensuring thread safety and efficient resource usage (especially when processing large files). Technical requirements: Platform: .NET 10. Architectural patterns: Dependency Injection, CQRS, modular project architecture. Communication: Strictly gRPC. Working with Excel: Use of efficient libraries (e.g., EPPlus, OpenXML, or similar of your choice). Modularity: Code should be organized so that the service is easily scalable and testable. Expected results: A fully functional microservice ready for deployment in a containerized environment. A clean codebase adhering to SOLID principles. Documented .proto files. Basic unit tests for critical data processing nodes. Candidate requirements: In your response, please specify: Your experience with .NET in microservices architecture. Examples of how you organize DI and modularity in your projects. Experience with Excel libraries in .NET. Willingness to work with gRPC contracts.

Configuration: 1C UT 11 Address warehouse Zebra TC26 TSD Work via RDP Product scanning is performed in receiving, placement, picking documents, and other warehouse operations. Current problem: Warehouse workers operate through the Zebra TSD. When scanning, they do not always notice messages on the screen. It is necessary to implement different sound signals for different scanning results. Required functionality: Successful scanning and processing in 1C short sound signal. Barcode read by the scanner, but the product is not found in 1C another sound signal (different from successful). Error during warehouse operation incorrect cell; incorrect product; other address warehouse control errors. separate sound signal. Sounds should be played on the TSD via RDP. Preferences: use of WAV files or another reliable playback method; ability to add new types of sound messages in the future; minimal impact on the speed of TSD operation. Please specify in your response: Experience with UT 11 and address warehouses. Have you implemented similar tasks for Zebra TSD or other TSDs. Estimated cost and execution time. How the implementation of sound signals is planned.