Guidelines

Code Style

• GDScript: Follow GDScript style guide
• Java: Follow Google Java style guide
• Kotlin: Follow Android Kotlin style guide
• Objective-C: Follow Google Objective-C style guide
• Swift: Follow Swift style guide

Commit Messages

Use conventional commits format:

type(scope): subject

body

footer

Types: feat, fix, docs, style, refactor, test, chore

Examples:

feat(android): add support for native ads
fix(ios): resolve banner positioning issue
docs: update installation instructions

Pull Request Process

1. Fork the repository
2. Create a feature branch (git checkout -b feature/amazing-feature)
3. Make your changes
4. Test on both platforms
5. Commit with descriptive messages
6. Push to your fork
7. Open a Pull Request with:
8. Clear description of changes
9. Related issue numbers
10. Testing performed
11. Screenshots (if UI changes)

Reporting Issues

Include: - Plugin version - Godot version - Platform (Android/iOS) - Device/OS version - Steps to reproduce - Expected vs actual behavior - Relevant logs

Additional Resources

• Godot Engine Documentation
• Android Developer Documentation
• iOS Developer Documentation
• Gradle Documentation