Abyll's Super App

[Limited]

Box-o-Tricks || Box-o-Trix

Looking good Abyll, although I havent had chance to test it yet.

[Sel]

Call it Appyll or Apyll

oh my god

yes hahaah

[jables]

does this work on gameserver servers?

[Aßyll]

nope. The only thing stopping it from working though, is just how the dll is injected. If someone had their own injector that worked on gameservers, then you could just use that. I have a plan to do something similar to SAPP's load cmd.. but that's for a later version.

[Cortexian]

nope. The only thing stopping it from working though, is just how the dll is injected. If someone had their own injector that worked on gameservers, then you could just use that. I have a plan to do something similar to SAPP's load cmd.. but that's for a later version.

I was under the impression that you got dll injection working for gameservers... Or was that supposed to be a secret?

[Aßyll]

Nah, I don't know how to yet. I have ideas planned, like I said - using a load cmd like sapp.

[jcap]

There's two or three things I want to see supported in here:

1. Support for multiple playlists. Have a way of setting up multiple playlist files you can name anything (just plain txt files with sv_mapcycle_add in it). Then you can type in-game /play "playlist1" and it will load the playlist's instructions and sv_mapcycle_begin it. Optionally, another command could be /loadpl which could load a playlist during a game, but not start it until /beginpl initiated (sv_mapcycle_begin).

2. !vote. There probably isn't a feature I miss more than !vote (why wasn't this app ever released!??). Any player could initiate a !vote which would poll the players in the server for a vote and then, if a majority rules for it, initiates the command voted on. !vote kick, !vote ban, !vote map, !vote mapnext, and any others that would be suitable for voting on.

3. This one is a little more complex, but it is something I've had my eyes on for about a year and a half. It would be absolutely amazing for Halo CE to have a global banlist, especially with the condition the game is in now with all the aimbotters and other assholes. The app could check a database hosted on Modacity a couple of times a day and update a table in your app's database for disallowed users. Each time a new connection is attempted, it would check against the table for disallowed users and either allow or deny them. Note that this would NOT interfere with the banlist file, because that would probably cause more problems than it's worth with both merging and managing (like having to restart the server to update it). Talk to me about this.

[Aßyll]

1. Support for multiple playlists. Have a way of setting up multiple playlist files you can name anything (just plain txt files with sv_mapcycle_add in it). Then you can type in-game /play "playlist1" and it will load the playlist's instructions and sv_mapcycle_begin it. Optionally, another command could be /loadpl which could load a playlist during a game, but not start it until /beginpl initiated (sv_mapcycle_begin).

Use cmdfiles for that: make any text file and put in the commands that you know are needed to change the mapcycle, i.e. a file named 'zombiecycle.txt':

sv_mapcycle_del 0
sv_mapcycle_del 0
sv_mapcycle_del 0
sv_mapcycle_del 0
sv_mapcycle_add cmt_snow_grove zombies
sv_mapcycle_add putput zombies
sv_mapcycle_add no_remorse zombies
sv_mapcycle_begin

and then ctfcycle.txt:

sv_mapcycle_del 0
sv_mapcycle_del 0
sv_mapcycle_del 0
sv_mapcycle_del 0
sv_mapcycle_add timberland ctf
sv_mapcycle_add bloodgulch super_ctf
sv_mapcycle_add wtc3 other_ctf
sv_mapcycle_begin

so if you want to go to zombies mapcycle, do "cmdfile zombiecycle.txt"
All that you have to do with cmdfiles is type up the series of commands in a file in the superapp folder, and then run it. (I think I'll type up some sort of tutorial on that, to go along with the readme.)

2. !vote. There probably isn't a feature I miss more than !vote (why wasn't this app ever released!??). Any player could initiate a !vote which would poll the players in the server for a vote and then, if a majority rules for it, initiates the command voted on. !vote kick, !vote ban, !vote map, !vote mapnext, and any others that would be suitable for voting on.

I'm not too sure about how to make a voting system, but I know it'd be easy to put into my app. I could figure it out eventually, but I won't focus on it right now... I'd be glad to get any help with it if someone feels like it - I'm still looking for a team.

3. ... Global banlist file ...

I could certainly add in such functionality, though I don't know how I could do it... I do know where the banlist is in the haloceded memory, and I was looking at trying to give some ability to live-edit the banlist without needing to reload the banned.txt. Your help would be welcome though: I don't know much about network programming yet.

[jcap]

I haven't used this because I'm not home yet. How are the players managed (names, total count)?

Really, you should manage all the players and settings in an Access database, like rec0's app. It's one file for easy management and you can add/remove from the database easily. It keeps the mess of files clean too.

I do think you should just keep the banlist separate, though. If you start getting into the updating of a banlist, you could end up with duplicates or some random issues by merging with memory. How does Halo reject players before even joining the game? In the logs, it just says QUIT.

[supersniper]

I had HSE set up on my server and I got the vote commands to work... but a poll was never started... it just automatically changed to the next map or kicked/banned the player.