I think the problem is that your trigger is being disconnected from the player - the game_text is confused on who it should be sent to. Since the button is triggered directly by the beam, it is not considered player induced.

Here's how I'd try modifying the set-up: Have the trigger_mult trigger one of four mm's. This mm triggers both the beam (same beam for each mm) and the game_text (different game_text for each mm). Instead of having the buttons trigger the game_text, have them trigger a trigger_changetarget for the trigger_mult so that it points to a random one of the four mm's. This way, it should keep the right player in mind for the game_text and then it will randomly choose a message to send to the next player.

Granted, it will not be random for the first player to trip it, but everyone afterwards will be random.

This is gonna be difficult. This is not newbie stuff, but I can tell from your initial post that you understand more than you think you do; you took steps to analyze the problem perfectly.

The game_text, in order for it to show up on one player's screen, and not everybody else's, has to be initiated through a trigger sequence started by the player. I believe that the env_beam triggering something is messing up that sequence, since if you shoot a button directly, the message shows; but if the beam triggers it, it does not. So the solution here, is to keep the beams so that something random shows up, but to have the game_text triggered without going through the beam system.

Therefore, if there are four seperate multimanagers (mm1, mm2, mm3, mm4) which all operate the beam in the same manner, but all also trigger a seperate game_text, then the game_text should be displayed to the player. The trigger_multiple then would only need to have it's target field switched to each multimanager. It wouldn't work to have the change take place on the time the multiple is fired, so the idea is to have it give the player a message, and then randomly choose a game_text for it to show next time.

So the set-up is quite similar. You have the trigger_multiple, and it's pointing at mm1. Mm1 hits the beam on and off, but now also displays the game_text. The beam goes on and off, hits one random button. Now this button fires a trigger_changetarget (a different changetarget for each button). The trigger_changetarget targets the trigger_multiple, and gives the trigger_multiple a new multimanager to target (the multimanagers and trigger_changetargets are kinda paired up). This way, the game_text that it'll show will be randomized.

The changetarget is a tough entity to get the hang off, but once you've mastered it, it opens up tons of possibilities for entity set-ups.

Wouldn't a multisource work as well? it would greatly simplify the setup as you would only need one mm/beam setup. that way only the game_text that is targeted (through ms) by both the one mm and the button it triggers through the laser would be displayed.

it seems like this would maintain both the randomization and the player-event connection.