Official Everybody Edits Forums

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.

#1 Before February 2015

nlmdejonge
Member
Joined: 2015-02-15
Posts: 1,264

some questions (for a new room "Speed Run 2")

Two days ago I opened a room Speed Run 1 and used some scripts to keep track of how fast players finished it and display their scores (seconds) here.

I've just closed aforementioned room (after two days and 226 runs/plays), uploaded the code I used so people can check it out (*), and I'm now going to focus on a new room Speed Run 2.
(*) The download link is in the last post of the room's thread.

I have two questions that will hopefully improve the playing experience of the new room:
1. As you can see here, jaa and spiderman managed to start the run together, even though I tried to prevent this using a green door as you can see in the room. Some other players also managed to do this. My question about this is: does anyone know of a way to make 100% sure that only one player enters a certain area? Maybe by using multiple spawn/starting points or certain coin(door) locations?
2. Some players leave immediately after their screenshot is taken and they drop down into the track. This means other players have to wait for no reason until the timeout is reached. What would be the best way to prevent this? I am thinking about also creating screenshots of the minimap to see if a player is still on the track, but maybe somebody has a better idea.

I will make it less likely for players to run out of time, but at the same time decrease the max. number of minutes the player gets. (So, the track will be shorter.) Also, I'm thinking about splitting the new room in half: the right side for the real run, the left side with the same track but on regular blocks and no time limit, so players can check out what's there and practice. Any other ideas? Or suggestions from those of you who played Speed Run 1?

Last edited by nlmdejonge (Jan 3 2012 5:36:42 pm)


I have permanently left the game and forum.
EE is an entertaining game and I enjoyed playing it...
...but it's time for me to move on.

Offline

#2 Before February 2015

cyph1e
Guest

Re: some questions (for a new room "Speed Run 2")

Hey,

I had a look at your source code, and was amused at your creative way of making this bot.
However, you'll be quite limited by using a bash shell script. You should look into using the
.NET PlayerIO API. This way, you can simulate a player and recieve all events sent from the
server and adjust the state of the bot accordingly. It runs decently on mono if you are on linux.

Almost a year ago, I created my first bot called along with the quickrace levels. The bot
respawned all active player on the start of a 'round', and started the internal timer.
You can see if a player has finished the level by listening to some event, such as taking
the crown, picking up his 10th coin, or any other event that is bound to a player. The timer
ofcourse depended on the server lag, but usually it measured it accurately with an error of
about 0.1 seconds. For every finished user, the bot reported in the chat the time of that user.

Getting to know if you placed third or if you beat the level highscore (or your own highscore)
were also features of quickrace.

Once you have the basic functionality, you can easily extend to let player have lifes and do
elimination like in shift, and probably a load of other stuff I didn't think of at that time.

I played your map, and the waiting time killed all the fun. It's a much more thrilling experience
if you can race with your opponents live.

#3 Before February 2015

nlmdejonge
Member
Joined: 2015-02-15
Posts: 1,264

Re: some questions (for a new room "Speed Run 2")

Thanks for your suggestions, cyph1e.


I have permanently left the game and forum.
EE is an entertaining game and I enjoyed playing it...
...but it's time for me to move on.

Offline

nlmdejonge1423767999193433

Board footer

Powered by FluxBB

[ Started around 1739058909.152 - Generated in 0.059 seconds, 11 queries executed - Memory usage: 1.36 MiB (Peak: 1.45 MiB) ]