[Dragokas]

Author: disawar1 [raziEiL] (fork by Dragokas)

Description:

For plugin developers.

Reports in log and chat area the names of events and forwards fire at the moment.

Features:

- all events splitted by Post & Pre
- forwards are supplied with client index if possible
- on round end additional info is collected (similar to Entity Limits Logger), such as:
* total entities
* precache info
* client weapons
* saferoom entities

Logfile location:

- addons/sourcemod/logs/say_event.log

Settings (ConVars):

Located at: cfg/sourcemod/say_event.cfg

- say_event_enable - def.: 1 - Log Events: 0=Disable, 1=Enable

Commands:

- Nothing

Installation:

- copy smx file to addons/sourcemod/plugins/

References

- [L4D & L4D2] Say Event | for devs by disawar1 (original plugin)

[Hawkins]

Would it help in debugging crashes, or is it too late to log when crash happens?

[Silvers]

Originally Posted by Hawkins Would it help in debugging crashes, or is it too late to log when crash happens?

Depends if crash happens after event. Better use Accelerator extension to identify exactly where server is crashing.

[Dragokas]

Hawkins, it depends. Indirectly and very inaccurate. If you know what plugin the mentioned event name is coming from, it may narrow search area.

[ZBzibing]

125 explain_radio
126 explain_gas_truck
127 explain_panic_button
128 explain_elevator_button
129 explain_lift_button
130 explain_church_door
131 explain_emergency_door
132 explain_crane
133 explain_bridge
134 explain_gas_can_panic
135 explain_van_panic
136 explain_mainstreet
137 explain_train_lever
138 explain_disturbance
Are these still useful in events now? I try to trigger them in the game, any prompt feedback every day

public void OnPluginStart()
{
	//RegAdminCmd("sm_zmob", Command_ZspawnMob, ADMFLAG_ROOT, "触发尸潮.");
	HookEvent("player_use", Event_PlayerUse);
	
	HookEvent("explain_pre_radio", Event_explainpanic);
	HookEvent("started_pre_radio", Event_explainpanic);
	HookEvent("explain_radio", Event_explainpanic);
	HookEvent("explain_gas_truck", Event_explainpanic);
	HookEvent("explain_panic_button", Event_explainpanic);
	HookEvent("explain_elevator_button", Event_explainpanic);
	HookEvent("explain_lift_button", Event_explainpanic);
	HookEvent("explain_church_door", Event_explainpanic);
	HookEvent("explain_emergency_door", Event_explainpanic);
	HookEvent("explain_crane", Event_explainpanic);
	HookEvent("explain_bridge", Event_explainpanic);
	HookEvent("explain_gas_can_panic", Event_explainpanic);
	HookEvent("explain_van_panic", Event_explainpanic);
	HookEvent("explain_mainstreet", Event_explainpanic);
	HookEvent("explain_train_lever", Event_explainpanic);
	HookEvent("explain_disturbance", Event_explainpanic);
}
//--------------------Event--------------------//
public void Event_explainpanic(Event event, const char[] name, bool dontBroadcast)
{
	PrintToChatAll("\x04[SM] button was pressed!!!");
}

[Silvers]

It's not when the the button was pressed but when the instructor hint shows how to use those buttons/events. If you want to hook button press use Stripper:Source to dump the maps entities and find the relative button/logic entity and use HookSingleEntityOutput(). You can see an example of this in "Lift Music" plugin I wrote.

[Dragokas]

ZBzibing, you can also use Silver's Input Hooks to track button name/class dynamically.

Just install it, enable it ("sm_input_listen") and press the desired button.

[ZBzibing]

Many thanks to Silvers, Dragokas, I did see the example, was very inspired and tried the method very well