Skip to content

Support

Need help with JiETNG? This page will help you find the assistance you need.

Getting Help

📖 Documentation

Start with our comprehensive documentation:

🔍 Search First

Use the search function (⌘K or Ctrl+K) to quickly find answers in our documentation.

Report Issues

🐛 Bug Reports

Found a bug? Please report it on GitHub:

Create Bug Report →

Please include:

  • 📝 Description of the issue
  • 🔄 Steps to reproduce
  • 📱 Platform
  • 🌐 Language setting

💡 Feature Requests

Have an idea for a new feature?

Submit Feature Request →

Please include:

  • 📋 Detailed description
  • 🎯 Use case / benefit
  • 🖼️ Mock-ups (if applicable)

Community Support

💬 Discord Server

Join our Discord community:

  • Ask questions
  • Share tips and tricks
  • Connect with other users
  • Get announcements

Join Discord →

📱 LINE

Contact through the bot:

Send "help" or "support" for quick assistance.

Frequently Asked Questions

Before asking, check if your question is answered in the FAQ.

Common topics:

  • Account binding issues
  • Score sync problems
  • Command usage
  • Feature availability

Response Times

Support ChannelExpected Response
DocumentationImmediate (self-service)
GitHub Issues1-3 business days
DiscordCommunity-driven (varies)
Direct MessageBest effort

Priority Support

Critical bugs and security issues are prioritized. Please mark them appropriately.

Contributing

Want to help improve JiETNG?

📝 Improve Documentation

  • Fix typos and errors
  • Add examples
  • Clarify confusing sections
  • Translate to other languages

Edit on GitHub →

🌐 Translations

Help translate documentation:

  • Japanese improvements
  • Chinese improvements
  • Other languages

🧪 Beta Testing

Join our beta testing program:

  • Test new features early
  • Provide feedback
  • Report bugs before release

Contact via GitHub to join.

Bug Bounty Program

While we don't offer monetary rewards, we acknowledge contributors:

  • 🏆 Hall of Fame listing
  • 🎖️ Special role in Discord
  • 📝 Mentioned in release notes

Eligible Issues

  • Security vulnerabilities (highest priority)
  • Critical bugs affecting many users
  • Performance issues
  • Data integrity problems

Development Support

🔧 Technical Questions

For developers:

  • API usage questions
  • Integration issues
  • Technical discussions

Discussions →

📚 API Documentation

Coming soon - detailed API documentation for advanced users.

Support Development

Support development:

💝 Financial Support

Japan: Liberapay

China: 爱发电

International: GitHub Sponsors

🌟 Non-Financial Support

  • ⭐ Star the project on GitHub
  • 📢 Share with friends
  • 📝 Write tutorials or blog posts
  • 🎨 Create fan art or promotional materials

Contact Information

Primary Channels

Developer

Response Policy

  • Security issues: Within 24 hours
  • Critical bugs: 1-3 business days
  • Feature requests: Reviewed weekly
  • General questions: Best effort basis

Security Vulnerabilities

For security issues, please contact privately first via GitHub Security Advisory rather than public issues.

Guidelines

When seeking support:

✅ Do

  • Search existing issues first
  • Provide detailed information
  • Be patient and respectful
  • Follow up if requested
  • Mark issues as resolved when fixed

❌ Don't

  • Spam multiple channels
  • Demand immediate responses
  • Share private account credentials
  • Post off-topic content
  • Be rude or disrespectful

Service Status

Check current system status:

  • Bot Status: Usually displayed in bot profile
  • API Status: Check GitHub for announcements
  • Maintenance: Announced in Discord and GitHub

Known Issues

Current known issues are tracked on: GitHub Issues

For legal or privacy concerns:


Making every play count