I’m tried to work with UNET many times during its development.
Developers of UNET forces us to use UNET, but it is still have a lot of critical bugs and flaws. Very bad tutorials, documentation and overall usability.
And seems like developers does not read feedback from the forum during long time.
It is sad.
Someone even use UNET for serious project?
I know UNET used in '7 days to die", but I don’t have an idea how they managed to do it.
Working with UNET it is pain, even with the most simpler tasks which can be implemented easily using old Unity network.
I want to prepare a full list of thing which should be fixed in UNET with maximum priority, but I’ looking on this forum and afraid that no one even will not read this.
Actually, I found this thread and seems like it is already answered on my question.
It is sad. Turned out that not everything which developed by Unity is a revolution.
Will hope that it is exception and not a rule for further Unity updates.
I am not sure what i need to comment. OK, i’m trying
When we started we understood that we cannot satisfy all our customers with one library, first of all because requirements from different customer groups are different. Newcomers want to make network game immediately and transparently (by pressing couple of buttons and left magic to unity), experts want access to raw sockets. The decision was made, to implement foundation, (without significant care how difficult api will be) + different libraries on top of them. HLAPI was implemented (and I repeated that here on during all unites where I presented) as EXAMPLE how it can be implemented. As HLAPI was develop in the same time when LLAPI implemented, some features are duplicated (if same feature was not ready yet in llapi, it was implemented in hlapi and do not block development). But again it is just example, we open source code so everybody can use it change it and so on.
We did hope that community will create different library on top of foundation and publish them. We was wrong Nobody want to do this.
We did hope that community will help us to find the bugs during pre-alpha alpha and beta testing. For new transport we published and keep in-sync special Unity build almost for a year. Very limited number of developers tried it and helped find and fix the bugs (thanks guys, i appreciate your help). But again - it was very limited amount.
So? we are not wizards (and I’m sorry about), we just try to do our best.
AFAIK, The code weaver stuff is only used by the HLAPI and wouldn’t interfere with building a custom library on top of the LLAPI.
I think the main reason people aren’t building their own interpretations of the HLAPI is because it’s a pretty hard thing to do well. The vast majority of people using unity want to make games, not build networking libraries.
Personally I ended up getting my hands super dirty digging around in the HLAPI code. While i would call it a worthwhile experience, at the end of the day it was a major setback for my project. I would have rather spent that time making my game more awesome instead of working on plumbing issues the player will never see.
@robochase , @marcV2g understood… Cannot promise that we will create that fast, but we will try… Anyway, according llapi you can always ask me, and as I know that or documentation is hmm, “not good” I’m ready to answer for any question related this.
Nobody want to do this.