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.
^^
color = #1E1E1E
Offline
Offline
Random guess: always.
Are portals older than bots? If so, when portals were introduced there'd've been no reason to set an ID limit anywhere other than in the in-game portal UI.
One bot to rule them all, one bot to find them. One bot to bring them all... and with this cliché blind them.
Offline
Since this update: https://forums.everybodyedits.com/viewt … p?id=39195
Offline
^ Ah, misleading thread title. Should've been one of:
Q. How long have portals in the game UI been able to hold 99,999 IDs?
Q. How long have portals been able to hold 2,147,483,647 IDs? (Unless that's fixed now. I tested it on 29/10/2017)
One bot to rule them all, one bot to find them. One bot to bring them all... and with this cliché blind them.
Offline
wow
color = #1E1E1E
Offline
Since this update: https://forums.everybodyedits.com/viewt … p?id=39195
False. Since ever. I wouldn't suggest you placing them though, It takes a lot of space in the world.
Offline
LukeM wrote:Since this update: https://forums.everybodyedits.com/viewt … p?id=39195
False. Since ever. I wouldn't suggest you placing them though, It takes a lot of space in the world.
Well yes, but this is in EE Q&A not B&P so they are probably talking about placing them with the client.
Offline
The only way of placing them is modifying the client or using bots. Since you can't place them in official client - i am fine with this
also have you tried placing 0 coins coin gate :^)
Offline
^ Why not just put a serverside cap on portal IDs?
One bot to rule them all, one bot to find them. One bot to bring them all... and with this cliché blind them.
Offline
^ Why not just put a serverside cap on portal IDs?
Idk, doesn't really affect the gameplay much since you can't see ids as a player, but many music bots will run out of ids pretty quickly
Offline
[ Started around 1734036369.7425 - Generated in 0.044 seconds, 15 queries executed - Memory usage: 1.53 MiB (Peak: 1.7 MiB) ]