Do you think I could just leave this part blank and it'd be okay? We're just going to replace the whole thing with a header image anyway, right?
You are not logged in.
Pages: 1
Ever wanted to y'know, have bigger blocks?
Well, I have the solution for you.
It's called biggifier bot, and turns your worlds into a big block nightmare - or heaven!
This bot can:
Turn your blocks into any size blocks
Auto-align the blocks into a secret hidden grid, so you can place a block roughly in an area, and watch as it automatically snaps to the position
Don't want the auto alignment to the secret hidden grid? That's fine, you can turn it off.
It may lack in features, but it doesn't lack in entertainment.
Offline
Make the snap to grid an option.
If you would like me to make a bot for you, go here.
Offline
->
->
BTW add a check box to turn the bot on and off without disconnecting or changing the value to 1.
( ͡° ͜ʖ ͡°)
Offline
This can be usefull to fill, or why not to create a level with a brush !
But there's somes fix to do :
I made the bot crash, and after reload it I had a weird inferno glitch : 9 blocks were keeps replaced, very very fast, it was fun !
After few time, the bot crashed
EDIT : The problem is funnier when you set a bigger brush size !
Anyway nice bot
I cannot run it.
This can be usefull to fill, or why not to create a level with a brush !
But there's somes fix to do :
I made the bot crash, and after reload it I had a weird inferno glitch : 9 blocks were keeps replaced, very very fast, it was fun !
After few time, the bot crashedEDIT : The problem is funnier when you set a bigger brush size !
Anyway nice bot
The replacing problem is caused by placing a block where the bot is making a block bigger.
In this case, you placed a block, and then the bot started to make them bigger. While the bot made the block bigger, it realized the other block was placed, then places it, then recognizes that it placed a block, and places that one, and cycles through over and over again. Planning on fixing it.
->
->
BTW add a check box to turn the bot on and off without disconnecting or changing the value to 1.
Yea, a simple little bug.
I'll do the "btw" part as well.
Offline
It was fun playing with it. Some bugs were a little annoying but that's ok. Bots like this really spice up the game a little bit Thanks for sharing it!
Offline
In case 'b', make it recognize when the botid is placing a block and don't register that block as a block to make bigger.
If you would like me to make a bot for you, go here.
Offline
In case 'b', make it recognize when the botid is placing a block and don't register that block as a block to make bigger.
But what if the person lags?
For example on my laptop, I need to put the delay between placing on ~25, even though it rarely accepts ~15 too.
On my PC though I can use the regular 10ms (even though thread.sleep probably does something like 12).
Offline
I updated it... I guess...
all it really does is work with the current "b" instead of rot13 so it's useable again...
meh
i really dont think anything else was added...
Offline
This bot still has bad bugs which need fix. Also please add the ability to unlock edit by code.
I'm known as "haslo" in EE. Also, I refuse to play EEU.
Offline
This bot still has bad bugs which need fix. Also please add the ability to unlock edit by code.
"bad bugs" Why doesn't you write them here? How else could he fix them if you are not telling him this?
Offline
Jabatheblob1 wrote:In case 'b', make it recognize when the botid is placing a block and don't register that block as a block to make bigger.
But what if the person lags?
For example on my laptop, I need to put the delay between placing on ~25, even though it rarely accepts ~15 too.
On my PC though I can use the regular 10ms (even though thread.sleep probably does something like 12).
Try not using Thread.Sleep even though you are on a seperate thread. It's best to make it loop and check on the millisecond time.
Offline
It's best to make it loop and check on the millisecond time.
You know such loops might result in high CPU usage, right?
Used to have such kind of loop (though not for checking amount of milliseconds passed, but instead if a list had items) in an old project (that I improved later), and my Intel i7 was on a minimum of ~45% CPU usage, from just that bot (I knew it was because of that loop because not running it put the CPU level back to normal levels).
Really I can understand a timer would be better (like said here and there), since it actually waits 10ms (instead of waiting at least 10ms like thread.sleep), but I don't really like having to use AutoResetEvent that much.
Your solution I honestly can't see the good part of. No offense.
Offline
Swarth100 wrote:It's best to make it loop and check on the millisecond time.
You know such loops might result in high CPU usage, right?
Used to have such kind of loop (though not for checking amount of milliseconds passed, but instead if a list had items) in an old project (that I improved later), and my Intel i7 was on a minimum of ~45% CPU usage, from just that bot (I knew it was because of that loop because not running it put the CPU level back to normal levels).
Really I can understand a timer would be better (like said here and there), since it actually waits 10ms (instead of waiting at least 10ms like thread.sleep), but I don't really like having to use AutoResetEvent that much.
Your solution I honestly can't see the good part of. No offense.
Add a thread.sleep(x) to the loop and you have a pretty accurate and efficient queue.
(Or y'know. BotBits.)
I have never thought of programming for reputation and honor. What I have in my heart must come out. That is the reason why I code.
Offline
Add a thread.sleep(x) to the loop and you have a pretty accurate and efficient queue.
(Or y'know. BotBits.
The whole point of his loop was to eliminate the need for thread.sleep. xD
Also, shameless advertising.
Also, I prefer to make as much myself, as long as it's reasonable (EEPhysics being unreasonable to recreate, obviously), hence why I personally don't use stuff like BotBits.
Offline
bump easteregg text wow you found it
Updated to 1.2. See the change log in the "Updates" spoiler.
Offline
Pages: 1
[ Started around 1732203913.0785 - Generated in 0.092 seconds, 12 queries executed - Memory usage: 1.68 MiB (Peak: 1.91 MiB) ]