Jump to content

kawaiiwolf

Members
  • Posts

    46
  • Joined

  • Last visited

    Never

Everything posted by kawaiiwolf

  1. There's a simple solution to the upgrade thing that I've found. Get a copy of a vanilla 1.0 minecraft.jar file. Either install a fresh one and downgrade or find someone with an old jar. The MD5 for the file should be 3820D222B95D0B8C520D9596A756A6E6. Save that file somewhere safe. Go into minecraft, allow it to upgrade, and then replace the 1.1 minecraft.jar with your 1.0 minecraft.jar. Next time you log in, it won't bug you about updating to 1.1. Now, this only works until 1.2 comes out, but then you just repeat the same process.
  2. Looks like something isn't loaded or installed correctly. Can you paste your Modloader.txt file that's in your .minecraft folder?
  3. Highly unlikely. For most people looking for tekkit, they want an experience that's wholly beyond vanilla, and that's just not something that minecraft by itself can offer. Minecraft doesn't feel as if it has endgoals, nothing to work for really. With tekkit, things are expensive, take time and a lot of resources and because of the investment, take time to think out how to build things. It's the effort, both in gathering and designing, that people like about tekkit and, again, that's not something that bukkit can do on it's own.
  4. While utterly confusing, this sounds like a haiku without knowledge of what a haiku is.
  5. Added some more plugins to OP Ptweaks - Reduces Server Lag ChunkManager - Reduces Network Lag MinecartPermanence - Chunk loading blocks in the form of minecarts
  6. Well that explains the seemingly random element to it, but I've found that they do minimal damage to the player (the nether takes a bite out of it but is that really a bother?). Additionally, there's no need to smelt the ores, the tekkit pack comes with custom recipes to convert the nether ores directly into something useful. I.E. a shapeless craft of 1 nether iron converts to iron ore directly, but since it's a custom recipe, you can't do this a stack at a time with meta-keys, just one at a time with a twitchy click finger.
  7. Or electrical engine, depending on how many EU/t you wanna suck down. Power link will eat up 120 Eu/t, the engine only 6. The energy link does supply a lot more juice though.
  8. Well, one approach would be to keep track of the items inside of the tubes. If an item is moving toward an unloaded chunk, load it. Once there are no more items inside a chunk that would otherwise be unloaded, unload it. Sadly this is only an implementation for the transport issue and doesn't really solve the problem of a large redstone network. However, I can see pipeways spanning a much larger chunk distance than a redstone network (at least until BC 3 that is). Edit: To clarify - To detect if an item is headed toward an unloaded chunk, see if there is an item inside a tube on the boundary of a chunk. Since precise timing isn't necessary for item transport (like it could be for redstone), a slight delay in the loading of a chunk wouldn't seriously compromise the integrity of a long pipe transport system.
  9. Teleport pipes are nice but we're missing the root problem here, the chunk loader. There are some mods out there that will keep chunks loaded but that's done via explicit administration. There needs to be something more autonomous, perhaps even a solution that needs to be built directly into buildcraft/redpower. How do you deal with items/signals/events leaving a loaded chunk.
  10. Another problem is just pure logistics. Lets say you build a HUGE pipeway. The problem is, not all of it will be loaded so you're going to lose information. The only way I can see this working is with rail carts and a server mod that keeps the carts chunks loaded. Teleport pipes, while a little theme breaking, do solve the problem of not having to keep large tracts of land and pipe loaded just to transport stuff. Either way, we're going to have to learn to live without
  11. Looking to see what kinds of other mods/plugins other people have installed, things that require no additional effort on the behalf of users beyond installing the Tekkit client. It'd be nice to have a comprehensive list of useful additions to help enhance the experience. If we're lucky, some of these might actually make it into the Tekkit pack. Please include a link ! PermissionsBukkit, Essentials - Great for server permissions and slash commands. See http://forums.technicpack.net/index.php?topic=83.0 Safe Creeper - Nerfs creeper explosions, ghasts and endermen. Still just as deadly, just not devistating to your buildings http://forums.bukkit.org/threads/mech-safe-creeper-0-4-control-creeper-explosions-enderman-tnt-fireballs-and-more-1-0-1-r1.25253/ MinecartPermanence - Keeps chunks nearby minecarts loaded without a player around to babysit or admin privileges. http://forums.bukkit.org/threads/fix-minecartpermanence-v1-1-keep-minecarts-always-loaded-1337.21988/ Ptweaks - Fixes a lot of memory issues and includes a bunch of memory tweaks that keep the server running happy. Additionally, fixes TNT explosions. Blowing up 1000 blocks of TNT works better on the server now than it does in single player. http://dev.bukkit.org/server-mods/ptweaks-remove-all-server-lag/ ChunkManager - Optimizes the network packets being sent to players. Essentially helps to minimize network lag and works very well with Ptweaks. http://forums.bukkit.org/threads/fix-chunkmanager-0-4-2-improved-chunk-sending-algorithms-1597.48294/
  12. If gold is your problem, try dipping into the nether. With nether ores, it's practically littering the nether if you can survive long enough to haul your finds back with you. Just be careful, I've found blocks down there randomly exploding ... and gasts don't make things much easier either.
  13. If you can give me a description of the setup (roles, overview of what they can do/etc) I'll put it up in the OP, keep a list of them.
  14. It really depends on which plugins you have installed to manage permissions. If you use the setup I described in http://forums.technicpack.net/index.php?topic=83.0 the pages that have the plugins also have a full listing of the permissions associated with them.
  15. While you're at it, here's my server address ( 127.0.0.1 ). Can you log in and build for me, I'm too busy to be bothered.
  16. I just had a thought on this though, incremental patches would be great to keep on record, but I'm not entirely certain we want merged versions. imagine this scenario. - Say ID 200 is used by mod 1. - First update, mod 1 is deleted, so ID 200 -> 0 to delete the old blocks - Second update, mod 2 takes over ID 200 - Last update, mod 3 isn't configurable and needs ID 200, so mod 2 gets moved to 200 -> 201 You could have merged updates for the first three (ID 200 -> 0), but if you merged all four, that's where you run into trouble.
  17. Thanks for all the hard work. It seems like the only thing this is missing is a sticky. Will you be including back-ports once new versions are released ? I imagine it might be useful for some people to be able to jump from 1.0 -> 1.14 -> 1.2 in one shot, especially if they haven't updated in a few weeks, the 1.1x branch is still relatively new.
  18. Yes and No. It's one of those random enhancements that makes the game better as a whole, similar to the inclusion of matmos. Make it optional client side or be restrictive on the server settings, but additional animations and some more movement options would be welcome. I.E. the ability to pull yourself onto a ledge and to crawl make perfect sense. Super jumps and gravity defying parkour are another thing, but it'd still be nice to have that option !
  19. Useful for anyone who wants to run their Tekkit server on a linux machine. It's a modified script from https://github.com/lhutton/minecraft-server-init-script and http://www.minecraftwiki.net/wiki/Server_startup_script. It requires rsync and screen and of course your latest java package. On a debian based system you can install it with update.rc <scriptname> defaults where <scriptname> is whatever is whatever you call this file. #!/bin/bash # User editable variables: # Always include the trailing slashes on directories! MINECRAFT="Tekkit.jar" # Name of your server jar file. This script supports vanilla and craftbukkit. MCPATH="/var/minecraft/server/" # Directory on disk of your MC server. Make sure your MINECRAFT jar file is located here. ARGS="-Xincgc -Xmx1024M -Xms1024M -jar" # Standard arguments for the minecraft server jar. USER="minecraft" # User your minecraft server runs under. BACKUPDIR="/var/minecraft/backups/" # Directory for backup tar files. # Various programs this script calls # Setup for Debian by default, you may need to update the location of these for other distros. JAVA="/usr/bin/java" SCREEN="/usr/bin/screen" DATE=$(date +%m-%d-%Y-%H:%M) TAR="/bin/tar" RSYNC="/usr/bin/rsync" # RAM Disk settings. # Don't use this if you don't know what you're doing! # See the README for me info RAMDISK=false # Set to true if you want to use a RAM disk, false to run from a hard disk. See README first. RAMDISKDIR="/path/to/ramdisk/" # The path where your RAM disk is mounted. already_running(){ if pgrep -u $USER -f $MINECRAFT > /dev/null then return 1 else return 0 fi } run_as() { WHOAMI=`whoami` if [ "$WHOAMI" == "$USER" ] then bash -c "$1" else su - $USER -c "$1" fi } start() { already_running if [ "$?" == "1" ] then echo "Minecraft already running ..." else if [ $RAMDISK == "true" ] then echo "Copying files to RAM Disk ..." setup_ramdisk echo "Starting $MINECRAFT ..." run_as "cd $RAMDISKDIR && $SCREEN -dm -S minecraft $JAVA $ARGS $MINECRAFT" sleep 7 else echo "Starting $MINECRAFT ..." run_as "cd $MCPATH && $SCREEN -dm -S minecraft $JAVA $ARGS $MINECRAFT" sleep 7 fi already_running if [ "$?" == "1" ] then echo "$MINECRAFT started." else echo "Error, $MINECRAFT could not be started. Check ${MCPATH}server.log for errors." fi fi } stop() { already_running if [ "$?" == "1" ] then if [ $RAMDISK == "true" ] then echo "Syncing RAM drive to disk .." sync_ram_to_disk echo "Sync complete." fi echo "Stopping $MINECRAFT ... " run_as "$SCREEN -p 0 -S minecraft -X stuff \"say SERVER SHUT DOWN IN 5 SECONDS. SAVING WORLD ...\"$(echo -ne '\015')" run_as "$SCREEN -p 0 -S minecraft -X eval 'stuff save-all\015'" sleep 5 run_as "$SCREEN -p 0 -S minecraft -X eval 'stuff stop\015'" sleep 2 already_running if [ "$?" == "1" ] then echo "$MINECRAFT could not be stopped." echo "Check ${MCPATH}server.log for errors." else echo "$MINECRAFT stopped." fi else echo "$MINECRAFT is not running" fi } status() { already_running if [ "$?" == "1" ] then echo "$MINECRAFT is running." else echo "$MINECRAFT is not running." fi } save_all() { already_running if [ "$?" == "1" ] then echo "Saving all in memory to disk ..." run_as "$SCREEN -p 0 -S minecraft -X stuff \"say SAVING WORLD. PREPARE FOR LAG.\"$(echo -ne '\015')" run_as "$SCREEN -p 0 -S minecraft -X eval 'stuff save-all\015'" sleep 10 run_as "$SCREEN -p 0 -S minecraft -X stuff \"say SAVE COMPLETE.\"$(echo -ne '\015')" else echo "$MINECRAFT not running." fi } backup() { already_running if [ "$?" == "1" ] then if [ "$RAMDISK" == "true" ] then echo "Syncing RAM drive to disk .." sync_ram_to_disk echo "Sync complete." fi echo "Backing up server ..." if [ -d $BACKUPDIR ] then run_as "$SCREEN -p 0 -S minecraft -X stuff \"say BACKING UP. SERVER GOING READ-ONLY.\"$(echo -ne '\015')" run_as "$SCREEN -p 0 -S minecraft -X eval 'stuff save-off\015'" run_as "$TAR czf ${BACKUPDIR}minecraft-server-${DATE}.tar.gz $MCPATH" run_as "$SCREEN -p 0 -S minecraft -X eval 'stuff save-on\015'" run_as "$SCREEN -p 0 -S minecraft -X stuff \"say BACK UP COMPLETE. SERVER GOING READ-WRITE.\"$(echo -ne '\015')" echo "Backup complete." else echo "Error, backup directory not found." fi else run_as "$TAR czf ${BACKUPDIR}minecraft-server-${DATE}.tar.gz $MCPATH" echo "Backup complete." fi } setup_ramdisk() { echo "You are setup to run in a RAM disk." echo "PLEASE see the README about syncing the RAM drive with a hard drive!" run_as "$RSYNC -art --delete-after $MCPATH $RAMDISKDIR" } sync_ram_to_disk() { if [ -f $RAMDISKDIR/${MINECRAFT} ] then echo "Syncing RAM disk to drive ..." run_as "$SCREEN -p 0 -S minecraft -X eval 'stuff save-off\015'" run_as "$SCREEN -p 0 -S minecraft -X eval 'stuff save-all\015'" sleep 2 run_as "$RSYNC -art --delete-after $RAMDISKDIR $MCPATH" run_as "$SCREEN -p 0 -S minecraft -X eval 'stuff save-on\015'" echo "Sync complete." else echo "Error, $MINECRAFT not in RAM disk." fi } mc_command() { command="$1"; if pgrep -u $USER -f $MINECRAFT > /dev/null then pre_log_len=`wc -l "$MCPATH/server.log" | awk '{print $1}'` run_as "$SCREEN -p 0 -S minecraft -X eval 'stuff \"$command\"\015'" sleep .1 tail -n $[`wc -l "$MCPATH/server.log" | awk '{print $1}'`-$pre_log_len] "$MCPATH/server.log" fi } case $1 in start) start exit 1 ;; stop) stop exit 1 ;; save-all) save_all exit 1 ;; backup) save_all backup exit 1 ;; status) status exit 1 ;; writetodisk) sync_ram_to_disk exit 1 ;; restart) stop start exit 1 ;; "command" | "cmd") if [ $# -gt 1 ]; then shift mc_command "$*" else echo "Must specify server command (try 'help' ?)" fi ;; *) echo "Usage: minecraft-server {start|restart|save-all|backup|writetodisk|stop|command/cmd}" exit 1 ;; esac exit 0 This is what I use on my server, but just for safety's sake: USE THIS SOFTWARE AT YOUR OWN RISK. THIS SCRIPT IS NOT WARRANTIED TO WORK PROPERLY OR AT ALL. PROVIDER(S) (i.e. me) ARE NOT LIABLE FOR ANY DAMAGE YOU MIGHT INVOKE UPON YOUR OR ANYONE ELSE'S MACHINE. If you have any questions as to what's going on in the script I'd be glad to help but the commands are fairly self-explanatory: The "cmd" code of is great value since it passes commands directly to the console without having to manually invoke the screen. Lets say you want to whitelist someone without having to edit the file/restart the server or promote a user within minecraft to op. You just type the command from your linux prompt/ssh session: /etc/init.d/minecraft-server cmd whitelist add SomePlayerName
  20. It wouldn't surprise me if I wasn't the only one who's first bukkit server setup was the tekkit pack. It took me a few hours and a bit of tinkering to get it to work stably for a simple setup so I thought I'd share my findings to help save you guys some time as well: Step 1 - Bukkit Plugins - PermissionsBukkit ( http://dev.bukkit.org/server-mods/permbukkit/ ). As I couldn't quite get the flat file permissions to work ... at all ... call me inept or what have you, I went for the defacto plugin. It's got a lot of shiny features and the potential for complicated setup, but in the end, it does what I need it to. - Essentials ( http://dev.bukkit.org/server-mods/essentials/ ). CommandBook is nice and all, but it's frustrating as hell when the motd suggests players to type "/help" and there's no permission set in CommandBook to let them do this. It's also quite a bit more feature rich if you're willing to take the time to look into it and does (most) everything that CommandBook can do. - Removing CommandBook. Unfortunately, there are a lot of command conflicts that I couldn't figure out how to reconcile and since CommandBook was mostly redundant with Essentials installed, it simply had to go. Step 2 - Permissions As a preamble, this is a whitelisted server for myself and friends, so griefing isn't an issue and since we're legit building (no item spawning), op rights aren't generally required. Everything is in the plugins/PermissionBukkit/config.yml file. Here's a copy of mine (This is the whole file. Note: NO TABS, tabs = bad): http://xshade.ca/projects/towny/ and the ever essential Essentials (See link above). He's included links for his permissions setup ( http://forums.technicpack.net/index.php?topic=83.msg965#msg965 ), but you can take a look at his permission file here: groups: default: permissions: permissions.build: true essentials.help: true essentials.home: true essentials.sethome: true essentials.motd: true essentials.kit: true essentials.kit.*: true This lets users see a MotD, teleport to (and set) their homes and spawn a basic kit to get themselves started (Wooden Pick/Shovel/Axe, some planks, torches and a couple cookies to tide them over). That's my story. If you have alternate permission setups, please post them here. Server administration can be a bit of a chore, so the easier we make it for new server admins, the more servers we have available. Volgarenthor gives a much more complicated setup, with no less than 8 role groups. His server employs PermsEX (need link), Groups: Visitor: default: true prefix: '&7[Visitor]&f:' options: build: false rank: 1000 permissions: - essentials.afk - essentials.helpop - essentials.helpop.receive - essentials.ignore - essentials.list - essentials.me - essentials.motd - essentials.msg - essentials.realname - essentials.rules - essentials.seen - essentials.suicide - essentials.spawn - essentials.tpaccept - essentials.tpdeny - essentials.kit - essentials.kit.visitor - -modifyworld.bucket.empty.water - -modifyworld.bucket.empty.lava - -modifyworld.bucket.fill.water - -modifyworld.bucket.fill.lava - modifyworld.* Citizen: default: false prefix: '&3[Citizen]&f:' options: build: true rank: 500 inheritance: - Visitor permissions: - essentials.balance - essentials.balance.others - iconomy.holdings - essentials.balancetop - essentials.pay - essentials.compass - essentials.depth - essentials.getpos - essentials.mail - essentials.mail.send - essentials.delhome - essentials.home - essentials.sethome - essentials.sethome.multiple - essentials.kit.starter - essentials.kit.newbie - towny.wild.* - towny.claimed.owntown.block.* - towny.town.* - towny.nation.* Trusted: default: false prefix: '&a[Trusted]&f:' options: build: true rank: 100 inheritance: - Citizen permissions: - essentials.sethome.multiple.medtier - essentials.kit.irontools - -modifyworld.bucket.empty.lava - -modifyworld.bucket.fill.lava - modifyworld.* Builder: default: false prefix: '&6[builder]&f:' options: build: true rank: 50 inheritance: - Trusted permissions: - -essentials.kit.irontools - essentials.kit.goldtools - essentials.heal - essentials.heal.cooldown.bypass - essentials.jump - essentials.tpa - modifyworld.* Veteran: default: false prefix: '&5[Veteran]&f:' options: build: true rank: 25 inheritance: - Builder permissions: - -essentials.kit.visitor - essentials.kit.* - essentials.sethome.multiple.hightier - essentials.back - essentials.back.ondeath - essentials.heal.others - essentials.top Moderator: default: false prefix: '&9[Moderator]&f:' options: build: true rank: 3 inheritance: - Builder permissions: - -essentials.setworth - -essentials.backup - -essentials.essentials - -essentials.gc - -essentials.remove - -essentials.socialspy - -essentials.sudo - -essentials.setspawn - -essentials.setxmpp - -essentials.xmpp - -essentials.xmppspy - essentials.* - -bukkit.command.reload - -bukkit.command.save.perform - -bukkit.command.save.disable - -bukkit.command.save.enable - towny.admin - permissions.manage.membership.* Admin: default: false prefix: '&c[Admin]&f:' options: build: true rank: 2 inheritance: - moderator permissions: - -essentials.socialspy - -essentials.xmppspy - essentials.* - bukkit.command.reload Owner: default: false prefix: '&4[Owner]&f:' options: build: true rank: 1 permissions: - '*'
  21. I can't support this highly enough. Assuming it's as bug free as a lot of the videos seem to indicate, a well made enhancement such as this, especially one that doesn't require already scarce block ID would be a welcome addition !
×
×
  • Create New...