Opticraft Community

I think that there should be a pedometer function, especially in light of the recent horse update. This would really help people measure track lengths. This would also help people measure block placement for larger builds.

The only two functions necessary would be:
/ped read     -- outputs the number of steps taken since "/ped clear" was typed.
/ped clear    -- restarts the count

Uh, can you explain a pedometer?

Seems like you didn't listen in English class so I'll give the roots.

Pedo = Foot
Meter = Somethig measured(basically)

I really agree with you on here mcoon, and I think this would take away the frustration in most building projects(such as building houses and such like you've said) and could relieve most people, including if you're a "heavy duty" builder.

Quote from: CazualxGrenade on July 02, 2013, 07:20:45 AM
Seems like you didn't listen in English class so I'll give the roots.

Pedo = Foot
Meter = Somethig measured(basically)

I really agree with you on here mcoon, and I think this would take away the frustration in most building projects(such as building houses and such like you've said) and could relieve most people, including if you're a "heavy duty" builder.

So, you're saying that this would ...measure things?! :d I agree. Maybe just give us //wand and //count?

//wand and //count to us Players? Negative. Plus there would be no way staff would give us that.

But anyways this is mcoon's topic not mine right?

Quote from: CazualxGrenade on July 02, 2013, 07:27:46 AM
//wand and //count to us Players? Negative. Plus there would be no way staff would give us that.

But anyways this is mcoon's topic not mine right?

I don't see a problem with it, but meh I see your point. Anyways back ontopic time.
Yeah, I agree with this now.

I'm thinking something as simple as:

[spoiler]float dis=0;
onTick(){
if(upkey.ispresssed) || downkey.ispressed){ if(upkey.ispressed && downkey.ispressed) { } else{ dis+= walkspeed/ticksPerSec;
if(leftkey.ispresssed) || rightkey.ispressed){ if(leftkey.ispressed && rightkey.ispressed) { } else{ dis+= walkspeed/ticksPerSec;
}

void clear(){
 dis=0;
}

void read(){
 cout<<dis;
}[/spoiler]

Simple. Quick. Done.

Quote from: mcoon1 on July 02, 2013, 07:44:46 AM
I'm thinking something as simple as:

[spoiler]float dis=0;
onTick(){
if(upkey.ispresssed) || downkey.ispressed){ if(upkey.ispressed && downkey.ispressed) { } else{ dis+= walkspeed/ticksPerSec;
if(leftkey.ispresssed) || rightkey.ispressed){ if(leftkey.ispressed && rightkey.ispressed) { } else{ dis+= walkspeed/ticksPerSec;
}

void clear(){
 dis=0;
}

void read(){
 cout<<dis;
}[/spoiler]

Simple. Quick. Done.

Wait uhm, with the arrows, are you meaning for WSAD or just a seperate function for the arrow keys?

Ya. Sorry about that. It was pseudocode, afterall.

I was thinking about pedometer. You got me confused for a sec :p

Quote from: raul7legend on July 02, 2013, 08:28:02 AM
I was thinking about pedometer. You got me confused for a sec :p

/pedometer     -- checks for nearby redchecks.

step 1 press F3
step 2 remember your coords
step 3 walk
step 4 check coords
step 5 substract bingo?

isnt this easy enough?

and we have /measure already

Quote from: xDeeKay on July 02, 2013, 08:42:32 AM

Quote from: raul7legend on July 02, 2013, 08:28:02 AM
I was thinking about pedometer. You got me confused for a sec :p

/pedometer     -- checks for nearby redchecks.

You know what, we might actually need a command like that. For restraining purposes :p

Quote from: raul7legend on July 02, 2013, 08:28:02 AM
I was thinking about pedometer. You got me confused for a sec :p

+1
[spoiler]
[/spoiler]

Quote from: Kascas on July 02, 2013, 08:43:52 AM
step 1 press F3
step 2 remember your coords
step 3 walk
step 4 check coords
step 5 substract bingo?

My only problem with this is that it can't realistically measure curved paths, paths that backtrack, or paths that move along more than one axis. the pedometer output could output something like:

[spoiler]total distance: 100m [x:45m, y:50m, z:5m][/spoiler]

...which would be nice, because then you could ignore drops in height, measure drops in height as you descend stairs, you could measure backtrack and curves, etc. all with one tool.