I imagine this is a beginner's-calibre; bonk-me-over-the-head-with-a-saucepan-for-asking kind of question, but here it is anyway:
When I was troubleshooting my other BGP issue that y'all were so helpful with, I tried configuring a route-map to set the weight to 100 for incoming routes. I created a route-map named "Toby" (Toby is my nephew!) like this here:
Enter configuration commands, one per line. End with CNTL/Z.
Sethtek-G(config-route-map)#match next-hop 1
Sethtek-G(config-route-map)#set weight 100
Sethtek-G(config)#access-list 1 permit host 172.16.0.2
Sethtek-G(config)#router bgp 190
Sethtek-G(config-router)#neighbor 172.16.0.2 route-map Toby
% Incomplete command.
Sethtek-G(config-router)#neighbor 172.16.0.2 route-map Toby in
% "Toby" used as BGP inbound route-map, nexthop match not supported
Dumb question: Why is nexthop match not supported for INBOUND routes? Aren't those the only routes for which the next-hop attribute is even interesting?