Hosting your own version of the ClassiCube webclient is relatively straightforward Only the following 3 files are required: 1) A web page to initialise the game .js and display the game 2) The game .js file 3) The default texture pack TODO: more advanced sample (authentication, custom game.js, skin server) ### Example setup For example, let's assume your website is setup like this: * `example.com/play.html` * `example.com/static/classisphere.js` * `example.com/static/default.zip` For simplicitly, 1) Download `cs.classicube.net/client/latest/ClassiCube.js`, then upload it to `static/classisphere.js` on the webserver 2) Download `classicube.net/static/default.zip`, then upload it to `static/default.zip` on the webserver The play.html page is the trickiest part, because how to implement this is website-specific. (depends on how the website is styled, what webserver is used, what programming language is used to generate the html, etc) #### Changing where the game downloads the texture pack from There should be this piece of code somewhere in the .JS file: `function _interop_AsyncDownloadTexturePack(rawPath) {` A bit below that, there should be `var url = '/static/default.zip';` - change that to the desired URL. #### Embedding the game in play.html The following HTML code is required to be somewhere in the webpage: ```HTML ``` **To start in singleplayer instead, just use `arguments: [ {username} ],` instead** ##### Variables * {username} - the player's username * {mppass} - if server verifies names, [mppass](https://wiki.vg/Classic_Protocol#User_Authentication). Otherwise leave as `''`. * {server ip} - the IP address of the server to connect to * {server port} - the port on the server to connect on (usually `'25565'`) ### Complete example The links below show how to integrate the webclient into a simple website * [Flask (python webserver)](hosting-flask.md) ### iOS / Android support The webclient is compatible with Android / iOS devices and will show a touch based UI to these devices. However, due to the limited screen size available on such devices, you should consider serving a webpage consisting of just the `` to these devices - no header, footer or anything else. Additionally, you will likely want to ensure zooming is disabled, viewport width is same as the device's width, and that 'add to device homescreen' is fully supported. You can accomplish that by adding these three HTML tags to the page: ```HTML ```