Bug: Changing AccountID and ConnectionIP in API: Impact on User Data Consistency
70 °C
Bug #132

Changing AccountID and ConnectionIP in API: Impact on User Data Consistency

Status: Closed
Priority:
Low
Added by:
thisis0144
on September 6, '26
Assigned to:
Unassigned
Due date:
Reported for:
Fixed In Release:
Not set

Steps to Reproduce

No steps to reproduce

Explanation

IUser AccountID & ConnectionIP fields
I understand and appreciate security and stuff you made in >= 1.5.0 versions but I don't get why AccountID and ConnectionIP are not constant. If user rejoins a server they always get a different ip in script api, ok, fair, but whats the point of security in the AccountID field? If I want I can join any server and open any guy steam account from tabscore and using third-party sites I can get their steam ids, but why scripts are no longer able to do this? In previous versions this field had an unique constant for each steam user, in new versions both of these fields are not constant at all, how can I save data of a specific user if I cant get a unique steam id of that user after he rejoins or I rehost server?

Watchers

Screenshots

None

Video Clips

None

Log Files

None

Device

No device information

[ #1 ] by
Loading comments...
Loading comments...
1 comment loaded

You don't have permission to comment on this issue.