04.07.2018, 10:31
Well you may think dini or yini is easyer to learn and use. And while that is True in some way, I tell you from experience that Its easyer to create something using sql. a while ago I didnt knew How to realise some things and had given it up. With sql it was so easy to do. Sql offers u alot more functionalist and it is not that hard to learn at all.
Example: my character system
I had No idea on How to do this. When I learned sql and thinked it over I figured I can make it like this and it works perfect:
Table with users and characters.
Field called userid in characters table.
So when a player logs in, I save his id from db in userid[playerid] and can Now simply use " SELECT FROM characters WHERE ID = userid[playerid]"
So think it over before u use dini or other glitchy saving systems. Im also pretty sure that if u wont use sql Now, u update it to sql later on anyway. I get weekly jobs from this community to convert a y ini/dini mode into sql..
Example: my character system
I had No idea on How to do this. When I learned sql and thinked it over I figured I can make it like this and it works perfect:
Table with users and characters.
Field called userid in characters table.
So when a player logs in, I save his id from db in userid[playerid] and can Now simply use " SELECT FROM characters WHERE ID = userid[playerid]"
So think it over before u use dini or other glitchy saving systems. Im also pretty sure that if u wont use sql Now, u update it to sql later on anyway. I get weekly jobs from this community to convert a y ini/dini mode into sql..