-
Notifications
You must be signed in to change notification settings - Fork 246
0.15.0 #1094
Comments
Also a version and protocol bump should happen soon so 0.15.0 players can join |
"Yay" more updates |
0.15.0 CURRENT_PROTOCOL=81 |
That's less important than the tons of protocol changes. |
In 0.15.0 a lot of changes in the protocols. Almost all protocols have been changed. |
@dog194 its full released |
@lolcraftboy I think we got the point. |
o oke |
|
Hope it Will be soon :( i was 60-100 player on My server i have 20 now :( |
Please update asap :3 Seems like ImagicalMine found a protocol, its 92 and 1358954509 . Is it working? |
Imagicalmine seemed to fix the problem of not able to join... I didn't check it yet but they said they did |
The official ImagicalMine project is dead, so I find that unlikely. And the Inactive-To-Reactive fork ... well, remotevase doesn't have a clue what he/she is doing with that code. |
Well he is saying it works??? |
That's because he copied code from Steadfast, which will cause issues if it works at all. It's not as simple as guessing the magic number. |
Ohhh I see. Is genisys close to finishing 1.2? |
I can't comment on that one. Plus 0.15.1 beta has just started. |
Oh ok... and the imagicalmine 0.15 version still does not connect. Lol |
0.15.1 is out on the Google play! Beta |
LBSG 0.15 keeps crashing too so it's no use copying from SF2 |
True... so it's better to write a new one from scratch? Then using some stuff from sf2? |
Well, imagicalmine is really close to making it official! They got the protocol now. |
Wait for us.. We have the 0.15.0 branch and we keep developing.. |
Ok!! Great! Glad to hear that! |
i hate this spamming so much... i can understand if some developers stop working because of so much stupid questions.... " 0.15 is out please fix " shit... let the guys do this hard work and wait like all the others -.- but stop spamming shit... |
@SurvivalHive is right. The spam doesn't help us in the slightest. Don't forget that the devs have many other commitments, just like any other people. |
I have a branch that I am currently testing for 0.15.0. Eveyrthing works fine except that the player logs out due to timeout. |
PM updated to 0.15.0 |
Yes, I am implementing their fixes into Genisys. |
My branch works, just tested it out. There is an error message that I am currently working on fixing, but it does not appear to affect anything. I will be submitting a PR very soon. EDIT: Due to the fact that I cannot find a suitable fix for the console message, and some Android players constantly crash when joining the server, I am not going to submit a PR yet. I will continue working on this and hopefully will find a solution. |
Nice! |
Nvm. Can't move. |
Please try the newest build.I have merged from PM. |
Can't join... newest build |
Done.Thanks |
Login timeout with build #466 changes manually patched in Player.php. SteadFast does not work correctly either. While you can join, breaking blocks doesn't create a drop and there are many other bugs. |
also note there are leads on every player, and player movement doesn't update. @CrayonDing |
Yea movement and leads and many worlds |
@xxFlare Did not know that, thanks. ..Genisys fanboy. |
Are u going to fix the bugs tomorow? Please work on the multiworld support! That's the main thing that every server needs! |
@daniktheboss Mulitworld support is the thing that a plugin should do. |
No you do /world "world" and you crash .. that's a plugin error? |
@daniktheboss You think /world is Genisys' command? Check src/pocketmine/command/SimpleCommandMap.php and you will find yourself an idiot. |
Oh lol ... sorry my bad haha.. ok I will try to update it... |
Seems ImagicalMine about to finish the fixes for 0.15.0 ._. |
Who gives a shit about what ImagicalMine is doing? This chat is for the iTXTech team and their work on Genisys, if you wanna go congratulate IMine leave this chat. |
Where download for 0.15.0 Genisys? |
@JUSTaMod I couldn't have said it better myself. Very well said. |
:/ y cant i hit players?? |
Changelog :
show u guys wht changes :)
The text was updated successfully, but these errors were encountered: