Hi @shikyo13 :) Great that you are interested, I'll find a way to get the addon to you.

So, the change log? Good question! The change log usually comes out once the addon is officially released, thats cause we might find bugs now in pre-release testing that we want to fix and they'll get added, but roughly, here's what the new version has over the previous:

- Multiple fixes for blender 2.80 beta compatibility (lots of changes to the blender python api have been supported now)

- Multiple scene support - now you can setup multiple scenes to render and all of them will render with crowdrender on all your connected nodes

- Fixed a bug where the hardware id would fail to be returned on some windows systems causing addon to not start (note this is also a security fix, for which the hardware id's of nodes will now change on our system when using 017. You'll get duplicate machines in your node list, but we'll be purging the system regularly after 017 is released to remove the duplicates)

- Fixed a problem where the local node would not render cached animation data (where the data was stored external to the blend file)

- Fixed a bug where opening a file in blender would cause the addon to 'go nuts' and become unstable

- Fixed a design flaw that sometimes caused nodes that were disabled to render to actually render when they shouldn't and vice versa, similar glitching could occur with individual node tile size settings

- Fixed issues with CUDA and OpenCL cards not being used or recognised, they can all be used now and will show up in each node's settings menu

- Fixed intolerable glitching which occurred after either disconnecting a node or reconnecting to multiple nodes (which was done by pressing "Connect" which connects to all nodes, even ones that are already connected. This was referred to as the "connected: " bug since once it happens the system becomes unstable and nodes would show their status as "connected :" and stop responding requiring a restart.

- Each node now shows an alert symbol if the node is not running the same version of the addon as the client/local node. clicking the alert symbol tells you what version that node is running and what version the client is running, so you can fix it by installing the same version on each node.