IssueRaiser

During the beta, the way we used to release CosmosUI was to send modified versions of the game interface files.

During the beta, the way we used to release CosmosUI was to send modified versions of the game interface files. On every patch, we had to manually go over all the changes we made and re-apply them to the new files. This process took several hours and in the process, no one could really play because they didn't have all their mods. Since it was becoming a real pain, I figured out that we could modify the existing functions from a new file instead of modifying the actual files[1]. I spend several weeks transforming all our code into "mods", essentially the first addons :) Once this migration was done and patches were no longer a pain point, Blizzard officially introduced the notion of addons. [1]: http://blog.vjeux.com/2011/javascript/hook.html

Posted by vjeux on May 21, 2014, 6:25 PM

Tags

Related issues

Raise real-world problems, find people facing the same issue, and discuss solutions.9,500 issues0 comments

hackernews (Other)

During the beta, the way we used to release CosmosUI was to send modified versions of the game interface files.

vjeuxMay 21, 2014, 6:25 PM

During the beta, the way we used to release CosmosUI was to send modified versions of the game interface files. On every patch, we had to manually go over all the changes we made and re-apply them to the new files. This process took several hours and in the process, no one could really play because they didn't have all their mods. Since it was becoming a real pain, I figured out that we could modify the existing functions from a new file instead of modifying the actual files[1]. I spend several weeks transforming all our code into "mods", essentially the first addons :) Once this migration was done and patches were no longer a pain point, Blizzard officially introduced the notion of addons. [1]: http://blog.vjeux.com/2011/javascript/hook.html

Comments (0)

No comments yet. Start the discussion.

Comment on this issue