Yes, you would have to fork the SimpleServer repository on github and install git on your computer. Take a look at github's help pages if you're interested. (I recommend using github even for your personal projects.)
Any other constructive comments concerning the above would also be appreciated...
I would advise you to start off with a simpler project than SimpleServer, especially if you're not familiar with object oriented programming at all. SimpleServer is not very well designed and the source code is a mess in certain places (StreamTunnel, I'm looking at you), so don't think this is how you should build your own projects in the future. Further, most of the problems iBotPeaches currently has to deal with have little to do with programming itself and rather require him to debug quirks in the minecraft protocol which isn't very well designed either (it's a bit better in 1.7).
Exception in thread "main" java.lang.UnsupportedClassVersionError: simpleserver/Main : Unsupported major.minor version 51.0
You're using a very old version of Java and ginbot86 appears to have compiled it against a newer one. Just update to JRE 7 and everything should work fine. (You should do that anyway, JRE 5 is extremely outdated.)
2012-11-24 10:12:16 [WARNING] To change this, set "online-mode" to "true" in the server.properties file.
2012-11-24 10:12:16 [WARNING] While this makes the game possible to play without internet access, it also opens up the ability for hackers to connect with any username they choose.
2012-11-24 10:12:16 [WARNING] The server will make no attempt to authenticate usernames. Beware.
2012-11-24 10:12:16 [WARNING] **** SERVER IS RUNNING IN OFFLINE/INSECURE MODE!
Setting onlineMode to true in config.xml is enough for SimpleServer to authenticate your players. Authentication will always be disabled for the vanilla server running behind SimpleServer, the only bug you found is that the warning no longer gets suppressed.
I just updated SimpleServer for Minecraft 1.4.4, you can download the new version on github.
SimpleServer 8.4.6 should work with Forge, the easiest was to install it is to put the Forge zip file into a folder called plugins and activating the enablePlugins option in simpleserver.properties.
In case you missed it, SimpleServer now comes with an improved backup and rollback system. Visit our wiki for more information.
Attention Bukkit users
From now on, you must use bukkits "world-container" option for usage with SimpleServer.
See the bukkit section in our wiki for details. This makes sure that even with multiple worlds (addon Multiverse) all worlds are considered for backup/rollback.
SimpleServer 8.4.4 (for Minecraft 1.3.1) can now be downloaded here. I am releasing this version one day early because I won't have time to do so tomorrow.
Changes:
Improvements to the event scripting system:
in event xml element: type="plate|button" replaces isbutton attribute
in area xml element: onenter + onleave attributes replaced by event attribute
Removed #CURRTIME special variable -> replaced by currtime stack operator
almost all commands/flow control structures support postfix expressions where it makes sense
Change argument passing for called events... now using Array + multiple assignment to retrieve
All events return a value (if none, then empty array), return command accepts values -> non-void
-> makes thread-stack usage move more into the background, language more usable
improved single-quote escape behaviour
New commands: npc, npckill
new operators: Acontains, Aexplode, getplayers, isinarea, getcoord, currtime, getitemalias, getitemid
removed give command -> use execcmd #PLAYER give ...
execcmd requires now a player name as first argument
New: Shops
Along with SimpleServer 8.4.4 comes a new feature: in game shops.
This has nothing to do with the trading system of Minecraft 1.3, it is a
stand-alone feature of SimpleServer.
Shops make it possible to trade Minecraft items against "credits", now the currency on SimpleServer.
The players interact with vendor bots that show up in the world.
Everything about shops like position, items available, stock sizes and prices can be
set individually when defining a shop.
The shop system is based on the SimpleServer event scripting system,
so shops are scripting code inside the "config.xml" file.
Anyway, creating shops is very easy because we designed
a tool for it: ShopTool.
For SimpleServer specific information (credits, how to use shops, ...) consult the "Usage" section of the Wiki page.
As this is something new, we would appreciate any feedback on shops and ShopTool.
Please use the new SimplerServer - ShopTool forum thread for this.
For bug reports on ShopTool please use the Github issue system (see project page).
I'm trying to get Simpleserver to work with the weekly snapshots, but I can't get it work completely.
First of, Simpleserver with 1.2.5 works flawlessly. The server runs, I can login and explore the world. No issue's at all. Running vanilla minecraft_server from snapshots 12w23a 23b and 27a also works flawlessly. Server runs, and I can connect without any problem.
Then the problem, when I run one of the mentioned snapshots with Simpleserver, it runs on the server, the client is able to see the server. But when I try to connect I'm getting a timeout. And I can't figure out why.
This is the error message I get in the Simpleserver console.
[SimpleServer] IP Connection from 192.168.1.3!
2012-07-09 20:47:34 [INFO] Disconnecting /127.0.0.4:35762: Took too long to log in
[SimpleServer] java.io.EOFException
[SimpleServer] PlayerStream error handling traffic for 192.168.1.3
java.net.SocketTimeoutException: Read timed out
[SimpleServer] Socket Closed: 192.168.1.3
I am open to suggestions.
btw. This is with snapshot 12w23b. Because that should be protocol version 35, the latest one which is supported by Simpleserver. Or I am missing something there
Each SimpleServer build only supports a single protocol version. If you want to use it with version 35 you have to build the source on github yourself.
The enchantment system got fixed in today's snapshot, so most mods will work again when 1.3 drops. I might even implement custom packets of popular mods which don't use then intended mechanisms (RedPower, I'm looking at you).
Tried this out with a modded vanilla server and it seems it's a not-so-transparent proxy. If you don't understand a packet, forward it tot he server ffs.
[SimpleServer] IP Connection from 192.168.254.1!
2012-06-14 12:51:21 [INFO] Pyrii [/127.0.0.5:59285] logged in with entity id 95 at (771.6434701999727, 65.0, -60.662306203615216)
[SimpleServer] java.io.IOException: Unable to parse unknown ServerStream packet 0x62 for player Pyrii (after 0x20
[SimpleServer] ServerStream error handling traffic for 192.168.254.1 (20)
[SimpleServer] Socket Closed: 192.168.254.1
java.net.SocketTimeoutException: Read timed out
2012-06-14 12:51:51 [INFO] Pyrii lost connection: disconnect.genericReason
[SimpleServer] java.io.EOFException
[SimpleServer] PlayerStream error handling traffic for 192.168.254.1 (1)
[SimpleServer] Socket Closed: 192.168.254.1
It's a shame as it seems like it could add alot of missing functionality for vanilla modded servers, but it's refusal to work with mods and lack of documentation I'm finding are major hindrances.
Unfortunately minecraft network packets are not prefixed with a length field, making it impossible to forward unknown packets. Also, there are currently some issues with the enchanting system which should be fixed in the 1.3 update. After the mentioned update all mods based on ModLoaderMP and MCForge should work again, assuming they use the networking functionality of those two mod frameworks.
Your configuration looks fine and unfortunately I can not reproduce your problems. Sometimes Bukkit plugins overwrite SimpleServer's commands, but as far as I know none of the plugins you're using are doing that. The "Teleporting failed" error is only displayed when a teleporting bot fails to connect to the server which is also done when using the /warp command. Are you sure the /warp command works and not just /warptome and /warpmeto?
The master branch was updated to 12w17a, I skipped a few versions because Grum couldn't make up his mind on which encryption to use (the early ones were exploitable). I will probably update to 12w21b sometime next week.
Is there any way to coarsen the permissions for warping? I would really like to be able to allow most of my users to USE warp points without being allowed to CREATE warp points.
Yes, you can do this using an <argument> tag. Have a look at our documentation for an example.
Also, is there any way to make the warp warmup and cooldown limits apply to player-to-player warps (!warpmeto and !warptome)? Right now it only applies to !home, they can warp instantly and as often as they like to each other, and the constant warping is really affecting server performance.
In most cases players shouldn't be allowed to use the /warptome command and should use /visit instead of /warpmeto. Cooldown and warmup apply to the /visit command.
i have gone throught this fourm many times and seen how people have made them self an admin my scripting skills are realy low my dad is a computer tech that runs his own company and i asked him to take a look at the coding he says it looks fine and when i log into the server i'm still set as a guest could i get some help here ?
Your father should have told you to consult the manual:
To make yourself OWNER: Just type setgroup [PLAYER] 5 into the server console where [PLAYER] is your In-Game-Name.
I've also noticed that this program seems to force the spawn to be 0,0 and not the usual spawn. The only time you visit the usual spawn is when you first log on.
Could there perhaps be a fix for this?
I don't think that's true, the spawn point isn't altered in any way.
0
Yes, you would have to fork the SimpleServer repository on github and install git on your computer. Take a look at github's help pages if you're interested. (I recommend using github even for your personal projects.)
I would advise you to start off with a simpler project than SimpleServer, especially if you're not familiar with object oriented programming at all. SimpleServer is not very well designed and the source code is a mess in certain places (StreamTunnel, I'm looking at you), so don't think this is how you should build your own projects in the future. Further, most of the problems iBotPeaches currently has to deal with have little to do with programming itself and rather require him to debug quirks in the minecraft protocol which isn't very well designed either (it's a bit better in 1.7).
0
You're using a very old version of Java and ginbot86 appears to have compiled it against a newer one. Just update to JRE 7 and everything should work fine. (You should do that anyway, JRE 5 is extremely outdated.)
1
If you already downloaded iBotPeaches' build and don't rely on bots you don't need to update to this version.
1
Setting onlineMode to true in config.xml is enough for SimpleServer to authenticate your players. Authentication will always be disabled for the vanilla server running behind SimpleServer, the only bug you found is that the warning no longer gets suppressed.
0
SimpleServer 8.4.6 should work with Forge, the easiest was to install it is to put the Forge zip file into a folder called plugins and activating the enablePlugins option in simpleserver.properties.
In case you missed it, SimpleServer now comes with an improved backup and rollback system. Visit our wiki for more information.
1
Changes:
Attention Bukkit users
From now on, you must use bukkits "world-container" option for usage with SimpleServer.
See the bukkit section in our wiki for details. This makes sure that even with multiple worlds (addon Multiverse) all worlds are considered for backup/rollback.
1
Changes:
Improvements to the event scripting system:
Along with SimpleServer 8.4.4 comes a new feature: in game shops.
This has nothing to do with the trading system of Minecraft 1.3, it is a
stand-alone feature of SimpleServer.
Shops make it possible to trade Minecraft items against "credits", now the currency on SimpleServer.
The players interact with vendor bots that show up in the world.
Everything about shops like position, items available, stock sizes and prices can be
set individually when defining a shop.
The shop system is based on the SimpleServer event scripting system,
so shops are scripting code inside the "config.xml" file.
Anyway, creating shops is very easy because we designed
a tool for it: ShopTool.
So try it out and get started quickly: ShopTool Quickstart-guide
For SimpleServer specific information (credits, how to use shops, ...) consult the "Usage" section of the Wiki page.
As this is something new, we would appreciate any feedback on shops and ShopTool.
Please use the new SimplerServer - ShopTool forum thread for this.
For bug reports on ShopTool please use the Github issue system (see project page).
We hope you enjoy the new feature!
0
This is the default setting for all SimpleServer commands.
There is currently no such setting.
Each SimpleServer build only supports a single protocol version. If you want to use it with version 35 you have to build the source on github yourself.
0
0
Unfortunately minecraft network packets are not prefixed with a length field, making it impossible to forward unknown packets. Also, there are currently some issues with the enchanting system which should be fixed in the 1.3 update. After the mentioned update all mods based on ModLoaderMP and MCForge should work again, assuming they use the networking functionality of those two mod frameworks.
0
Your configuration looks fine and unfortunately I can not reproduce your problems. Sometimes Bukkit plugins overwrite SimpleServer's commands, but as far as I know none of the plugins you're using are doing that. The "Teleporting failed" error is only displayed when a teleporting bot fails to connect to the server which is also done when using the /warp command. Are you sure the /warp command works and not just /warptome and /warpmeto?
I updated the master branch to protocol version 35 today.
0
0
Yes, you can do this using an <argument> tag. Have a look at our documentation for an example.
In most cases players shouldn't be allowed to use the /warptome command and should use /visit instead of /warpmeto. Cooldown and warmup apply to the /visit command.
0
Your father should have told you to consult the manual:
0
https://github.com/SimpleServer/SimpleServer/wiki/Compiling-Your-Own-SimpleServer.jar-Version
I don't think that's true, the spawn point isn't altered in any way.