Devieth

If you can get socket to load on SAPP you may be able to get it to load in Chimera. SAPP can put out errors without crashing.

Ahh. Also think you mentioned luasocket, not sure if it would work for you, but try installing Lua modules in the executable (haloce.exe) directory using luarocks? That part of Chimera's Lua was not really set up to point to something like `chimera/lua/global/modules` unfortunately. Good chance it still wont work though. Neat project though.

You could use something like this: local file = io.open( "%username%\\Documents\\My Games\\Halo CE\\chimera\\lua\\global\\health.txt", "w" ) That way it will target what ever user the current system is on all Windows systems. Not sure how to implement such a thing on Linux though, as there you are pointing to the `z:` drive? This would want to point to wine's `c:` drive.

This is something that @Chalwk's project reminded me that I wanted to do when I first discovered Discordia (Lua API for Discord.) So actually a good amount of thanks to him that I even made this. Probably a lot more simple that what he's doing. Discordia is pretty awesome and I been writing bots with it for a couple months now.

Just this morning. Been thinking about it for a while now, and someone else's interest in it made me want to do it.

So I created a Discord bot that will allow you to run console commands from Discord. First thing is you will need to set up a bot with Discord and copy its Token over for use in the Discordia Script. https://discord.com/developers/applications When inviting your bot, do not give your bot administrative privilege, this is to make sure you make it so the bot can only read messages from admin channels by specifically adding that bot to category permissions or per-channel permissions. Here are the permissions you want to give it: How to invite your bot: https://discordpy.readthedocs.io/en/latest/discord.html ____________________________________________ After that you will need the Discordia + Bot package [ discord.lua ] and the server side script [ discord.lua ]. Setting up the Discordia bot: 1. Unzip the luvit.zip onto the same system your server is going to be running on. 2(a). Open the haloce.lua in the luvit.zip, at the top you should see this: -- Set up bot local bot_prefix = ">" local bot_token = "YOUR_BOT_TOKEN" -- Path to haloceded/haloded(s) local servers = {} servers['ce01'] = {"C:\\Users\\Gigabyte\\Desktop\\CE_Test", '-path "C:\\Users\\Gigabyte\\Desktop\\CE_Test"', "haloceded.exe"} --servers['ce01'] = {"C:\\Users\\Gigabyte\\Desktop\\PC_Test", '-path "C:\\Users\\Gigabyte\\Desktop\\PC_Test"', "haloded.exe"} 2(b). Take the bot token you got from your discord developers page and paste it in replacing `YOU_BOT_TOKEN`, and make sure that the quotations are still around it. 2(c). Now below `servers` you will want to set your server short-name (in my case it was ce01, so `servers['ce01'] =`). Set the server path, launch arguments, and executable name as well. (The second line is an example how to do a HaloPC server, or add another server.) NOTE: You cannot have 2 servers with the same short-name like I did by accident. 3(a). Take the discord.lua and paste it into your SAPP server's lua folder. 3(b). Remember to add `lua_load discord` to your SAPP init.txt. 4(a). Open t he discord.lua, at the top it should look like this: -- Path to Discordia bot. local discordia_path = "C:\\Users\\Gigabyte\\Desktop\\luvit\\" -- Path to read commands from. local command_file_path = "\\ce01\\command.txt" 4(b). For discordia_path, put the path were you have the the bot unzipped to, like shown above. 4(c). For command_file_path you need to put the server short-name where I did otherwise the server will not be able to pick up commands. 5. Start your Halo server + the bot (using the start_bot.cmd) Preview of how it should work when set up correctly: luvit.zip

Who needs good netcode when you have and uninstall button. Sigh... We just need that new client in 10 years that bakes in all the fixes. By that time

This works exactly how I thought it would. Does make it easier on people instead of having to manually run the commands to achieve this. Nice.

This script exists already. Should be in the releases section.

Here is the link: https://cdn.discordapp.com/attachments/279602619947810818/279697864538456064/haloce.rar Found from this Discord: https://discord.gg/BSUPuq

Opinion: I wouldn't run Halo in any type of windowed mode as it introduces a lot of input lag, more than expected compared to other games. Tabbing in and out sucks but if you are using Chimera 1.0 (or using HAC2 custom_chat or classic_chat) you won't have to worry about game crashes from tabbing, and the game resumes rather quickly. If you want there is even an executable that keeps the engine active even when tabbed out so things don't desync/freeze when the Halo window loses focus.

Since this is here, this is another version of Chimera (that has Lua support) that I worked on that could be used: https://github.com/it300/Chimera600 Comes with these couple changes (including the ones from gbMichelle's -581)

Is there any way to bypass the stupid limitation in SAPP that makes it so you can't have a Lua script execute `reload`? Trying to set up a script that auto-updates server files (which works) but this block on the reload command is only thing getting in the way. I tried using firebird and crash the server to get it to restart the server (which works on windows as long as you have vcredist 2015 installed) which wont work on linux with the versions of wine that support SAPP. Tried making a module for ffi but failed (and tried to use the execute_script code from chimera -572 because I don't know asm. But kept getting an error saying `"push %0;"` is an unsupported instruction.)

Sweet, if you want an easier way to detect input I have a custom build of Chimera (currently called -17.572) which has 2 Lua API functions like `get_key_press(VK_Key_Code)` `chat_out(Message, Mode)`. chimera.zip Other stuff that was done to this custom version:

I am currently running 10.2.1 on wine fine, up-time hitting the month+ mark. Try different versions (even older versions) of wine in order to get it to run. Each Linux OS can have a quirk that requires a specific version of wine. I primarily work with Ubuntu. Ubuntu 12.04 = wine1.7 Ubuntu 14.04 and 16.04 = wine1.6 Ubuntu 18.04+ = unknown Also make sure you have English locale packages installed.