Arcane-Backend-V4

A Universal Backend For Old Builds Of Fortnite Aiming To Be 1:1!

Fully Supported Builds:

[ 1.7.2 - 3.1 ]

Build Specific Issues:

Season 1:

• 1.7.2 - 1.10 | Cannot connect to xmpp and cannot use matchmaker

Season 2:

• 1.11 - 2.5 | Cannot connect to xmpp and cannot use matchmaker

Season 3:

• 3.0 - 3.1 | Cannot connect to xmpp and cannot use matchmaker

Project Stack: (Will Most Likely Change)

• Language: Typescript

Features:

• Login system
• Easy setup
• Database (MongoDB)
• Cloudstorage
• Auto shop (purchasing skins and items)
• Full Battle Pass integration
• Challenges system (daily and weekly challenges)
• Friends system (add/remove/block friends)
• XMPP
• Working MCP (10%)
• NewsV1 (Fortnite in-game news system)
• NewsV2 (Fortnite in-game news system)
• Discord Bot Integration
• Matchmaker (matchmaking system)
• Party V1 (basic party system)
• Party V2 (advanced party system with cross-play)
• Daily rewards system (login rewards)
• Gifting system (send gifts to friends)
• Purchasing from item shop
• HWID Bans (hardware bans)
• Refunding system
• Frontend for managing backend
• Universal backend (multi-version support)
• API for external integrations
• Player inventory management
• Seasonal events (Christmas, Halloween)
• Player stats tracking
• WebSockets for real-time communication
• IP Bans (ban based on IP address)
• Private lobbies for custom games
• Cross-platform matchmaking
• Competitive matchmaking and leaderboards
• Tournament support
• Save The World

Bot Commands (NOTE: BOT IS DEPRECATED!)

• Register command (for creating new accounts)
• Ping command (for checking bot responsiveness)
• User lookup command (check user stats and profile)
• Ban management command (ban/unban users)
• Announcements command (send announcements to users)

Contributing Guide

All Contributions Are Reviewed!

We welcome contributions but ask that you follow these guidelines:

1. No Stolen Code ('Skidding'): Ensure that all contributions are original. We do not accept code taken from other projects (e.g., LawinserverV2).

2. Focus on Incremental Changes: As this is also a learning project, we ask that you avoid making overly complex or significant changes that are beyond the current level of understanding. Smaller, meaningful changes are appreciated!

3. Avoid Deleting Core Code: Please refrain from removing large portions of the existing codebase. Certain sections may be integral to the backend’s functionality, and deleting them could break core features.

Tips for Contributing:

• Create a New Branch: Always create a new branch for your contributions (e.g., feature/[feature-name]).
• Submit Small Changes: Small bug fixes, documentation improvements, and new features are highly encouraged.
• Respect the Learning Process: Keep changes manageable and easy to review to help keep the project maintainable.

Thank you for contributing to the project!