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.

Advertisement

Hello, visitor! These forums are run off of the revenue generated from these ads. If you'd like to support us, please whitelist us or consider donating:

#1 2019-01-07 03:48:26

Slabdrill
Formerly 12345678908642
From: canada
Joined: 2015-08-15
Posts: 3,012
Website

player-made speedruns

Allow players to enable the timer in any world with /starttrial, even if there aren't any time goals available. I know it's possible with /info, but starttrial puts the timer in a bigger out-of-game location.
Allow crew members with "world options" to set trophy times. These trophies are not actually saved with the player, but it gives a concrete sense of speedrun progress.
As there's no reward for speedrunning, there doesn't need to be a check for whether a time is possible or not.

Last edited by Slabdrill (2019-01-07 05:34:05)


suddenly random sig change

Offline

#2 2019-01-07 05:31:45

mikelolsuperman
Member
From: Under your bed
Joined: 2016-06-26
Posts: 1,010
Website

Re: player-made speedruns

This would be nice and since there are no rewards or anything it wouldn't be too unfair to make a level with invisible portals in weird spots that you don't come across when speedrunning it. Would work well with the suggestion of having the speedrun times in ee itself when enabled in settings. For campaigns it would need an anticheat otherwise someone could just use some hack to go faster or teleport or whatever and since you (as far as I know) can't speedrun an incomplete level the anticheat doesn't see if you cheated or you actually did the campaign the legit way as it's just treated as a normal level after that.


Blue is my favourite color

I also like lasagna, but not when it's blue

Offline

mikelolsuperman1546835505737882

Board footer

Powered by FluxBB

[ Started around 1553338263.1137 - Generated in 0.018 seconds, 12 queries executed - Memory usage: 1.23 MiB (Peak: 1.33 MiB) ]