amperbee
thunderdome denizen
I wanted to ask some stuff so I can clear my mind. And some miscellaneous questions, the which some resulted interesting.
1) What happens if I made a giant, but with giant I mean GIANT, file with functioning code, and I were to use that on a netgame?
2) Only if the previous question got a negative answer, is there a way I can split the code in different files and somehow join them together? Or the netgame would get the same fate as if I used the entire file?
3) I can accidentally cause a memory leak?
4) How do I make the screen go pitch black, while retaining the HUD elements, along with custom HUD elements?
5) It would be okay if I made a (for example) 9x9 matrix, then make 81 hud elements for every single content on every "cell"?
5.1) If not, then I can just make 9 and concatenate them?
5.1.1) If not, concatenate all and add a line breaker after every row?
6) How does the "consvar_t" thing work? Something like "respawnitemtime.value"?
7) "players[0]" always targets the server player on a normal in-game server, or the first player that joined on a dedicated server?
8) SRB2 Lua can read files?
9) I can edit sectors mid-game? With that I mean editing the floor Z and ceiling Z, and possibly the sector type and texture, not creating new sectors, because that's only possible on Doom Builder IIRC. I already read the variables for the sector, but I want to confirm they can be changed mid-game and not just at map load.
10) I can refer to the sector a player is standing on?
11) If I made a map and created a polyobject, I can make the polyobject thing teleport under the player at command?
11.1) And rotate it?
12) Some variables are read-only because they're hardcoded to be like that, for security, because thre is no possible way to even remotely edit them if even allowed, or for any other reason? I'm asking that because there are a few interesting variables that are read-only.
13) Is it possible to make 4 team CTF/Match?
I hope I'm not being annoying with my questions, I just want to understand more how does Lua work in SRB2, and know the answers of some things I might run into.
1) What happens if I made a giant, but with giant I mean GIANT, file with functioning code, and I were to use that on a netgame?
2) Only if the previous question got a negative answer, is there a way I can split the code in different files and somehow join them together? Or the netgame would get the same fate as if I used the entire file?
3) I can accidentally cause a memory leak?
4) How do I make the screen go pitch black, while retaining the HUD elements, along with custom HUD elements?
5) It would be okay if I made a (for example) 9x9 matrix, then make 81 hud elements for every single content on every "cell"?
5.1) If not, then I can just make 9 and concatenate them?
5.1.1) If not, concatenate all and add a line breaker after every row?
6) How does the "consvar_t" thing work? Something like "respawnitemtime.value"?
7) "players[0]" always targets the server player on a normal in-game server, or the first player that joined on a dedicated server?
8) SRB2 Lua can read files?
9) I can edit sectors mid-game? With that I mean editing the floor Z and ceiling Z, and possibly the sector type and texture, not creating new sectors, because that's only possible on Doom Builder IIRC. I already read the variables for the sector, but I want to confirm they can be changed mid-game and not just at map load.
10) I can refer to the sector a player is standing on?
11) If I made a map and created a polyobject, I can make the polyobject thing teleport under the player at command?
11.1) And rotate it?
12) Some variables are read-only because they're hardcoded to be like that, for security, because thre is no possible way to even remotely edit them if even allowed, or for any other reason? I'm asking that because there are a few interesting variables that are read-only.
13) Is it possible to make 4 team CTF/Match?
I hope I'm not being annoying with my questions, I just want to understand more how does Lua work in SRB2, and know the answers of some things I might run into.