Lua: Further centralize code, fix Bizhawk 2.9 (#1685)

* Fixes the socket library for bizhawk 2.9/lua 5.4 by including another one in parallel
* Fixes lua 5.4 support by making socket.lua into a "modern" module (the `module` keyword is gone)
* Adds the linux version and 32 bit windows socket dlls because why not
* Merges common functions into `common.lua` - the only functional change of this should be that:
  * Some things that were locals are globals now - this can be changed, I just was lazy and it likely doesn't matter
  * `drawText` now uses middle/bottom for all prints - feel free to do what you like with that change
This commit is contained in:
zig-for
2023-04-15 00:17:33 -07:00
committed by GitHub
parent 808203a50f
commit 5a7d20d393
41 changed files with 255 additions and 2570 deletions

View File

@@ -27,10 +27,10 @@ Once Bizhawk has been installed, open Bizhawk and change the following settings:
BizHawk is running in the background.
- It is recommended that you provide a path to BizHawk in your host.yaml for Adventure so the client can start it automatically
- At the same time, you can set an option to automatically load the adventure_connector.lua script when launching BizHawk
- At the same time, you can set an option to automatically load the connector_adventure.lua script when launching BizHawk
from AdventureClient.
Default Windows install example:
```rom_args: "--lua=C:/ProgramData/Archipelago/data/lua/ADVENTURE/adventure_connector.lua"```
```rom_args: "--lua=C:/ProgramData/Archipelago/data/lua/connector_adventure.lua"```
## Configuring your YAML file
@@ -66,7 +66,7 @@ path as recommended).
Once both the client and the emulator are started, you must connect them. Within the emulator click on the "Tools"
menu and select "Lua Console". Click the folder button or press Ctrl+O to open a Lua script.
Navigate to your Archipelago install folder and open `data/lua/ADVENTURE/adventure_connector.lua`, if it is not
Navigate to your Archipelago install folder and open `data/lua/connector_adventure.lua`, if it is not
configured to do this automatically.
To connect the client to the multiserver simply put `<address>:<port>` on the textfield on top and press enter (if the