Releases: YNG-CLIENT/Client
Releases · YNG-CLIENT/Client
v1.0.3
Full Changelog: v1.0.2...v1.0.3
1.0.1
fix: Use GH_TOKEN and disable auto-publish in package.json - Change workflow to use secrets.GH_TOKEN instead of GITHUB_TOKEN - Remove publish config from package.json to prevent auto-publish - Let our workflow handle the release creation instead - This should fix the electron-builder GitHub token errors
0.0.1 | YNG Client (BASE Release)
🚨 ALPHA Release – Still in Development – NOT PREBUILT 🚨
YOU Must build it yourself for NOW!
Version a-0.0.1 | YNG Client
What is YNG Client?
YNG Client is a Minecraft Launcher the client is 100% free with NO Microtransactions like Lunar Client, Badlion, Feather and MANY MORE we are keep the base client open source keeping OUR api closed source while being connected using the app we are working on making users not need to watch fucking ads in a LAUNCHER to a PAID game
Full Changelog: https://github.com/YNG-CLIENT/Client/commits/v0.0.1-alpha
FAQ
- Why Would We Need ANOTHER client? You don't you should NOT need another client VS the base minecraft client.... BUT microsoft dose not care about the looks or performance even MOST major clients don't saying Hey! Let me spend 20$ for a FUCKING CAPE.
- How can the client be open source BUT Connect to the YNG Client API? We care about security and have the API source code limited to 2 people @KoopaCode & @iakzs you connect to it using our API url setup via the /src/main/src/main/config.js file!
- Will the API ever be open source? Depends aslong as we continue the development we WONT release the source for the API. If the development ever stops we WILL release the API & or update the client to have the API built in & or make it setup to play without the API
- Can I OPT out of using the YNG API? Kinda? We are working on making a documentation so YOU can create you're OWN api! and set the new API endpoint in the settings tab. We plan to setup a OPT out of auto updates and YNG Client API option SOON!
- How do the YNG Client Capes work? We create capes on our Appwrite DB and upload to there bucket and the client will check if the signed in user was granted the said cape!
- What DO we store in our API? We Store 1. UUID 2. Username 3. Granted Capes 4, Client Version! Everything else is disgraded and not synced to our Appwrite