-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
uploading #19
Comments
I'm sorry for the delay in adding the upload game feature. Several months ago, I promised the developer of VRP that I would add this feature, but due to some personal reasons, I haven't been able to devote much time to QRookie. |
Here, I promise again that I will add the upload game feature. I can't guarantee that it will be added very soon, but I will definitely implement this feature eventually. |
How this works?? It's secure that anyone could upload games? That person would need to create a torrent? If you could share your thoughts? @glaumar |
We need to implement the functionality of the getApkButton_Click function in rookie. Simple description:
More details need to be read from the code, such as checking if the user is connected to a Quest VR device or an Android phone, and how the compressed file should be named. Possible difficulties:
|
A more effective implementation approach would involve enabling QRookie to determine which packages on the connected device are either more up-to-date or missing, similar to how Rookie operates. This method is the primary source of most Rookie donations. For reference, the following files are relevant:
The recommended functionality for QRookie should be as follows:
This approach ensures that QRookie efficiently facilitates the donation of game files. Relying on a single button that requires the user to manually select each package is not only inefficient but also fails to prompt immediate action. |
can you add a way to share the games we own with the vrp team the sharing is an integral part of keeping the group running
No donos = No VRP
The text was updated successfully, but these errors were encountered: