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

Jojatekok
Guest

When bombing goes wrong...

Are you happy when someone bombs your level with guests or accounts for free? Yeah, me, too, but today, I've just realized that it's not so good sometimes...

I was just hosting our bot-assisted level called 'Yo!Scroll', then suddenly, I disconnected (that happens very often to me, I don't know why :/). I tried to reenter, but the bot couldn't join the room. I tought it was the bot's fail, but I could neither join using the Flash client. So, I looked at the lobby and saw this:

madnessc.png

My suggestion is - yeah, this topic could go to the 'Game Suggestions' section, but there, it wouldn't get any attention - to let the level's owner enter the level anytime, even when the world is full of people. What do you think?

Last edited by Jojatekok (Jun 3 2012 10:55:11 am)

#2 Before February 2015

Processor
Member
Joined: 2015-02-15
Posts: 2,246

Re: When bombing goes wrong...

Player.IO dosent allow rooms to have more players than 45. It is a bug that it shows 51 right now. And sorry, it was me bombing //forums.everybodyedits.com/img/smilies/tongue


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

#3 Before February 2015

DJDavid98
Member
From: Hungary
Joined: 2015-06-12
Posts: 305
Website

Re: When bombing goes wrong...

I personally agree, tho I never had this issue before.
And by the way, you are not the owner of the level, so... xD
Untitled-1.jpg

Last edited by DJDavid98 (Jun 3 2012 11:32:29 am)

Offline

#4 Before February 2015

Jojatekok
Guest

Re: When bombing goes wrong...

DJDavid98 wrote:

I personally agree, tho I never had this issue before.
And by the way, you are not the owner of the level, so... xD
http://i0.kym-cdn.com/entries/icons/ori … tled-1.jpg

I'm not the owner of it, but I can access the owner's account. //forums.everybodyedits.com/img/smilies/wink

#5 Before February 2015

~Omri~
Guest

Re: When bombing goes wrong...

Jojatekok wrote:
DJDavid98 wrote:

I personally agree, tho I never had this issue before.
And by the way, you are not the owner of the level, so... xD
http://i0.kym-cdn.com/entries/icons/ori … tled-1.jpg

I'm not the owner of it, but I can access the owner's account. //forums.everybodyedits.com/img/smilies/wink

OOOOOOOOOOOOOOOOOOOOOOOO NERD HAXXXOR PEW PEW PEW
Well you and proccesor are really good freinds ofc you know each others account,like mihb and mustang

#6 Before February 2015

Mylo
Master Developer
From: Drama
Joined: 2015-02-15
Posts: 829

Re: When bombing goes wrong...

erm think before you write... they dont have any1 acc, how they should.

Offline

#7 Before February 2015

eeplayer17
Guest

Re: When bombing goes wrong...

Well I definitely agree a level owner should never not be able to get into their own level. Maybe have one of the 45 spots reserved for the owner so only 44 people who aren't the owner can be in the level at a time.

#8 Before February 2015

FruitMonster2
Guest

Re: When bombing goes wrong...

Good job with a double negative? But I agree, users should have 110% access to their level, regardless if it's full of people.

#9 Before February 2015

The First Gamer
Guest

Re: When bombing goes wrong...

Actually the maximum amount of people that can join a room these days is around 200, Chris updated the servers a bit of time ago (2-4 months I believe) and it allowed far more people to join rooms.

Though, on a downside, if your connection isn't strong enough, you won't be able to enter worlds with 45+ people in them, this is also the problem Jojatekok is experiencing.

So I cannot entirely assist on these matters, but providing enough information should allow him to make his own solution.

Jojatekok 142390829353139

Board footer

Powered by FluxBB

[ Started around 1731763545.3368 - Generated in 0.045 seconds, 13 queries executed - Memory usage: 1.45 MiB (Peak: 1.58 MiB) ]