a) a lot of files are used by both server and client. Packaging server and client separately would require you to double the files - and therefore to waste space.
b) please read the AssaultCube License. You are not allowed to add or remove files during repackaging. Sorry.
c) it's impossible to package a client that would not also work as a server. It's just the way it is.
If you really want to package a server, the first step would be to create a script and a setup that would allow "installed" binaries to properly run a server in the first place. Current packages (like deb) horribly fail in that department. Hint: for the most recent release version 1.2, you will probably have to use the client binary to run the server. Or wait for the next version...
b) please read the AssaultCube License. You are not allowed to add or remove files during repackaging. Sorry.
c) it's impossible to package a client that would not also work as a server. It's just the way it is.
If you really want to package a server, the first step would be to create a script and a setup that would allow "installed" binaries to properly run a server in the first place. Current packages (like deb) horribly fail in that department. Hint: for the most recent release version 1.2, you will probably have to use the client binary to run the server. Or wait for the next version...