NEW FEATURES:
1. Auto-Update Time Settings on Server start.
2. Editable text document in GUI. (will help people who don't want to open a file with notepad)
3. Add more to Tools? Not sure what...but something would be nice!
ADD-ONS:
1. Customizable Chat
> I really want a command like /msg [player/console] [message] , maybe you can devise it to merge it with /whisper, or
make it an alias.
2. Store(for zombie)
3. Zombies should have some super power...i dunno what but something like letting them fly would be funny
AUTOS:
*(Currently command blocks/macro blocks)
1. Development Layout Purpose:
Command blocks - generally for the use of repeating(aka using /repeat) commands. *Note: Can only repeat 1 command at a time. so sad
Macro blocks - generally for the use of repeating(no command yet, but it's for repeating more than 1 task) blocks.
2. Development Layout Construction:
Command blocks:
/cmdblock [block] [cmd] [args] [#ofuses]
[#ofuses]: Any Positive Number, Infinite
/cmdblock show -shows which blocks are valid command blocks.
Macro blocks:
/macro record [blocks] [filename] - records/ LOGS the blocks that are placed or built.
/macro abort - optional, maybe can use /abort
/macro stop - stops the recording to [filename]
/macro save [block] - saves the macro as a specific block.
/macro delete [filename] - deletes the specified macro file.
[block]: air, water, lava, and more possibly.
/macro show - shows where macros are placed.
OTHER INFORMATION:
Command blocks:
If no [block] is specified, then the block in player's hand will be used.
Macro blocks:
This may be a new concept. So i think it will take time. It'll be similiar to how bot files are saved. They don't have an extension yet like .bot, or .macro.
[Example]
I pulled up a bot file and here it is:
- Code: Select all
#Version 2
walk 1149 1107 519 223 10
nod 10 2
Obviously this is like a macro...except an object(bot) is moving. Bot(or whatever it is called) Files make bots move. Macro Files should repeat blocks placed/built. There can be more discussion though.
[More Complex Example]
- Code: Select all
place [block] 30 50 30
place [block] 30 51 30
place [block] 30 52 30
place [block] 30 53 30
place [block] 30 54 30
place [block] 30 55 30
I'm not sure if it would be something like that, but generally if you were going to do that by (hand or should i say) command blocks that would be difficult since command blocks generally can only do one line of tasks whereas a macro file will be able to record or log a series of events into a file that can be replayed later.
*No idea but i just really like the word log now.
Lastly:
/macro record [blocks/command] [filename] - logs the commands/blocks that are being done, and placed or built. [Logged to file]
So what I have been thinking is that maybe command blocks are just blocks that can only perform 1 command for 1 block (That means it can only perform 1 build for 1 block, making it useless for building blocks since it would be time consuming and very unorganized)
NEW AUTO(S):
Auto Achievements> Ideas for Implementation
So far I have only got a few ideas.
PLAYER ACTION | PLAYER AWARDED
AFK | AFKer
Buy 1st item | Shopper
Chat "You are nice" | Kind
Chat "{anything}" | NOTABOT
Die for 50 times | DIEHARD
Don't die for a round | Survivor
Fall over at least 5 blocks | FALLER
Jump 10 times in a row | Hopper
Jump | Jumper
Walk on ground | Walker