I have a few friends who like playing JSettlers against robots only, and they're frustrated when they can't log in to the server or can't get any free bots.
I've altered JSettlers so that the client starts up its own server plus three robots. All communication is over pipes instead of sockets, since Java security restrictions would otherwise prevent the client from connecting to the local server. You can try it out at this URL:
Is anybody interested in incorporating this patch into JSettlers itself? Doing so would require a few changes to the existing code in order to support pipes in addition to sockets. Basically, I propose creating an SOCSocket interface and an SOCServerSocket interface. These interfaces can either be implemented by wrappers around the standard Socket and ServerSocket objects, or they can be implemented by my LocalSocket and LocalServerSocket objects, which use pipes instead. Thoughts?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I like your thoughts here Jeremy! This would also be good for the client application: it could start a server for a quick personal game, or quick host a game for others to connect to directly.
The user interface will take some planning to look and work smoothly, but it's very good.
Care to take the discussion to the dev forum?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have a few friends who like playing JSettlers against robots only, and they're frustrated when they can't log in to the server or can't get any free bots.
I've altered JSettlers so that the client starts up its own server plus three robots. All communication is over pipes instead of sockets, since Java security restrictions would otherwise prevent the client from connecting to the local server. You can try it out at this URL:
http://afflatus.cs.berkeley.edu/settlers
Is anybody interested in incorporating this patch into JSettlers itself? Doing so would require a few changes to the existing code in order to support pipes in addition to sockets. Basically, I propose creating an SOCSocket interface and an SOCServerSocket interface. These interfaces can either be implemented by wrappers around the standard Socket and ServerSocket objects, or they can be implemented by my LocalSocket and LocalServerSocket objects, which use pipes instead. Thoughts?
I like your thoughts here Jeremy! This would also be good for the client application: it could start a server for a quick personal game, or quick host a game for others to connect to directly.
The user interface will take some planning to look and work smoothly, but it's very good.
Care to take the discussion to the dev forum?