Our game updates to resources do not use Assetbundle.
Instead, the following solution is used (client C # and Server Java Conventions, the transport Protocol is JSON):
The first step: the client and the server contract a version number.
The second step: The client sends a local version number to the server (different players, the local version number of information is certainly not the same), the server than the latest version number and the client-local version number, filtering out the list of files that need to be updated. Send the latest version number and the list of files that need to be updated to the client.
Step three: The client downloads the list of files that need to be updated until the download is complete, and then rewrites the local version number.
The update to the script is also a mature Ulua scheme.
One recently studied the simple Framework of the June- v0.2.7 network http://www.ulua.org/
This frame is in place.
The LUA script itself is treated as a resource, but it has a special
1. When packaging, package the Lua script resources in the game into zip.
2. The first time the player launches the game, unzip the Lua script's zip file to local. (Execute once, and then update Lua just like normal resources)
Open Source Library: http://icsharpcode.github.io/SharpZipLib/
3. Perform the three steps of "Update resources" above each time the player starts.
Novice Learning-Hot Update in unity-update ideas