hi,

so currently in samp you have vehicle ids the problem is that they could potentionally change and another vehicle takes over that id which may not be wanted. So im suggesting some sort of unique id for vehicles that will always (unless DestroyVehicle, FS /GM Unload happens) "point" to that specific vehicle no matter what happens. This could be added in the /dl command and with GetVehicleUID you could retrieve it.

samp-precise-timers ?
github.com/bmisiak/samp-precise-timers


Briefly
Developed for net4game.com (RolePlay), this plugin provides precise timers for the server. It is written in Rust, a memory-safe language.

Why rewrite timers?
I had a lot of safety concerns with some of the existing solutions. They weren't written with data integrity, memory safety or preventing server crashes in mind and seemed to have quite a few bugs. As privacy and safety is our primary concern at net4game, I wrote this in Rust, which combines high-level ergonomics with the performance of a low-level language. ?

Please check out the code to see the benefits. You might like Rust a lot. The code is much simpler than C equivalents, especially the ones which still use *char, free() and delete[] instead of modern C idioms such as std::unique_ptr, but as Rust has no runtime, there is no overhead ??

We would like your help! ??
Oh, and if you enjoy working on servers, we are looking for a team to help our international expansion. ??? net4game has been around for a decade as the biggest Polish server. We introduced a lot of innovations over the years and we are almost ready to become international. Shoot me an e-mail at [email=bm犇@net4game.com]bm犇@net4game.com[/email] if you're interested.

Downloads on GitHub
Also available on sampctl as

Selam.?

They broken

Hola comunidad lo que vengo a presentarles es un creador de TextLabels y Dialog por web,?tambien nos permite ver como va quedando cr?ditos?al creador _Zume.

Quote:Most people here know "Bullworth Town", and have played this great game, but hey, that is not the important thing in this thread.

I discovered that some people wanted to launch the map of this game on their servers, but the conversion for sa: mp did not exist, some servers work to convert this map and others doknow how to do it. I am doing this conversion, since I am possibly going to publish it at the end of the month (June), this is for people who are interested in using this place.



If you want to have more information about the conversion of this map, you can access my Discord.

I don't?know what other information to provide, but hey, I'll be adding updates to this thread over time.

Will o:mp be featured in?Discord Rich Presence ? So we can say like wich server we are on and server infos and some other infos?

I've installed the 5.x branch of the YSI library to get rid of the pesky const correctness warnings and followed the instruction of changing the syntax to include y_hooks in all my files and this was the result

Right, so I've been thinking about y_hooks.

This is the current syntax:

1. Exactly what's above, just an obvious function call. ?This has several downsides - verbose, variable parameters, string argument specifier (error-prone), string function name; and only one upside - not custom syntax.
   
   
2. Using indirection.inc with the hook name:
   
   
   PHP Code:

   return @.OnPlayerConnect(playerid); 

   
   Advantages: Established syntax, compile-time specifier determination (can be part of the `hook whatever` line, don't worry about that), less verbose, more clear.
   
   Disadvantages: Still no compile-time parameter checking, but none of the proposals have that.
   
   
3. Using indirection.inc with the `hook` keyword:
   
   
   PHP Code:

   return @.hook(playerid); 

   
   Basically the same as option "2", but more consistent across all hooks, and less likely to conflict with other variables. ?As for specifiers, there are two options - 1) none, which is not good, but means that the chaining is no longer tied to the hook function:
   
   
   PHP Code:

   Other(a)
{
    return @.hook(a);
}

hook stock MyFunc(a)
{
    return Other(a);
} 

   
   Or the other option is just make `hook` a local in exactly the same way as would be done in option "2a".
   
   
4. `continue`.
   
   I like this for one reason - it is quite clear on meaning:
   
   
   PHP Code:

   hook stock MyFunc(a)
{
    new b = continue(a  5);
    return b - 5;
} 

   
   `continue()` cannot conflict with `continue`, so this is a completely unambiguous overload of an existing keyword.
   
   
5. `hook continue`.
   
   Like "4", but using slightly more verbose, less confusing, syntax:
   
   
   PHP Code:

   hook stock MyFunc(a)
{
    new b = hook continue(a  5);
    return b - 5;
} 

   
   
6. `yield continue`.
   
   Again, like "4" and "5", but reusing the `yield` keyword, already existant in YSI. ?`y_iterate` uses `yield return`, so this would provide meaning to `yield continue` as well:
   
   
   PHP Code:

   hook stock MyFunc(a)
{
    new b = yield continue(a  5);
    return b - 5;
} 

   
   
7. Completely custom syntax:
   
   
   PHP Code:

   hook stock MyFunc(a)
{
    // Example custom syntax, probably not this, maybe `next()`.
    new b = next_hook::MyFunc<>!!!(a  5);
    return b - 5;
} 

   
   
8. Something I've not thought of.
   

Well i done this?


It isnt that great but just to give some ideas
Well i can explain what it stands for
The burger u know the burger and a scope aim for shot so burgetshot

Tried to do something like this

Burgershot old school