Комментарии:
very very useful than
k you so much
Yeah most devs really don't promise not to break their API, which is extremely annoying.
I mean if devs are going to constantly break the API, especially not on a schedule or pre-announced, can they at least leave the old method in place, mark it as depreciated, and then point it to the new method so people have a chance to work on updating their code, not just open up the project one day and have Unity and VisualStudio scream at them there's now 50+ errors.
It's like moving a road to a new one, we don't just close down the old road suddenly and say "Sorry go around." We leave the old one open, let people know "Hey this new thing is happening, start using it when it's ready." and then go "Yeah old road is gone, go to the new one like you were told six months ago when we started building it."
Basically can dev's stop with the secret api changes, then all of a sudden blow up entire projects when the new release and changes drop unannounced.
I am using FishNet for my Unity project and it’s working great! Thanks for all the hard work you put in this solution
One thing that would be immensely helpful are docs or tutorials that cover the basics of networking and explain the used concepts from the ground up. Just from a glance it seems like this is the case for NGO documentation but in the FishNet docs I often got lost in the beginning because it was not very clear where to start and most articles assume some background knowledge or previous experience with networking solutions. Other than that I have really enjoyed working with FishNet so far.
The main problem with FishNet is, it doesn't have as many practical tutorials as other network solutions. Such as chat system tutorials, lobby systems, etc
Ответить