Unreal Sample for PGS

[RKS13D]

The unreal/ directory contains sample demonstrating how to use Online Subsystem Google Play for implementing features like

Google Play Games Authentication
Google Play Games Achievements
Google Play Billing for in-app purchases using Google IAP

[gemini-code-assist]

Summary of Changes

Hello @RKS13D, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request introduces a comprehensive Unreal Engine sample project, 'ShooterGame,' designed to showcase the integration of Google Play Services. The sample provides practical demonstrations of Google Play Games authentication, achievements, and in-app billing, with core functionalities implemented in C++ where necessary. This addition expands the games-samples repository to include Unreal Engine, offering developers a valuable resource for incorporating Google Play features into their Unreal projects.

Highlights

• New Unreal Engine Sample: Introduced a new Unreal Engine sample project, 'ShooterGame', demonstrating Google Play Services integration.
• Google Play Services Features: The sample showcases Google Play Games Authentication, Achievements, and Billing, with C++ implementations for certain features.
• Extensive Project Configuration: Added comprehensive Unreal Engine project configurations, including Git LFS tracking, .gitignore rules, and various .ini files for editor, engine, game, and input settings.
• Android Integration: Enabled Google Play support and in-app purchasing within the Android runtime settings, along with necessary Android permissions.
• New Game Assets: Included a large collection of Unreal asset files (.uasset, .umap) for animations, blueprints, characters, levels, materials, and weapons to build out the 'ShooterGame' sample.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request introduces a new Unreal Engine sample project demonstrating Google Play Games services integration. The overall structure is good, but there are several issues ranging from minor inconsistencies in configuration files to critical bugs in the C++ code that could lead to crashes. I've identified a critical memory issue related to dangling pointers in the UI code, unsafe map access, and some security and maintainability concerns with hardcoded values and placeholder names in configuration files. Additionally, there's a minor documentation error in the README.