EventManager

Watch your console as Event Manager loads. Does it say Deathmatch is registered?
If not, it might say why not.

 

No nothing

(01:02:53) | [RCON][154.58.124.97:55734] oxide.reload EventManager
(01:02:53) | [Oxide] 17:02 [Warning] Calling 'Unload' on 'EventManager v2.0.24' took 289ms
(01:02:53) | [Oxide] 17:02 [Info] Unloaded plugin Event Manager v2.0.24 by Reneb / k1lly0u
(01:02:53) | [Oxide] 17:02 [Info] Loaded plugin Event Manager v2.0.24 by Reneb / k1lly0u
[DOUBLEPOST=1473466300][/DOUBLEPOST]Ok I just wiped my config, and tried to do anything with the default, none of it works.

 

You cut the end off your config file. Always check with JSON validator if you have weird issues.
Replace the final comma with
]}}

Code:

{
    "Announce_Event": true,
    "AnnounceDuring_Event": true,
    "AnnounceEvent_Interval": 120,
    "Battlefield_Timer": 1200,
    "Default_Gamemode": "Deathmatch",
    "Default_Spawnfile": "Arena",
    "KillDeserters": true,
    "Messaging_MainColor": "#FF8C00",
    "Messaging_MsgColor": "#939393",
    "Required_AuthLevel": 1,
    "UseClassSelector_Default": true,
    "UseEconomicsAsTokens": false,
    "z_AutoEvents": {
        "AutoCancel": true,
        "AutoCancel_Timer": 300,
        "GameInterval": 1200,
        "z_AutoEventSetup": [{
            "CloseOnStart": true,
            "EventMode": 1,
            "GameType": "Deathmatch",
            "Kit": "Arena",
            "MaximumPlayers": 20,
            "MinimumPlayers": 2,
            "Spawnfile": "Arena",
            "TimeLimit": 1800,
            "TimeToJoin": 60,
            "UseClassSelector": false,
            "ZoneID": 50283398
        }]
    }
}

 

Cleared my entire config file and pasted that in, reloaded the plugin and still get the below

 

That's a different error now with a different cause.

Chances are your spawn file name, kit name, or arena name have been put in incorrectly.

Is that error the result of /event launch ?
If so, go back to inputting manually for troubleshooting

/event game *
/event spawnfile *
/event kit *
/event whatever else *

pretty sure it'll tell you which one is wrong

 

Here's a screen of my spawns so I know thats working too

 

Sure, but if you type the spawnfile name wrong in your config (or manually), you'll get the error you're seeing.
Same goes for other required parameters like Kits etc.

Incidentally, what spawn plug are you using with that nice graphical display?

 

Spawns with Spawns Database

I've checked my kit, spawnfile and zone ID, all working fine, do you think it's any of the parameters in the zone?

Here's the output of the log file, not very helpful

[09/09/2016 17:29:37] Next auto event
[09/09/2016 17:29:37] No events init

 

Kick ass...Thank you.
That's what I'm using....Never noticed that there's a 'show' option.


Yeah, any time I've seen your error, it's been from typing /event launch with a custom parameter put in the config incorrectly.
Either check check and double check them all, or load the event manually and see which parameter is rejected.

 

Dude it falls down at the first hurdle when trying to create manually, I've been trying a mixture of both this whole time. If I do anything like /events open or new it tells me to load a spawn file, I try load the spawnfile and it moans about Deathmatch not being registered

EDIT: Just removed every trace of the plugin, reloaded, tried to do it manually and still failed moaning about Deathmatch, is this plugin broken?

 

What version are you trying to run?

If you don't see game is registered in console as you load/reload the plugin (or event manager) then it's never going to work.

Fixing your config file a few posts back should have allowed the plugin to register.
Is that not the case?

 

Oh jesus

Oh, jesus, Christ, I didn't realise the extra dependency of deathmatch plugin, fuuuck, thanks man, loading it now

 

Fuck me. lol.

Next question was please post your ArenaDeathmatch.json.
Presumably there wouldn't have been one.


For future, the same is true for all games, as far as I know
GunGame + Chopper Survival, for example, are separate plugins which must be installed and configured, along with EventManager.

Good luck.

 

Love you dearly Game in progress now

 

Haha! Enjoy.
If you need any help with zone manager or GunGame or anything, hit me up.

 

People seem to be able to join even though closeonstart is true, or is there just some overlap

 

Not 100% sure.
I've never used deathmatch so I'm not aware of its specifics.

If you're manually launching, the EventManager closeonstart won't apply, as far as I know. You'll have to do /event close

btw - I have a bunch of pics of my arenas here, if you're interested.

 

So presumably I can just have additional deathmatches using different kits in my config? It'd be nice for it to cycle through different ones, like have a shotgun one, primitive, rocket one.

 

I've noticed since the modification of spawn files is a bit bugger, it's easier to just create a new spawn file to use, however what I've noticed is it needs updating in 3 places for it to work properly, I have to change it in the config of ArenaDeathmatch, and twice in the EventManager config, both in default spawnfile and also in the spawnfile for deathmatch, my question is, can it be made so eventmanager can update the arena deathmatch config, and also, can i set the default spawnfile to null? As I'd like to set up team DM and dont want it using the same spawns, if i set the spawnfile in the game mode config area, does it overide the default one?

 

Hey,

Yeah, I never bothered trying to edit a spawn file. Always found it quick to just re-do it.

If you go for manual game setup then you get to specify the spawnfile each time.
I've no idea what's in my configs...I just do
/event game GunGame
/event spawnfile 'field arena' <- choose whatever one I want.
/event open.....etc

EventManager V3 is in public testing and has a GUI setup screen which addresses all these issues.
There's a demo video a few pages back - take a look.

I'm not recommending you use it just yet, but I'm doubting there'll be any updates or changes to V2.*