In order to change this, Steam requires you to start spending money. That means that they cannot send requests to friends and add friends on Steam or access certain parts of Steam. So in summary, there's lots of room to give multiple instances really unique id's.Currently, new Steam users, when they create a new account, are given limited accounts. There's also account types, AnonUser or MultiSeat might be something of interest, or yet again, make your own type.
Gmod uses steam universe 0 today, newer source1 games use 1, you could choose to use your own universe id, like 10. If you really want to go the SteamID way, make full use of the SteamID space. You could try UniqueID which should give you a different result even on multiple instances, then there's also a per-IP approach (which in your case might not actually work, you'd need more of a client port approach, not sure if you can get that without a c++ module) There are multiple ways to store data for players with the same SteamID. Since SteamID64() returns a string, and that number can't accurately be represented by a double anyway, just return SteamID(). OldPlayerMetatableSteamID( self)Įnd function FSI. Local fakeSteamID = self: GetNetworkedString( "FakeSteamID ") Ply: SetNetworkedString( "FakeSteamID ", fakeSteamID) OldPlayerMetatableSteamID(ply) = "STEAM_0:0:0 " then local userId = ply: UserID() - User ID is unique for the current session.
If this is a duplicate player, assign a unique SteamID (for this session). Add( "PlayerInitialSpawn ", "FSI.PlayerInitialSpawn ", function( ply) PlayerMetatable = FindMetaTable( "Player ")įSI. If SERVER then SetGlobalBool( "IsLanServer ", GetConVarNumber( "sv_lan ") ! = 0)Įnd if GetGlobalBool( "IsLanServer ") ! = 0 then - sv_lan is not replicatedįSI.
And this is a nightmare because I need to scrape the last few friends to test. This wouldn't just be a little helpful, it'd be extremely helpful.Īs a use case, I'm currently working on a custom prop protection, and currently working on allowing players to request permissions from other players, which other players can then grant or deny. This could be accompanied by something like sv_allowduplicateplayers or sv_allow_multiple_connections_from_same_user_without_forcing_them_to_lose_friends but these could be changed to append a value, eg. I understand there'd be a couple of complications like player:SteamID(), player:SteamID64(), etc. It'd be nice if we could run multiple game instances on the same PC for testing purposes. And asking friends to test, is a good way to lose friends.Īnd since bots can't do everything, they're not useful for most scenarios. However, it's cumbersome to test multiplayer related code because you need a real person to help you. Working on a gamemode and (unrelated) addon, and auto refresh is extremely useful.
0 kommentar(er)
