Official Everybody Edits Forums

Do you think I could just leave this part blank and it'd be okay? We're just going to replace the whole thing with a header image anyway, right?

You are not logged in.

#2 Bots and Programming » [Library] OpenPIO.PlayerIOServer | Open-Source PlayerIO » 2017-01-06 17:39:32

OpenPlayerIO
Replies: 5

OPIO_Post.png

OpenPIO.PlayerIOServer

An open-source alternative to PlayerIO.
Repository

FAQ:
  • What license does OpenPIO.PlayerIOServer reside under?
    GNU General Public License 3.0 or higher.

  • Which .NET framework does OpenPIO.PlayerIOServer require?
    .NET Framework 4.6 or above.

#3 Re: Bots and Programming » [Library] OpenPIO.PlayerIOClient | Open-Source PlayerIOClient » 2016-10-31 01:11:52

The repository URL has been changed, as previous automated build configurations needed to be purged.

#5 Bots and Programming » [Library] OpenPIO.PlayerIOClient | Open-Source PlayerIOClient » 2016-10-29 18:11:12

OpenPlayerIO
Replies: 11

OPIO_Post.png

OpenPIO.PlayerIOClient

An open-source alternative to PlayerIOClient.
9tk7vrpboxu2lleu | Repository

FAQ:
  • Is it possible to use this as a drop-in replacement for PlayerIOClient?
    Almost certainly. There's support for the vast majority of PlayerIOClient functionality.

  • What are the benefits of using OpenPIO.PlayerIOClient rather than PlayerIOClient
    The largest advantage towards open-source is the flexibility it provides.
    For example, OpenPIO.PlayerIOClient provides valid JSON representations of DatabaseObjects, as opposed to the pseudo-JSON you'll find in PlayerIOClient.

  • What are the performance costs/benefits when using OpenPIO.PlayerIOClient?
    Currently, there are no benchmarks available - we'll get on that soon!

  • What license does OpenPIO.PlayerIOClient reside under?
    GNU Lesser General Public License 3.0 or higher.

  • Which .NET framework does OpenPIO.PlayerIOClient require?
    .NET Framework 4 or above.

Board footer

Powered by FluxBB

[ Started around 1732215164.657 - Generated in 0.080 seconds, 9 queries executed - Memory usage: 1.29 MiB (Peak: 1.4 MiB) ]