[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
how it is right now it just goes through the table and returns the tickets with the players guid right?
rektbyfaith
01-12-2023, 01:00 AM #1Archived author: Crow • Posted: 2023-01-12T01:00:06.048000+00:00
Original source
how it is right now it just goes through the table and returns the tickets with the players guid right?
Original source
I also don't like the use of for i = 1, size of table in Lua
rektbyfaith
01-12-2023, 01:00 AM #2Archived author: Foe • Posted: 2023-01-12T01:00:23.449000+00:00
Original source
I also don't like the use of for i = 1, size of table in Lua
Original source
My suggestion really is a matter of "proper and scalable code" compared to "trashy and easy to bottleneck code"
rektbyfaith
01-12-2023, 01:00 AM #3Archived author: Nix • Posted: 2023-01-12T01:00:33.134000+00:00
Original source
My suggestion really is a matter of "proper and scalable code" compared to "trashy and easy to bottleneck code"
Original source
Right now every time a player logs out, it goes through all tickets and checks if the player owns that ticket
rektbyfaith
01-12-2023, 01:00 AM #4Archived author: Nix • Posted: 2023-01-12T01:00:48.260000+00:00
Original source
Right now every time a player logs out, it goes through all tickets and checks if the player owns that ticket
Original source
This scales with the number of tickets total (Even tickets the player does not own)
rektbyfaith
01-12-2023, 01:01 AM #5Archived author: Nix • Posted: 2023-01-12T01:01:00.204000+00:00
Original source
This scales with the number of tickets total (Even tickets the player does not own)
Original source
what you're suggesting somehow just goes right to the tickets rather than scrolls through it?
rektbyfaith
01-12-2023, 01:01 AM #6Archived author: Crow • Posted: 2023-01-12T01:01:28.163000+00:00
Original source
what you're suggesting somehow just goes right to the tickets rather than scrolls through it?
Original source
Instead I'm proposing using a lookup table (key, val pair), which will always scale with the number of tickets for the given player
rektbyfaith
01-12-2023, 01:01 AM #7Archived author: Nix • Posted: 2023-01-12T01:01:28.497000+00:00
Original source
Instead I'm proposing using a lookup table (key, val pair), which will always scale with the number of tickets for the given player
Original source
based on the guid
rektbyfaith
01-12-2023, 01:01 AM #8Archived author: Crow • Posted: 2023-01-12T01:01:40.993000+00:00
Original source
based on the guid
Original source
It goes right to the list of tickets owned by the player, instead of all tickets yes
rektbyfaith
01-12-2023, 01:01 AM #9Archived author: Nix • Posted: 2023-01-12T01:01:41.966000+00:00
Original source
It goes right to the list of tickets owned by the player, instead of all tickets yes
Original source
Correct
rektbyfaith
01-12-2023, 01:01 AM #10Archived author: Nix • Posted: 2023-01-12T01:01:44.418000+00:00
Original source
Correct
1 Guest(s)
1 Guest(s)