AREAS_USE_TIMER: It exist, but is not allowed? about ysi-includes

[Misiur]

It seems the OPU doesn't have any kind of rate limiter. I think we could try something like

#if defined AREAS_USE_TIMER
    ptask Area_Loop[200](playerid)
#else
    hook OnPlayerUpdate(playerid)
#endif
{
//(...)
}

And use code from OPU.

[Crayder]

It looks like it could work, but I wonder what he was planning there...

[Y-Less]

I planned many many things, then frequently forgot them and came back years later only to wonder why I left code half finished in a weird way... I can only assume that it was done thins way for response times, but OPU is most likely overkill.

The best thing to do in cases like that is look at old versions. If a feature is never completed it likely won't give an error, it just won't be usable at all. If you get a compiler error for certain settings it usually means that it used to work but I removed it for some reason and wanted to alert anyone that was using that method.

[Misiur]

All I could find was initial commit, and pawn-lang/YSI@1286b8d . @Crayder if you are interested, just try using the current OPU body but with timer, then run the YSI-Test-Suite or test ingame.

[Y-Less]

Check the "master" branch from before files got moved about - a lot of data appears to be an initial commit when it isn't because earlier commits were in a different place. Git can't handle file renames, it does them as a delete and an add so there's no way to see the continuation between the two.

[Misiur]

There's only "first commit" before that with single README file, so before 14 april 2012 there's no more history :(