gen-protobuf

name	gen-protobuf
description	Regenerate the C# protobuf client files after editing any .proto file in bnet-messages/src/main/proto/. Use this whenever a .proto message definition changed, before committing — otherwise the Godot client (bestia-client) keeps stale generated code that no longer matches the schema. Triggers on: .proto, protobuf, protoc, Envelope, CMSG, SMSG, bnet-messages, regenerate proto, gen-protobuf.

Regenerate Protobuf Messages

Run this skill after modifying any .proto file in bnet-messages/src/main/proto/ to regenerate the C# files used by the Godot client.

How to run

Run the batch file from anywhere — it does not need bnet-messages/ to be the current directory:

bnet-messages/gen-protobuf.bat

protoc.exe lives in bnet-messages/ alongside the script. The script resolves it (and every proto/output path) via %~dp0, its own location, so it does not rely on protoc.exe being on PATH or on the caller's working directory.

What it does

• Clears bestia-client/src/Bnet/Proto/
• Runs one hardcoded protoc.exe invocation per .proto file (a manually maintained list inside the .bat, not a glob over the proto directory)
• Writes the regenerated C# classes back to bestia-client/src/Bnet/Proto/

Important notes

• Brand-new .proto file: add a line to gen-protobuf.bat first. The script does not discover files automatically — if you create a new .proto and don't add its protoc.exe line, the script runs successfully but silently produces no C# class for it (no error, no warning). Only editing an existing .proto file needs no .bat change.
• The Kotlin/JVM classes (used by the zone-server) are generated at build time by Gradle via the com.google.protobuf plugin — no manual step needed there.
• The C# output files are committed to the repo; always regenerate and commit them together with any .proto change.
• After regenerating, verify the expected types exist in the output (e.g. grep COMMAND bestia-client/src/Bnet/Proto/ChatCmsg.cs).