Search the Community
Showing results for tags 'cycle'.
Found 3 results
-
New Mission does not start unless all players leave!
WurschtBanane posted a topic in ARMA 3 - SERVERS & ADMINISTRATION
This is what my server.cfg looks like, i censored some things: // // More information at: http://community.bistudio.com/wiki/server.cfg // // GLOBAL SETTINGS hostname = "hostname"; // The name of the server that shall be displayed in the public server list password = ""; // Password for joining, eg connecting to the server passwordAdmin = "passwordAdmin"; // Password to become server admin. When you're in Arma MP and connected to the server, type '#login xyz' //reportingIP = "arma3pc.master.gamespy.com"; logFile = "server_console.log"; // Tells ArmA-server where the logfile should go and what it should be called // WELCOME MESSAGE ("message of the day") // It can be several lines, separated by comma // Empty messages "" will not be displayed at all but are only for increasing the interval motd[] = { "", "Server hosted by nitrado.net", "" }; motdInterval = 10; // Time interval (in seconds) between each message // JOINING RULES maxPlayers = 6; // Maximum amount of players. Civilians and watchers, beholder, bystanders and so on also count as player. kickDuplicate = 1; // Each ArmA version has its own ID. If kickDuplicate is set to 1, a player will be kicked when he joins a server where another player with the same ID is playing. verifySignatures = 1; // Verifies the players files by checking them with the .bisign signatures. Works properly from 1.08 on equalModRequired = 0; // Outdated. If set to 1, player has to use exactly the same -mod= startup parameter as the server. // VOTING voteMissionPlayers = 1; // Tells the server how many people must connect so that it displays the mission selection screen. voteThreshold = 2; // 33% or more players need to vote for something, for example an admin or a new map, to become effective allowedVoteCmds[] = {}; // disables voting // INGAME SETTINGS disableVoN = 0; // If set to 1, Voice over Net will not be available vonCodecQuality = 10; // Quality from 1 to 10 persistent=1; regularcheck=""; // MISSIONS CYCLE class Missions { class CLASS1 { template = Missionname1; cadetMode = 1; }; class CLASS2 { template = Missionname2; cadetMode = 1; }; }; My problem is that when mission Number 1 is over the second one does not start when a player instantly clicks OK after the debriefing, because then the old mission starts again, but it does not even restart, it just keeps going. This really pisses me off because the Mission end trigger that ends the mission after 10 mins can only be activated once... Can anyone help me with this? In KOTH there are always different kinds of missions that switch without players having to leave or wait... -
This is how the Mission part in the server.cfg looks like: // MISSIONS CYCLE class Missions { class ARMA3 { template = "Stratis_dogfight.Stratis"; difficulty = "Veteran"; }; }; How do i make it load missions one by one when one is completed? Say one coop is done then the dogfight mission starts etc. and when the last mission is completed it starts from beginning again. Like in King of the Hill by Sa-Matra. Im just sick of always changing the mission name in the cfg. Its also a public server which is why i am asking.
-
[BUG?] syncing and "on act" not working with cycle waypoints
sarogahtyp posted a topic in ARMA 3 - MISSION EDITING & SCRIPTING
i ve 2 groups with 3 waypoints for each of them placed at 2D editor. there r 2 move waypoints and the last is a cycle waypoint to let em walk along the waypoints continuously. I ve synced every pair of waypoints each other. wp 1 of group 1 is synced with wp 1 of group 2 wp 2 of group 1 is synced with wp 2 of group 2 wp 3 of group 1 is synced with wp 3 of group 2 my thougts were that the group which is faster waits for the slower group on each waypoint. that works for the first and second waypoint but at the third (cycle) waypoint the faster group isnt waiting but running to wp 1 and waiting there until the slower group is at wp 1. I just need a confirmation for that behaviour to know if thats normal that syncing of cycle waypoints seems to be senseless... thx alot. EDIT after some more testing I noticed that cycle waypoints dont execute the "On Activation" field. I entered a systemChat in it which works if its a move waypoint but not if its a cycle waypoint. Is that intended or a bug?