MAP - Ballrace: Prism

[CalculatorSpoon]

wo.

[bot]

[ul][li]Card’s description was updated.[/li][/ul]

[CalculatorSpoon]

Wo.

[macdguy]

@bot

Card’s description was updated.

WOOOOOOOOOOOOOOOOOOOO

[Zapty]

[CarsonK]

What had happened that “broke everything” @Madmijk

[CrazyMikeComics]

I’d rather have the gameworld be playable with the risk of a cheater, then keeping it the way it is. It’s unplayable, the host has an advantage and the only way to get units is to play the gameworld with people. Too bad the host is the only one who will have fun.

[Mikusch]

http://upload.mikusch.org/AUMxRC7.mp4

Here’s the sneak peak. Couldn’t find the old thread

[Radek]

This one I guess: GLXY Music pulse

[rileyzzz]

Remember that this game is in Early Access. IIRC they are working on fixing the lag issues.

[Hidari]

Oh my gosh! Boop blocks looks /and/ sounds awesome! I’m so excited right now, I can’t even express it fully.

[macdguy]

@Sgtpanda

Sorry to go off topic

Please don’t go off topic. This is not the place to talk about how Ball Race networking works. I’ve made a lengthy post about it already.

It’s not an easy thing to solve and we’re working on it. That’s the official statement.

---

It’s also not just about cheaters. Making it clientside opens up other issues like how to handle the buttons, how to handle payouts, how to handle a lot of things, and we’d have to recode our networking from the ground up.

Please stop thinking cheating is a small thing that we can easily prevent. Cheating is a legitimate concern because client authoritative means you can easily run a few commands and tell everyone you’ve finished the map and get instant payouts forever. It would make cheating a LOT easier. Yes, there are cheaters right now, but this would make it even worse.

You can’t verify physics simulation from the client on the server. The physics simulation is non-deterministic, meaning it’s pretty random and you can’t predict what it does.

---

Also for Virus read:

Trust the client architecture OR Clientside

This has been a planned feature for a while: https://trello.com/c/mC6cifE4/178-weapon-prediction It’s lower priority than the stuff we’re working on right now, but once we have time we’ll be working on it I assure you. Unreal already does latency compensation for movement, we just need to write a system for weapons. The technique we plan to use is called “Backward Reconciliation”. At a high level, this is the basic premise: The client fires the weapon and FX are played back immediately o…

[GreenGiant]

Keep in mind that the song in the video is not final, but yeah the level looks pretty.

[Hidari]

Yeah, I realized that later, it still looks great though!

[XANA]

Doesnt matter when this comes out frankly: I’ll crush it’s times into the ground like I’ve done for the other maps.

[bot]

[ul][li]“More playtesting” has been checked off on the “Checklist” checklist.[/li][/ul]

[CalculatorSpoon]

oo boy

[Belgo]

sOON

[TJEntertainmentYT]

This level is gonna be hard like midori

[Madmijk]

Just a heads up, this map requires fast response time in regards to physics, because you will be running on blocks that appear and disappear. As a result, it is currently very hard to play (or unplayable in some levels) when you suffer from a moderately high ping.

With this in mind, the map will be released as soon as we get our new Ball Race physics prediction stuff thing implemented (or whatever we will end up doing to make Ball Race great again). How long this will take, I cannot tell. But it is not an option to release this map around this time, as it would only have acceptable gameplay in singleplayer mode. Please understand.

Other than that, the other devs say that the map is very hard, but clearly they just need to git gud.