In the Tanks client New() proc, I check the client passport as follows:
if(CheckPassport("Tanks passport number")) subscriber = 1
// misc. stuff
if(subscriber)
src << "You are a Tanks subscriber. Thank you for your support!"
Whenever I host, it checks out fine. If I host on a dummy key and log in as my primary, it checks out fine. If I log into someone elses game online, it never flags client.subscriber. It's not just that the message does not display. I can't access anything that requires client.subscriber to be 1.
ID:150506
 Sep 10 2001, 6:13 pm
|
|
Deadron wrote:
This sounds similar to the problem Tom had with DragonSnot. I remember reading the post long ago, but I wasn't worried about subscriptions then and assumed it would be fixed by the time I was. I can't find the post now. Is there some way to repair this, or do I just wait? | |
Are you sure the other person hosting the game was running version 304? Earlier versions did not include support for passport checking.
--Dan | |
I have version 304, and if I hosted with a key that didn't have a subscription my primary key couldn't use it's subscription. I haven't test with a secondary key with a subscription yet. Should I?
| |
Abracadabra! CheckPassport() should work for remote clients now. The only catch: due to a bug in DreamSeeker, I cannot force re-authentication of cached passport data from the hub. If you still have problems, you will need to manually remove the following file: <code>Byond/users/windows-login/cfg/cauth.txt</code> If you still experience problems after that, then I definitely want to hear about it! --Dan | |
This sounds similar to the problem Tom had with DragonSnot.