Need help with saving data

If you only have this one action serverside then the client will always return the same id thus overwriting the current ini.

What I would do is this:
--> Save INI to file (Filename: peername.ini)

This would then create an ini file based upon the peer's name which would be more unique than peer ID. I hope I understood your post correctly and this is helpful, if not let me know...

Why use more than one file instead of groups?

Set Item "Userpassword" in Group "Client_Name$( "Lacewing Relay Server" )" to received text.

The Ini file will look like this:

[peername]
Userpassword=whatever
[anotherpeername]
Userpassword=whatever

Or am i completely missing the point?

blub, I think it's jut preferable to save each user's data into their own file... It makes more sense because you won't have a gigantic single file representing all users, and if you need to review/modify a user's data, it's super easy to just locate their file and modify only that instead of having to modify the giant file that contains every person's data. I'm pretty sure he means he wants to save all of the user's data to these files... like health or score or stats or whatever... So having a hundred lines of text for each player in a single text file would be unwise.

Hydra, I think you just need to make sure you're setting to the right INI file when you save/load data. Also you should definitely be saving the INI file as the account name for the player, as ByteDex suggested.

I've set up a user login/account system using Lacewing already and this is how I did it. Basically the user creates a username/password which is then created in a mysql database. When the user logs in, I'm using Get object to actually retrieve the database info to make sure the password and such is accurate. Then it uses that username that was accepted as the account username for that person, and will then access the proper accountname.ini file from the server for that specific user.

You have to just make sure that you are pointing toward the right INI file whenever you are saving/loading user data... otherwise it's using whatever ini file was initially set. (in this case, the first player that logged in)

Quote

I know im a complete noob, but i cant figure out this lacewing server extension. When I host on port 6121, clients cannot connect.

You have to open/forward the port on your router.

And your attachment doesn't work.
"Invalid Attachment specified. If you followed a valid link, please notify the administrator"

Can you reupload it?

If you are familiar with using SQL, it better better to save everything into a sql database. If not you can still use the ini object:

The Problem: As you are writing to the ini object, it is an use when another player saves their data.

Solution:

Objects You Need: String Parser, list box

(Not all the actions are by exact expression name

On the client end:

1. Start of frame ------> Send "1" + "-" + "LaceWingSelfName"

(1 would be you data. "-" would be your parsing character for the string parser object. The lacewing Self Name, is the name you have chosen in lacewing for your player

Server Side:

1. On text received on subchannel - Insert line 'LaceWing Text Received' from line -1)

(You want it to insert into line -1 at the end. We are creating a que list.

2. If Number of Lines of List Box is Greater than 0 - Set current line to 1 / Set Delimiter to "-" / Set Source String to Current Line / Delete Current Line, Set Global Value A to 1
Global Value A = 0

3. If Global Value A = 1 - Set Group "Data" Set Item to "Element 2 of string parser" / Set String to "Element 1 of string parser" / Save ini / Set global value to 0

The list box on the server will keep a constant que, any lines collected in it will handled when the lines in the list box are greater than 0.

Global value A of 1 will take that information and save it to your ini object, at a one at a time basis.

If you use a fast loop, the que will be emptied in no time.

-Mike

MikeB, Lacewing already queues messages, so your solution is not necessary at all. :p

If 5 people save at the same time, Lacewing would save each person's data one at a time over 5 game loops.

This definitely just sounds like an issue of the INI++ file not being set properly to each player's account name when saving data. I'd be happy to take a look at the file if it was re-attached.

edit: also saving everything to SQL is not practical in most online game situations. SQL databases aren't the fastest things in the world, you know :p

Do you have the server sending data to itself? Shouldn't the client send stuff be in the client app?

Oh I see, so the client/server is the same app, just one is dedicated to hosting while the others connect... Right.

I'd have to actually look at the app to help out, I think.

INI++ can definitely save multiple INI files, so fear not. This is fixable.

What you described is pretty much how it's done. Just walk through the steps and test each bit... First see if the server receives the message, then test if the server is loading the data from the proper peer name, then see if the server is sending the data to the player, then you can figure out if the data is correct.

It's just:

1. player tells server "hey I'm here, send me info"
2. server receives message, grabs the info, sends it to player
3. player receives
4. profit!

To send multiple numbers you can just add them to a stack and blast it.

On the other end you'd get them by their index. Again, you'll want to watch DizzyDoo's video on stack messages to understand what's going on with them.