Cool! I saw you online.
Offline
Magnie wrote:
Cool! I saw you online.
![]()
Yeah...I was bad and forgot to logoff with 'quit'
That is why you must always log off with 'quit'
Offline
ohaiderstudios wrote:
Magnie wrote:
Cool! I saw you online.
![]()
Yeah...I was bad and forgot to logoff with 'quit'
That is why you must always log off with 'quit'
If you create the server with Python instead of MySQL then it can see when you disconnect and it automatically logs you off.
And you can create a Scratch client.
Edit: And if you use a server, you don't need to update the clients as often, since all the new features are on the server.
Last edited by Magnie (2011-12-21 00:01:25)
Offline
Magnie wrote:
ohaiderstudios wrote:
Magnie wrote:
Cool! I saw you online.
![]()
Yeah...I was bad and forgot to logoff with 'quit'
That is why you must always log off with 'quit'If you create the server with Python instead of MySQL then it can see when you disconnect and it automatically logs you off.
And you can create a Scratch client.
![]()
Edit: And if you use a server, you don't need to update the clients as often, since all the new features are on the server.
Yeah I know...maybe...
I might just dump the entire MySQL thing and just make it be a local thing...
Offline
ohaiderstudios wrote:
Magnie wrote:
ohaiderstudios wrote:
Yeah...I was bad and forgot to logoff with 'quit'
That is why you must always log off with 'quit'If you create the server with Python instead of MySQL then it can see when you disconnect and it automatically logs you off.
And you can create a Scratch client.
![]()
Edit: And if you use a server, you don't need to update the clients as often, since all the new features are on the server.Yeah I know...maybe...
I might just dump the entire MySQL thing and just make it be a local thing...
You don't need to drop the entire thing, you could still use the same concept of how you set up the MySQL database. ( Though I haven't found a simple way to decompile the code, so I don't know much about any of the code.
)
Offline
Magnie wrote:
ohaiderstudios wrote:
Magnie wrote:
If you create the server with Python instead of MySQL then it can see when you disconnect and it automatically logs you off.And you can create a Scratch client.
![]()
Edit: And if you use a server, you don't need to update the clients as often, since all the new features are on the server.Yeah I know...maybe...
I might just dump the entire MySQL thing and just make it be a local thing...You don't need to drop the entire thing, you could still use the same concept of how you set up the MySQL database. ( Though I haven't found a simple way to decompile the code, so I don't know much about any of the code.
)
Hooray to the not being able to decompile the code!!!
If Magnie can't do it, nobody can!
jk
Offline
ohaiderstudios wrote:
Magnie wrote:
ohaiderstudios wrote:
Yeah I know...maybe...
I might just dump the entire MySQL thing and just make it be a local thing...You don't need to drop the entire thing, you could still use the same concept of how you set up the MySQL database. ( Though I haven't found a simple way to decompile the code, so I don't know much about any of the code.
)
Hooray to the not being able to decompile the code!!!
![]()
If Magnie can't do it, nobody can!
jk![]()
Well, I can't do it with just 7Zip and observation. I haven't tried looking for a Python Decompiler. Though I can see which modules you use.
Offline
I clicked on this when I saw MMOTBG - it was confusion with other TBGs...
Offline