[DiscordArchive] how it is right now it just goes through the table and returns the tickets with the players guid rig
[DiscordArchive] how it is right now it just goes through the table and returns the tickets with the players guid rig
Original source
I mean the c++ one you have to update and modernize and sometimes that changes over time or core swaps
rektbyfaith
01-12-2023, 01:06 AM #31Archived author: Crow • Posted: 2023-01-12T01:06:28.050000+00:00
Original source
I mean the c++ one you have to update and modernize and sometimes that changes over time or core swaps
Original source
also I just dont understand it
rektbyfaith
01-12-2023, 01:06 AM #32Archived author: Crow • Posted: 2023-01-12T01:06:35.490000+00:00
Original source
also I just dont understand it
Original source
Lua is way easier to read and i can load it on the go
rektbyfaith
01-12-2023, 01:06 AM #33Archived author: Crow • Posted: 2023-01-12T01:06:45.274000+00:00
Original source
Lua is way easier to read and i can load it on the go
Original source
The big pointers I'd give about being careful when using lua is
1. Database Calls (Make sure they're cold paths, i.e happens only when absolutely necessary, typically with player interactions that could be on login/logout, or store the information in a table that is pushed to the database upon reload or shutdown, although that could lead to data loss in case of crashes)
2. Poorly scaling code (Especially for gameplay code, make sure you do as few operations as possible)
3. Don't polute the global space (Unless you understand fully what it is you're doing, everything is a local)
If you follow those guidelines (I'm sure more routined Lua users may have more), you should find yourself in a manageable situation in regards to performance
rektbyfaith
01-12-2023, 01:07 AM #34Archived author: Nix • Posted: 2023-01-12T01:07:34.727000+00:00
Original source
The big pointers I'd give about being careful when using lua is
1. Database Calls (Make sure they're cold paths, i.e happens only when absolutely necessary, typically with player interactions that could be on login/logout, or store the information in a table that is pushed to the database upon reload or shutdown, although that could lead to data loss in case of crashes)
2. Poorly scaling code (Especially for gameplay code, make sure you do as few operations as possible)
3. Don't polute the global space (Unless you understand fully what it is you're doing, everything is a local)
If you follow those guidelines (I'm sure more routined Lua users may have more), you should find yourself in a manageable situation in regards to performance
Original source
True <a:aPES_FastParty:656893193757130762>
rektbyfaith
01-12-2023, 01:07 AM #35Archived author: Nix • Posted: 2023-01-12T01:07:50.992000+00:00
Original source
True <a:aPES_FastParty:656893193757130762>
Original source
I mean, the global variables are still "local" no?
rektbyfaith
01-12-2023, 01:08 AM #36Archived author: Crow • Posted: 2023-01-12T01:08:05.938000+00:00
Original source
I mean, the global variables are still "local" no?
Original source
Global means you don't define it as a local
rektbyfaith
01-12-2023, 01:08 AM #37Archived author: Nix • Posted: 2023-01-12T01:08:20.574000+00:00
Original source
Global means you don't define it as a local
Original source
did I fail to understand that
rektbyfaith
01-12-2023, 01:08 AM #38Archived author: Crow • Posted: 2023-01-12T01:08:22.068000+00:00
Original source
did I fail to understand that
Original source
oh
rektbyfaith
01-12-2023, 01:08 AM #39Archived author: Crow • Posted: 2023-01-12T01:08:30.657000+00:00
Original source
oh
Original source
If it has local in front of it, it cannot be a global
rektbyfaith
01-12-2023, 01:08 AM #40Archived author: Nix • Posted: 2023-01-12T01:08:33.886000+00:00
Original source
If it has local in front of it, it cannot be a global
1 Guest(s)
1 Guest(s)