I been out of the loop for a bit. What Skin/theme is everyone using?

EDIT- My  mistake, texture pack is the correct term i was thinking of.

The server we all know and love has just received a minor 1.3.1 facelift. The vote to reset the maps dictated (by a small margin) that we are keeping the same maps for 1.3.1, and resetting them for 1.4.

The update went with as few hitches as one could hope for. Had a bit of a hiccup with the maps, so I deleted them and I’ll be regenerating them over the next few days.

That was really the only issue that I’ve run across so far, let me know if you have any other problems.

I’m thinking of resetting the maps.

You. Right now.

Sunday, August 5th, 2012 6:55:59PM PST

I’m really sorry, SDX. 
-Eldornathqy/Thor

Hello Everyone,

I am pleased to announce that the server is in great condition and is continuing to thrive.  With the latest additions to the reporter, the release of 1.3, and the keen eyes of the moderators we have a great server on our hands, however I am not here to talk about the present, I am here to talk about the future of the server.  The server is becoming taxed more every day, but to understand this we must first understand where the server came from.  When this all began, the server was a white list only server for members of the SDX Developers.  From there we grew outwards, eventually being an offline mode server where our population exploded, and with the population explosion, so came a griefer explosion that required mods to take over and combat them.  Eventually we added a voice server mumble which was originally only used for the minecraft server but is now used by the WoW players more than our servers minecraft players.  We invite everyone to join in mumble and talk, it is always great to have a voice chat with your fellow gamers.  And then finally a few months back c0mp and I put together this website for the server.  All this is run on the same machine which is where the future comes in.  It is time to future proof this server, and today is the day!  I have procured the server a new motherboard, as well as an upgrade of ram, plus 2, count them 2 CPU’s on the motherboard.  This board is a beast and will be being shipped to comp and warped Monday.  There is a picture of the new motherboard after the break.

Continue Reading

Dear Noob players,

As you have now realized, if you were a super noob and updated minecraft to 1.3.1, you can no longer connect to the server because we are still running 1.2.5.  It takes a little bit more time for the updates to our Bukkit-based server & plugins to be developed and released, so it may be a few weeks until we begin running 1.3.1. (Patience is a virtue!)  I realize you are terribly excited to play around with all the new features in 1.3.1 (see list of new features on the wiki here) but if you wish to continue to play on the SDX server, you need to do the following:

Download this jar file: minecraft.jar

Windows Vista/7:

1. Click the Start Icon.
2. In the Search Bar, type %AppData% and press Enter.
3. Open Roaming.
4. Open .minecraft.
5. Open bin and you will see minecraft.jar (It may appear only as minecraft).
6. Copy and paste the minecraft.jar you downloaded earlier into this folder.  When it asks you if you want to replace the old one, click Copy and Replace.

Windows XP:

1. Click the Start Icon.
2. Double-click ‘Run‘.
3. Type in %APPDATA% and press enter.
4. Open Roaming.
5. Open .minecraft.
6. Open bin and you will see minecraft.jar (It may appear only as minecraft).
7. Copy and paste the minecraft.jar you downloaded earlier into this folder.  When it asks you if you want to replace the old one, click Copy and Replace.

Macintosh:

1. At the top of the screen, click Finder.
2. From menu, choose Go, Go to Folder.
3. Enter “~/Library/Application Support/minecraft/“
4. Open “bin” and you will see minecraft.jar (It may appear only as minecraft).
5. Copy and paste the minecraft.jar you downloaded earlier into this folder.  If it asks you if you want to replace the old one, click Copy and Replace.

Thanks for playing SDX!

-Thor

Just want to let everyone know that I’ll be visiting family out of state for a week, with very limited access to to the server. I’ll still be able to remote in, but if anything happens that requires physical access to the server (extended power outage or the like) no one will be around to turn the system back on.

So if you can’t connect to the server anytime between Saturday morning and the following Saturday evening, try going outside or something until we get back. I hear there’s… ya know… stuff out there.

I’ll have somewhat limited access to email, so the best way to contact me will be using the Contact form, in the menu bar above. See you all again in a week!

Dear mods,

First of all: I *THINK* I have figured out how to post on the site…..  (fingers crossed, if not, then you probably will never see this)

Second of all: I heartily thank you for sharing the burden of griefer-hunting with me, but I have noticed a distressing problem.  I have come across 10+ different griefers who have been demoted and reported, thanks to wwsean08′s reporting system (thanks for that gorgeous piece of code Sean!) but whose griefings have not been rolled back using Hawkeye.  I checked the files, and the various mods all reported rolling them back, but it apparently failed.  This may be a bug, since most of the failed rollbacks are fairly recent, but I would like to go over brief syntax with you so we all know how to make our Guest world appear immaculate for the new members-to-come joining the server.

Hawk uses several parameters in it commands, primarily  p:USERNAME  r:RADIUS  w:WORLD, the capital letters being specified values. When previewing a rollback, you should use “/hawk preview p:USERNAME r:RADIUS” (the radius parameter is optional, and world parameter is unneeded) and then use “/hawk preview apply/cancel” to apply/cancel the preview.  After a Griefer is demoted, a FULL rollback is needed to clear all their works from the world using “/hawk rollback USERNAME“.

Third of all: I strongly recommend against using hawk’s rebuild command, as it destroys signs, ladders, beds, redstone, torches, repeaters, paintings, rails, ect., re-orients stairs, and empties chests when you use it to restore a player’s edits.  I attempted to fix an earlier boo-boo today using the rebuild command and screwed up some members’ houses so bad that C0mp needed to step in to fix it with massive restores from backups! So… I recommend that, until someone finds a way to circumvent this, the rebuild command be avoided like smallpox infested blankets!

I do not mean to be the young upstart telling the old dogs what to do, I merely offer my humble opinion to the moderator community.

Thank you for your time,

Eldornathqy

-more Hawkeye syntax can be found in this summary: http://i.imgur.com/0MnoQ.png and at their bukkit page: http://dev.bukkit.org/server-mods/hawkeye/

It’s been a while since we’ve added a new Moderator, and yes, we acknowledge it’s been long over due.  We have received a lot of feedback, and even some suggestions of whom among us might be a good fit for the needed position. After some deliberation, c0mp and I have come to the following conclusions:

We have a community that is growing in a positive direction
We wish to maintain and expand this community
We need more support to accomplish this
We have many great candidates
Without further ado,

Please welcome Eldornathqy as our newest Moderator

…our dynmap chat is back!

Honestly, I’m not sure what I did to fix it. I’ve been trying to debug it on and off for months now. The maddening part about it is that none of the PHP logs or browser debugging tools were pointing to any issues. Tonight I sat down to see if I could fix it, did a bunch of stuff, finally ended up breaking dynmap altogether in the process (sorry for anyone who tried to load the map during that ~10 minutes of downtime!) When I undid that change and switched back to the way it was, chat started working.

So it was one of those things where nothing really changed from when chat didn’t work, but something about fully breaking dynmap and then undoing that change somehow fixed chat in the process. So go ahead and use it (don’t abuse it!) but tread lightly. Don’t breathe on it, don’t even think about it too much, because it could break again any time. Enjoy!

c0mp