2vb/snow
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Performance first, universal Fortnite private server backend written in Go.
165 Commits 1 Branch 0 Tags 1.4 MiB
Go 95.7%
HTML 3.3%
JavaScript 0.8%
Dockerfile 0.2%
3fcda14f1a
Go to file
Eccentric 3fcda14f1a Rework automatic storefront!
2024-02-18 00:09:02 +00:00
aid Rework automatic storefront! 2024-02-18 00:09:02 +00:00
discord Refactor external data to improve startup time 2024-02-11 00:27:08 +00:00
fortnite Rework automatic storefront! 2024-02-18 00:09:02 +00:00
handlers Rework automatic storefront! 2024-02-18 00:09:02 +00:00
person Request to join now works 2024-02-17 14:40:17 +00:00
socket Rework automatic storefront! 2024-02-18 00:09:02 +00:00
storage Start on tcp xmpp for seasons 2 <= 2024-02-16 01:14:14 +00:00
.air.toml Improve Display Asset accuracy 2023-12-10 23:54:31 +00:00
.gitignore Continue to research how fortnite storefront works. 2023-11-26 22:39:05 +00:00
default.config.ini Rework automatic storefront! 2024-02-18 00:09:02 +00:00
go.mod Start on tcp xmpp for seasons 2 <= 2024-02-16 01:14:14 +00:00
go.sum Update to go1.22.0 2024-02-10 01:55:47 +00:00
main_test.go Add permissions test 2024-02-09 23:56:06 +00:00
main.go Rework automatic storefront! 2024-02-18 00:09:02 +00:00
makefile Better 2024-02-10 00:34:12 +00:00
readme.md Rework automatic storefront! 2024-02-18 00:09:02 +00:00

readme.md

1

Snow

Performance first, feature-rich universal Fortnite private server backend written in Go.

Overview

  • Single File It will embed all of the external files inside of one executable! This allows the backend to be ran anywhere with no setup (after initial config)!
  • Blazingly Fast Written in Go and built upon Fast HTTP, it is extremely fast and can handle any profile action in milliseconds with its caching system.
  • Automatic Profile Changes Automatically keeps track of profile changes exactly so any external changes are displayed in-game on the next action.
  • Universal Database It is possible to add new database types to satisfy your needs. Currently, it only supports postgresql.

What's up next?

  • Purchasing the Battle Pass. This will require the Battle Pass Storefront ID for every build. I am yet to think of a solution for this.
  • Interaction with a Game Server to handle Event Tracking for player statistics and challenges. This will be a very large task as a new specialised game server will need to be created.
  • After the game server addition, a Matchmaking System will be added to match players together for a game. It will use a bin packing algorithm to ensure that games are filled as much as possible.

And once battle royale is completed ...

  • Save The World

Feature List

  • XMPP For interacting with friends, parties and gifting.
  • Friends On every build, this will allow for adding, removing and blocking friends.
  • Party System V2 This replaces the legacy xmpp driven party system.
  • Automatic Item Shop Will automatically update the item shop for the day, for all builds.
  • Gifting Of any item shop entry to any friend.
  • Locker Loadouts On seasons 12 onwards, this allows for the saving and loading of multiple locker presets.
  • Item Refunding Of previous shop purchases, will use a refund ticket if refunded in time.
  • Client Settings Storage Uses amazon buckets to store client settings.
  • Support A Creator 5% Use any display name and each purchase will give them 5% of the vbucks spent.
  • Discord Bot Very useful to control players, their inventory and their settings

Supported MCP Actions

QueryProfile, ClientQuestLogin, MarkItemSeen, SetItemFavoriteStatusBatch, EquipBattleRoyaleCustomization, SetBattleRoyaleBanner, SetCosmeticLockerSlot, SetCosmeticLockerBanner, SetCosmeticLockerName, CopyCosmeticLoadout, DeleteCosmeticLoadout, PurchaseCatalogEntry, GiftCatalogEntry, RemoveGiftBox, RefundMtxPurchase, SetAffiliateName, SetReceiveGiftsEnabled

Support

Contributing

Contributions are welcome! Please open an issue or pull request if you would like to contribute. Make sure to follow the same formatting and to keep commits concise and readable e.g. do not change line indents to mess up code review!