I fixed the main issue we've been having, but I still can't receive the data by listening to port 4000 on the server. I'll try writing a simple server for It.
Simple networking things
- Internal protocol for networking thread (code that determines what
should be done with the recieved data)
- Networking thread (the meat of the thing)
- Functions to kill, debug and send data to the thread
- That's all I think
To use this:
First start the network thread with the function network() from net.rs
That should start the thread and return a variable "tx" which is the
sender for the thread communication
To use the networking thread, you must use one of the functions in
net.rs related to communication and you must input the necessary values,
the first value is ALWAYS the tx returned by the network() function and
WILL NOT work without it, so the network() function must be called and
within the same scope (where the tx variable containing the sender is)
you must use one of the communication functions
To do (for Dan):
- Networking implementation for the GUI
- Server
- Further expand things that the network thread does (if necessary)
To do (for me):
- Once GUI implementation is finished, properly test the changes
- Probably will have to do debugging idk... suffering...
- VerbenaIDK, yasmina :3
This little bit of ChatGPT code here opens port 4000 (the client-to-server port we're thinking of) and takes a bunch of variables in an array and tells them to the server or as we nicknamed It - whispering to the server.
I added a fix for multithreading {I am actively in pain send help aaaaaaaaaaaa}
Once activated autoclicker now doesn't kill the program instead making a background thread that adds X amount to the current players score.
The thread Is currently not killed upon program close and you should probably not run It, since It leaves a dangling thread.
Cheers
~ Dan
