💰 ZUI Bounty Program

Official Bug Bounty & Feature Development Program

Program Overview

The ZUI Bounty Program rewards community developers who contribute significant bug fixes and feature implementations to the ZUI project. This program demonstrates our commitment to collaborative development and recognizes the valuable contributions of skilled developers.

Program Objectives

• Quality Assurance - Incentivize critical bug fixes
• Feature Development - Encourage implementation of requested features
• Community Engagement - Foster collaborative development
• Code Excellence - Reward well-documented, maintainable contributions

🎯 Active Bounties

Bounty #001: Input Blocking Implementation

Amount: $10-20 USD (To be decided between bounty hunter and maintainer).
Type: Bug Fix
Priority: Major
Status: Open
Start Date: March 1, 2026
Deadline: September 1, 2026
_{I am attempting to fix this myself first. Please do not attempt any work on fixing this until at least the start date}

Problem Statement

Input blocking functionality does not currently work as intended. When users interact with ZUI panels, game inputs are not properly blocked, resulting in unintended interactions with the game world behind the UI interface.

Requirements for Award

To qualify for this bounty, submissions must meet the following criteria:

1. Pull Request Submission

   • Must be submitted to the official ZUI GitHub repository
   • Must target the appropriate branch as specified in contribution guidelines
   • Must include comprehensive commit messages

2. Technical Requirements

   • Fix must properly block all game inputs when the user is interacting with ZUI panels
   • Solution must handle both keyboard and mouse inputs
   • Implementation must not introduce performance degradation
   • Must be compatible with existing ZUI integrations

3. Code Quality Standards

   • Code must be well-documented with XML documentation comments
   • Must follow existing code style and conventions
   • Should include inline comments explaining complex logic
   • Must not introduce new bugs or break existing functionality

4. Testing & Validation

   • Must pass all existing automated tests
   • Must include testing methodology documentation
   • Should be tested with multiple mods and use cases
   • Must demonstrate proper input blocking and restoration

5. Documentation

   • Update relevant wiki pages if applicable
   • Include migration notes for breaking changes (if any)
   • Provide usage examples if new APIs are introduced

Submission Process

1. Fork the official ZUI repository
2. Create a feature branch: fix/input-blocking-#001
3. Implement your solution
4. Test thoroughly across multiple scenarios
5. Submit Pull Request with reference to Bounty #001
6. Participate in code review process

Award Distribution

Upon successful merge of the Pull Request and verification of functionality:

• Payment will be processed within 7 business days
• Payment method will be coordinated with the contributor
• Contributor will be publicly recognized in project documentation

🏆 Claimed Bounties

📋 Bounty Program Rules

Eligibility

• Open to all developers worldwide
• No prior contribution history required
• Multiple submissions per developer permitted
• Team submissions accepted (award will be split)

General Guidelines

1. One Bounty Per Issue

   • Each bounty is awarded to the first valid, merged solution
   • Partial solutions may be considered at maintainer discretion
   • Quality takes precedence over submission time

2. Code Ownership

   • All submitted code must be original work or properly licensed
   • Contributors retain copyright but grant project usage rights
   • Code must comply with project license (MIT/LGPLv3)

3. Review Process

   • All submissions undergo thorough code review
   • Maintainers may request changes or improvements
   • Contributor must be responsive during review period
   • Final acceptance decision rests with project maintainers

4. Award Payment

   • Awards paid via Cash App, Steam Giftcards, or negotiated between the Bounty Hunter and the Maintainer.
   • International contributors welcome (currency conversion at time of payment)
   • Tax compliance is responsibility of recipient
   • Payment requires valid contact information

5. Recognition

   • Contributors listed in project credits
   • Featured in release notes
   • Added to Hall of Fame (this page)
   • Optional social media recognition

Disqualification Criteria

The following will result in bounty disqualification:

• ❌ Plagiarized or stolen code
• ❌ Code that introduces security vulnerabilities
• ❌ Malicious or intentionally harmful implementations
• ❌ Violation of project code of conduct
• ❌ Failure to respond to review feedback within 30 days
• ❌ Submission after deadline without prior approval

🎖️ Hall of Fame

Top Contributors

💡 Proposing New Bounties

Community Suggestions

Community members may suggest issues for bounty consideration:

1. Identify the Issue

   • Must be a confirmed bug or approved feature request
   • Should have clear acceptance criteria
   • Must align with project goals

2. Assess Impact

   • Consider user impact and priority
   • Evaluate technical complexity
   • Determine appropriate reward level

3. Submit Proposal

   • Open an issue on GitHub with bounty-proposal label
   • Provide detailed description and justification
   • Suggest bounty amount (maintainers make final decision)

Bounty Funding

• Primary funding: Project maintainer (Zanakinz)
• Community sponsorship: Contact maintainer for co-funding opportunities
• Corporate sponsorship: Available for large features or critical fixes

📞 Contact & Support

Questions About Bounties

• GitHub Issues: Tag with bounty-question
• Discord: #bounty-program channel
• Email: Contact project maintainer directly

Before Starting Work

⚠️ Important: Before investing significant time:

1. Comment on the bounty issue to declare your intent
2. Confirm the bounty is still available
3. Ask clarifying questions about requirements
4. Discuss your proposed approach with maintainers

This prevents duplicate effort and ensures your solution aligns with project needs.

📊 Program Statistics

Last Updated: January 2026

🔄 Program Updates

Recent Changes

January 2026

• ✅ Bounty Program officially launched
• ✅ Bounty #001 posted: Input Blocking Implementation ($10-20)

Upcoming

• 📅 Additional bounties to be posted as needs arise
• 📅 Evaluation of community-suggested bounties
• 📅 Potential increase in award amounts for complex issues

📜 Legal & Payment Terms

Payment Terms

• Awards paid within 7 business days of PR merge
• Payment processed after verification of functionality
• Contributor must provide valid payment information
• International wire transfer fees may apply

Tax Information

• Recipients responsible for tax reporting in their jurisdiction
• 1099 forms issued for US contributors over $600/year
• International contributors advised to consult local tax laws

Liability

• ZUI project reserves right to modify or cancel bounties
• No guarantee of bounty award until PR is merged
• Project maintainers have final decision on all awards
• Disputes resolved at maintainer discretion

🚀 Get Started

Ready to claim a bounty?

1. Review Active Bounties
2. Read Bounty Program Rules
3. Check Contributing Guidelines
4. Fork the repository and start coding
5. Submit your Pull Request

Questions? Open an issue or join our Discord community.

Related Pages

• Known Bugs - Current issues and bug reports
• Contributing - General contribution guidelines
• API Reference - Complete API documentation
• Best Practices - Code quality standards