Custom Events

Your example doesn't help me so far. I changed my code to be pretty much identical except for the actual custom event names and it still doesn't get a received event. There is a value of 1 in the Inspector for the Custom Event receivers as there should be. You also seem to have a mistake in your sample code. In the ReceiveEvent function why are you switching on a publicly set field eventReceivedBehavior instead of the function parameter customEventName?

public void ReceiveEvent(string customEventName, Vector3 eventOrigin) {
switch (eventReceivedBehavior) {

[EDIT]
I see what you're doing with the eventReceivedBehavior, but it seems rather hackish. You're hard-coding the event to be received and anytime the ReceiveEvent comes in then you're just switching on the one selected for in the inspector. Does that mean that the listener will only ever get ReceiveEvent called for the exact event/s that it has registered for?

I'm not "hard-coding" the event to be received, and it's nothing hacky. It's assignable in the Inspector from a Dropdown. Your script is hard-coding the event names into your if and return statements. i.e. if you want to change which event(s) you are listening to, you have to change the code in 2 places for each event. I just select a different event in Inspector and done.

My code only handles a single event to listen to. If you want to test with 2 events, add 2 instances of that script, with each listening to different events.

Yes, correct on your question above: the receiver has its ReceiveEvent method called only if it listens to that particular event, which is established through the SubscribesToEvent method. I ignore the event name parameter of ReceiveEvent because I already know what it is since we only listen to one event and the method doesn't get called if it's something else.

No need to apologize, I took it as you didn't understand what I was doing with the code, so I was clarifying. Not particularly upset, but in general I don't hard-code things. I make them general purpose even if I'm only going to use it for one purpose myself. It's better for maintenance purposes.

And non-DRY (don't repeat yourself) code is one of my biggest pet peeves when I do code reviews at my day job. Such as defining the same "magic string" in 2 places. At the minimum, that should just be a constant so you have a single place to change it if you need to later. Better still, if you have 2 events in the same class, you should still use a public string with that attribute I used so you can select it from the Dropdown in the Inspector, for each. No need to go hunting down code when you can do everything in the IDE.

I told you how you can get that to fire, by using my class twice. You could gut the switch statement out of mine and the variables that are used there and replace it with your own code.

You can verify if it's getting fired or not by turning on "Log Messages" at the top of the LevelWaveSettings game object Inspector.

It will log things like "Firing Custom Event: my event" to the Console. Even when you click the "Fire!" button. If it's not logging from the respawn then it's not firing.

But I just did a quick test in example scene #1 put adding a Custom Event to fire on respawning the player and it does fire the custom event.

OK, I found the problem. In Killable.cs it has the following code:


if (respawnDelay.Value <= 0f) {

                   if (respawnFireEvents) {

                       // ReSharper disable once ForCanBeConvertedToForeach

                       for (var i = 0; i < respawnCustomEvents.Count; i++) {

var anEvent = respawnCustomEvents[i].CustomEventName;

LevelSettings.FireCustomEventIfValid(anEvent, Trans);

}

}


So, it only fires the custom events if the respawnDelay is <= 0. I have my delay set to 5. So, I have to ask then why it only lets the custom event fire if the delay is <= 0. As soon as I set my delay to 0 then it fires the event.

[EDIT]
Or is there some other place that it tries firing the event once the respawn delay is over? I'm searching for that now.

Thanks. No rush. I can wait for the official release.