-
-
Notifications
You must be signed in to change notification settings - Fork 901
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
FUTURE CLIENT #4303
Comments
but why use 2 clients at once? + meteor is compatible with future, it now crashes (which is a bug) #4141 |
its not compatible and i wanna use 2 client bc future doesnt have alot of modules that meteor can easily have with pulgins |
Future has been rewritten for modern versions for about a year now. so I'm not sure exactly what you mean by "native version" |
so i managed to get it to work. it was not a problem with rusher. future and meteor are only compatible on one 1.20.1 version. "meteor-client-0.5.4-1935.jar" due to the fact that meteor doesn't store its older versions, which is a bit stupid as there are very little downsides of it, it is hard to get your hands on this version. one way is to rewrite the code so it works with future i personally dont know how to do this but if your smart this is probably the best way. or. you can download it from someone else who has it. i would never recommend downloading anything form anyone ever however i needed meteor so i took the risk and asked someone i trust who had the file. long story short thats the only version that works with future on 1.20.1 and i can confirm it works. if you want the .jar file dm me on discord "doritobob777" and ill send it to you. if you dont trust me however you will have to find someone else, or, rewrite the clients code. |
Describe the feature
MAKE IT SO ITS COMPATIBLE WITH FUTURE PLSSS IM BEGGING
Before submitting a suggestion
This feature doesn't already exist in the client. (I have checked every module and their settings on the latest dev build)
This wasn't already suggested. (I have searched suggestions on GitHub and read the FAQ)
The text was updated successfully, but these errors were encountered: