Programming advice for ZOS

Donny_Vito

Dojohoda wrote: »

I'm not a programmer but I can attempt to play along.

If hampster = slow, retire hampster, + fresh hampster.

please overlook and carry on.

Hah, are you implying the ZoS servers are ran by hamsters??

Alinhbo_Tyaka

I thought it was prepping us for a new Equestrian circus act they plan to introduce in an ESO circus DLC.

JimmyJuJu

Runefang wrote: »

marlonbrando wrote: »

JimmyJuJu wrote: »

How about this instead:

If not_in_combat
then allow_mount = true
end

I mean, FFS...it's been 5 years guys - can you please fix this one already? Thanks.

Or even,
if (last_damage_time() - current_time()) > 60 then
cancel_in_combat()
end

So you want the server to check this every... millisecond? every second? For every player? And it effectively needs to record each time you receive damage with a time stamp in order for the formula to work.

Congratulations you’ve killed the server.

Really, just remove the condition to mount while in combat. I've personally always thought this to be an unnecessary restriction. So what if some guy at 1% HP mounts and runs off. That's what would happen IRL anyway and would make combat more realistic.

Dojohoda

Donny_Vito wrote: »

Dojohoda wrote: »

I'm not a programmer but I can attempt to play along.

If hampster = slow, retire hampster, + fresh hampster.

please overlook and carry on.

Hah, are you implying the ZoS servers are ran by hamsters??

I hope they've checked for 3-legged hamsters.

Seriously though, I hope they have success with sorting out the issues.

MongooseOne

Anytime this has happened to me I simply jump and I plop back down in the saddle.

Drako_Ei

marlonbrando wrote: »

Or even,
if (last_damage_time() - current_time()) > 60 then
cancel_in_combat()
end

If i take damage at 10 seconds, and 100 seconds have passed, so now its 110 seconds, then it becomes...

if (-100 > 60) then
cancel_in_combat() //never executes
end

It has to be: current_time()-last_damage_time()...

Because as it is... it would cause an infinite incombat bug...

...you are qualified as a ZoS programmer, congratulations.

Drako_Ei

validifyedneb18_ESO wrote: »

How people thing a single if statement is somehow going to drag server performance down, I have no damn clue.

Every physics simulated item in the game has to do 3 floating point integer comparisons, against every other static or otherwise object in the scene every physics frame. And that is just AABB pre-checks.

But no, comparing 1 global integer against a local player integer, once per player per frame, waaaay too much for the servers to handle.

Lets not talk about the matrix multiplications when projecting aoe on the ground, every cast, or knowing zos... every tick

marlonbrando

redlink1979 wrote: »

Really, just remove the condition to mount while in combat. I've personally always thought this to be an unnecessary restriction. So what if some guy at 1% HP mounts and runs off. That's what would happen IRL anyway and would make combat more realistic.

Either that or make it take, I dunno, 30 seconds to mount if you're in combat? Assuming you really must have some kind of penalty for some reason.

It never made sense to me that you can ride while in combat but can't get on your mount while in combat.

Don't quite understand why you can't mount on the porch of a keep either.

marlonbrando

Drako_Ei wrote: »

marlonbrando wrote: »

Or even,
if (last_damage_time() - current_time()) > 60 then
cancel_in_combat()
end

If i take damage at 10 seconds, and 100 seconds have passed, so now its 110 seconds, then it becomes...

if (-100 > 60) then
cancel_in_combat() //never executes
end

It has to be: current_time()-last_damage_time()...

Because as it is... it would cause an infinite incombat bug...

...you are qualified as a ZoS programmer, congratulations.

Yes, you're right, my mistake, it should have been current_time() - last_damage_time().

I'm one of those rare people who makes programming errors.

LadySinflower

Versispellis wrote: »

https://www.youtube.com/watch?v=OpidGiBemJ4

I think it's just a feature at this point.

That's the weirdest looking treadmill I've ever seen!

Seriously, skyrim is doing it now too? (It never happened to me when I played Skyrim.)

marlonbrando

Elsonso wrote: »

That is not the source of the performance problems.

This is

/* DevGuy  20130423 - remove the following line in 2015 to increase performance */
sleep(1000)

They still haven't done that.

Just think: If they made that sleep(500) they could potentially *double* performance.