You can modify the blips to your liking, everything is accessible.
(Script was made in like 15 minutes, it was for a friend that needed it, so I also decided to release it for free)
| Code is accessible | Yes |
| Subscription-based | No |
| Lines (approximately) | 100 |
| Requirements | es_extended |
| Support | Yes |
This won’t work with onesync enabled servers
Are you sure, because I didn’t test this…? These are just normal blips
The Issue is that this adds blip on entity in the client side, so if the player distance is above the limit set by onesync for entities then no such entity will exist in the client to add a blip for.
But if you read the source code, you’ll see that it doesn’t attach the blip to entities. It creates normal blips (the ones you’d use for different locations…)
You get player source ids from the server, and you send it every 3 seconds to the client (3 seconds by default). Afterwards, you get the player from the server id in the client, you get coordinates for every one of them and just display it as a normal blip. If OneSync does not render normal blips, than I’m mistaken. 
You can see here you get the coords from the client using the ped fetched from client
Here the optimal way is to get the ped coords from server in a loop and send it to client
Yes, that would also make sense, but then you’d have to run the loop in server as well.
I did a PR in github you can check it
Good job!