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.
141 Commits 1 Branch 0 Tags 1.4 MiB
Go 95.7%
HTML 3.3%
JavaScript 0.8%
Dockerfile 0.2%
b0d2d6fd2c
Go to file
Eccentric b0d2d6fd2c Better
2024-02-10 00:34:12 +00:00
aid Better 2024-02-10 00:34:12 +00:00
discord Better 2024-02-10 00:34:12 +00:00
fortnite Better 2024-02-10 00:34:12 +00:00
handlers Better 2024-02-10 00:34:12 +00:00
person Better 2024-02-10 00:34:12 +00:00
socket More socket 2024-01-31 16:21:19 +00:00
storage Atomise permissions field in database 2024-02-09 21:51:26 +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 Better 2024-02-10 00:34:12 +00:00
go.mod Add amazon s3 cloud settings 2024-02-04 19:49:31 +00:00
go.sum Add amazon s3 cloud settings 2024-02-04 19:49:31 +00:00
main_test.go Add permissions test 2024-02-09 23:56:06 +00:00
main.go Better 2024-02-10 00:34:12 +00:00
makefile Better 2024-02-10 00:34:12 +00:00
readme.md Better 2024-02-10 00:34:12 +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?

  • Party System V2 Currently it relies on the automatic XMPP solution which is very hard to keep track of.
  • Seeded randomization for the Item Shop instead of a random number generator. This will ensure that even if the backend is restarted, the same random items will be in the shop during that day.
  • 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

Supported MCP Actions

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

Support

Contributing

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