DMeville

Untitled

Sep 8th, 2016
302
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 1.73 KB | None | 0 0
  1. I first used Bolt years ago when it was first announced, way before it was part of the Photon family. At that time the developers were very ambitious, and they did make a great product, but like any emerging tool there were lots of initial problems, slow updates/fixes, and the developers would often disappear for weeks without a word. With the very steep learning curve that comes with Bolt, and little to none documentation/tutorials at the time this left myself and other early adopters in a position of frustration.
  2.  
  3. Recently I needed to re-evaluate all the networking packages now available for a project of mine that requires multiplayer. I looked at UNET, Photon, Forge, and others. Most of which had all these problems that frustrated me with Bolt years ago (and terrible support). I decided to take a look at Bolt again, and I'm VERY happy I did.
  4.  
  5. Bolt is still the same Bolt, except everything just works now, and is so easy to use. The learning curve is still very steep (or at least it was for me with no real previous networking experience), but after spending a week of going through the tutorials and documentation (all of which are great now, and super easy to), and asking questions on the active Slack help channel I feel like a networking master. Which is funny because Bolt is doing all the heavy lifting for you.
  6.  
  7. Bolt also has a Bolt for Steam SDK (available upon request at the time of this review) which works great. In only a few hours of work I had players joining a Steam lobby and connecting to a game together with Bolt.
  8.  
  9. Bolt has great - and most importantly - responsive support (<1h response times for all my questions!) which is the big seller for me, as other networking package's support left a lot to be desired.
Advertisement
Add Comment
Please, Sign In to add comment