Illegal Exit 04
Moderator: Light
Re: Illegal Exit 04
Yes! I got a spot awesome.
(Hint to people who want to play but didn't sign up: sadly, there's a chance I won't make the tourney. But I hope I will.)
(Hint to people who want to play but didn't sign up: sadly, there's a chance I won't make the tourney. But I hope I will.)
Re: Illegal Exit 04
And this is precisely why I have extra spots on the sign-up page.Titanoboa wrote:...sadly, there's a chance I won't make the tourney.
Re: Illegal Exit 04
Shit, I missed it!
Can anyone sign me up for one of those extra spots? I'd really like to play
Can anyone sign me up for one of those extra spots? I'd really like to play
Re: Illegal Exit 04
You didn't miss anything. Just sign yourself up whenever you get the chance.
Re: Illegal Exit 04
I'm having thoughts about the flow of the tournament. Right now the rules are: matches end at 10 points, first to win 2 matches is the victor. But it's really hard to gauge how long that's going to take. It could be over in 15 minutes or it could take an hour. I think I have a better plan.
I would like to make this a timed event. No score limit, and a singe 30 minute match. Who ever has the most points at the end wins the game (and I can record these scores in the history if I remember to get a screenshot). I think 30 minutes is long enough to make it worth showing up, but no so long that people get bored and tired. Quick and fun tournament.
Also, if you want to get a feel for it, I've attached settings for local play. Because 12 players is a lot, size_factor is now -2 instead of -3 (which is what we use for half the players).
I would like to make this a timed event. No score limit, and a singe 30 minute match. Who ever has the most points at the end wins the game (and I can record these scores in the history if I remember to get a screenshot). I think 30 minutes is long enough to make it worth showing up, but no so long that people get bored and tired. Quick and fun tournament.
Also, if you want to get a feel for it, I've attached settings for local play. Because 12 players is a lot, size_factor is now -2 instead of -3 (which is what we use for half the players).
- Attachments
-
- settings.cfg.not.zip
- rename to settings.cfg
- (2.5 KiB) Downloaded 137 times
- ItzAcid
- Match Winner
- Posts: 511
- Joined: Tue Feb 09, 2010 7:16 am
- Location: I reside in your mind.
- Contact:
Re: Illegal Exit 04
I think that's going to be a great adjustment. Looking forward to it
Won Tourneys/Competitions: WWG4 (Hmm, need more braggage like Durka)
Oo oO
Oo oO
-
- Match Winner
- Posts: 638
- Joined: Mon Jun 14, 2010 5:36 am
Re: Illegal Exit 04
maybe add a round time limit too, because if somebody's ahead and they're one of the last two, they could technically wait it out until the end of the 30 minutes
- compguygene
- Adjust Outside Corner Grinder
- Posts: 2342
- Joined: Thu Aug 21, 2008 12:09 pm
- Location: Cleveland, Ohio
- Contact:
Re: Illegal Exit 04
I am working on a multi-mode incam server. I was reading through the settings you just posted, and I wondered what CYCLE_WALL_NEAR does?
Armagetron: It's a video game that people should just play and enjoy
https://bit.ly/2KBGYjvCheck out the simple site about TheServerPharm
https://bit.ly/2KBGYjvCheck out the simple site about TheServerPharm
Re: Illegal Exit 04
In these settings, it's set to 4, which means if you're closer than 4 grid units to a wall, you accelerate, otherwise not.help text wrote:CYCLE_WALL_NEAR (Maximum accelerating wall distance)
- Phytotron
- Formerly Oscilloscope
- Posts: 5041
- Joined: Thu Jun 09, 2005 10:06 pm
- Location: A site or situation, especially considered in regard to its surroundings.
- Contact:
Re: Illegal Exit 04
Are you sure it's grid units?
It's also, hmm, what's the term.... As we all have surely noticed, the closer you are to a wall (within that value), the greater the influence of the acceleration. There's a term for that.
But what also seems to happen as you raise or lower that value, is that it affects that influence. So, for example, Shrunkland has _NEAR 8 (as all the Breakfast servers had, I think), which means that you'll catch acceleration at a greater distance from the wall. But it also seems to increase how strong the acceleration is when you're right up on a wall. A low _NEAR seems to not only require you to get closer before acceleration kicks in, but also make acceleration weaker once it does. So, at the same distance from a wall, a higher _NEAR will provide greater rate of acceleration than a lower one. I think. Or, I could be delusional.
Z-Man?
EDIT: Wait a minute. Scratch that, reverse it.
It's also, hmm, what's the term.... As we all have surely noticed, the closer you are to a wall (within that value), the greater the influence of the acceleration. There's a term for that.
But what also seems to happen as you raise or lower that value, is that it affects that influence. So, for example, Shrunkland has _NEAR 8 (as all the Breakfast servers had, I think), which means that you'll catch acceleration at a greater distance from the wall. But it also seems to increase how strong the acceleration is when you're right up on a wall. A low _NEAR seems to not only require you to get closer before acceleration kicks in, but also make acceleration weaker once it does. So, at the same distance from a wall, a higher _NEAR will provide greater rate of acceleration than a lower one. I think. Or, I could be delusional.
Z-Man?
EDIT: Wait a minute. Scratch that, reverse it.
Last edited by Phytotron on Wed Feb 15, 2012 2:39 am, edited 1 time in total.
- Jonathan
- A Brave Victim
- Posts: 3391
- Joined: Thu Feb 03, 2005 12:50 am
- Location: Not really lurking anymore
Re: Illegal Exit 04
Increasing CYCLE_WALL_NEAR will always lead to more acceleration. The slope is even identical. There is suddenly a good amount of acceleration coming out of nowhere with small CYCLE_WALL_NEAR, which may be what you're experiencing. You can compensate by decreasing CYCLE_ACCEL_OFFSET, which makes for steeper acceleration near the wall.
The basic equation, before any modifiers are applied:
acceleration = CYCLE_ACCEL * (1 / (distance + CYCLE_ACCEL_OFFSET) - 1 / (CYCLE_WALL_NEAR + CYCLE_ACCEL_OFFSET))
The basic equation, before any modifiers are applied:
acceleration = CYCLE_ACCEL * (1 / (distance + CYCLE_ACCEL_OFFSET) - 1 / (CYCLE_WALL_NEAR + CYCLE_ACCEL_OFFSET))
ˌɑrməˈɡɛˌtrɑn
- Phytotron
- Formerly Oscilloscope
- Posts: 5041
- Joined: Thu Jun 09, 2005 10:06 pm
- Location: A site or situation, especially considered in regard to its surroundings.
- Contact:
Re: Illegal Exit 04
Ah, you posted while I was editing, heh. I was just in Shrunkland checking if my recollection was correct, and turns out it's the reverse. Doh! So, everyone, reverse what my edit describes and you'll get what Jonathan is replying to directly to me. The edited version now properly describes my experience. Everyone following? Heh.
- Jonathan
- A Brave Victim
- Posts: 3391
- Joined: Thu Feb 03, 2005 12:50 am
- Location: Not really lurking anymore
Re: Illegal Exit 04
I declare you not the king of page breaks, but king of edits!
By the way, CYCLE_WALL_NEAR and CYCLE_ACCEL_OFFSET are really in grid units. Well, actually, the distance to walls is measured diagonally backwards. But the sideways distance is still what matters.
CYCLE_WALL_NEAR is where acceleration begins.
-CYCLE_ACCEL_OFFSET is where acceleration is infinite.
The above is applied by translating the basic reciprocal function only; its scale is left intact.
CYCLE_ACCEL scales the result. It can't be defined as concretely as the other settings. This is about as close as you can get to capturing its essence:
acceleration at distance (1 - CYCLE_ACCEL_OFFSET) = CYCLE_ACCEL * (1 - 1 / (CYCLE_WALL_NEAR + CYCLE_ACCEL_OFFSET))
Or: d/ddistance (acceleration at distance (1 - CYCLE_ACCEL_OFFSET)) = -CYCLE_ACCEL
By the way, CYCLE_WALL_NEAR and CYCLE_ACCEL_OFFSET are really in grid units. Well, actually, the distance to walls is measured diagonally backwards. But the sideways distance is still what matters.
CYCLE_WALL_NEAR is where acceleration begins.
-CYCLE_ACCEL_OFFSET is where acceleration is infinite.
The above is applied by translating the basic reciprocal function only; its scale is left intact.
CYCLE_ACCEL scales the result. It can't be defined as concretely as the other settings. This is about as close as you can get to capturing its essence:
acceleration at distance (1 - CYCLE_ACCEL_OFFSET) = CYCLE_ACCEL * (1 - 1 / (CYCLE_WALL_NEAR + CYCLE_ACCEL_OFFSET))
Or: d/ddistance (acceleration at distance (1 - CYCLE_ACCEL_OFFSET)) = -CYCLE_ACCEL
ˌɑrməˈɡɛˌtrɑn