Just Cause 3 was meant to have a built in multiplayer mode, but like the microtransactions, it was cancelled.
So the command allows us to call any game events. The help command is used just like the list command, entering "help send_event" as example gives us its usage, which would be "send_event ". When you search for event, it will list you add_menu_event and send_event as an example. You simply enter "list event" as an example and the console will list you all events containing that word. Then simply execute the buttfile using "execute events.butt" as an example and you got all your events ready with just one command.
You could then create a buttfile and enter commands to add several events. But say you want to add a bunch of events. It is now available to quickly trigger from f9 > events. So say you want to add the player kill event from the console, you'd enter "add_menu_event ply.kill". The events you add will show up under a new "Events" tab. As an example, the console has the command add_menu_event, which lets you add a game event to the debug menu. As for commands you can use, you can use the same commands as you'd use for the debug console. You can create one by creating a txt file in the install location of the game and changing the file extension from. A buttfile can be compared to a batch file under Windows.
#Just cause 3 dropzone how to#
The first option tells you how to execute a buttfile. It presents you with the version number, here 1.0, and three tips on how to use it: Pressing the tilde key, you can open the beta's debug console. Leaked via Xbox-underground in late 2014, these are currently the earliest details of Just Cause 3.Īccording to the article by Gamespot, somewhat prior to this version of the game, the PC version was meant to be free to play and the console version payed and supported by micro-transactions, but these plans were already changed at this point, as we can see in the final game and later stated by Christopher Sundberg.
0 kommentar(er)
