Jump to content


  • Content Count

  • Joined

  • Last visited

  • Medals

Everything posted by terox

  1. your client and the server can not use the same ports if on the same machine If they are different machines and you are hosting from your home network, then i would suspect your server is not configurred correctly on the router Set the server up to run on non default ports and make sure the upnp box is ticked and read up on how to set a dedicated server up on the router you are using (They all have their idiosyncracies)
  2. well here is what I would do Make sure the target line of your -mod and -servermod arguments are exactly as per the mod folder names (Case sensitivity) (The first part of your rpt states exactly what you are running, this is why its extremely important. If you run any mod folders that use any dll's like task force radio, they will most likely have to remain in their originally named mod folders Ask your host how to access the full contents of your rpt files, If you restart the server, a new rpt file is created maybe you can access the first part of the rpt file that way and then if your stuck follow this guide....
  3. THIS IS PART OF YOUR RPT FILE What ?????? So how come you managed to copy an extract from it if you wasn't able to find it ?
  4. Make sure you dont have any spaces in the file name eg co 23 mymission name (Otherwise it will rename the mission to co%2023%20mymission.altis.pbo and pack just the mission.sqm up without any other additional files such as the init.sqf) so instead use co_23_mymission then in the mission editor select "Export to multiplayer" This will create co_23_mymission.Altis.PBO filename in your root MpMissions folder The .Altis.pbo extension will be automatically added by the engine when you export the mission in this way It is this that you need to upload to the server After you have created the .pbo you can then rename it if you wish, adding a version number for the mission and removing the underscores to make it more readable in the mission selection screen eg co 23 mymission v001.Altis.pbo
  5. You really need to upload the entire file,the first few lines are very important... infact it all is Example These files can be fairly large so if there is a B.I limit, upload them to a pastebin site and link to it from the post
  6. No RPT file no can help. I am assuming you arent actually loading CUP even though you think you are. The rpt file would prove/disprove this
  7. terox


    Reads the links I gave you. If you think the rules are being breached let BIS know
  8. try listing the arma64server.exe in the game server firewall as well as the normal ports
  9. FYI afaik, when you initially boot up the server it doesnt read the MpMissions listing. It only does this when the first player connects, it then reads through all description.ext files and any files #included from it and will stop loading if it finds an error So if the server fails to load after nothing apparently has been done to it, this is the most likely issue because if a mission is uploaded while the server is running, it wont show up as a faulty mission until the server is next rebooted and someone logs into it, often misleading an admin into thinking nothing has changed
  10. Maybe the server is not fully loading rather than not responding to #missions command If this is the case try clearing out all the MpMissions and rebooting the server. Your rpt file will be worth reading through
  11. terox


    You are pointing out Monetisation rules which are very different from donation rules and there is a clear distinction between the two. Here are the links for all of this information: https://www.bistudio.com/monetization https://www.bistudio.com/monetization/faq#c2
  12. terox

    Looking for a developer

    try the scripting forums
  13. terox


    According to the BI Rules on monetisation, donations are allowed providing they are given as a gift "without any counter value" which reading between the lines means The donator does not receive any special privileges, equipment, special access or any perks of any kind that are not readily available to those who do not donate. This is how most open arma communities fund their servers. We have been running of donations in this way buying our own servers and colocating since 2003 and without those that do donate we would not have survived for as long as we have. We are currently starting to save up for the next gen of ArmA whenever that will come and that server for our expected requirements is gonna be the most expensive server we have ever bought. I would suggest if you find yourself on an Arma community server that is run well, gives you quality of gameplay that you should consider offering a small monthly contribution towards the running costs. £$5 is peanuts and easily found for most people, and if a decent bunch in the community all chip in it helps a lot A 1U rack server can cost a few thousand $, £, Euros to buy dependant on the hardware and then £50 + for colocation Rented slot servers vary in price from as little as £15/month Rented full dedicated servers can cost anything from £80 upwards Windows licenses aren't cheap and then there are additional apps such as Firedeamon and websites that also need to be funded
  14. follow this to the letter... as for the rpt entries it will take time for you to learn what to ignore and what is important. You should prove a vanilla install before you start adding 3rd party content. That way you would know what the issue is as it would have been caused and become evident as the last thing you did to the server. (This included uploading missions)
  15. terox

    Join a server by a link

    This is only a guess... some apps can do this and so do some websites, so am assuming this may be possible with a bit of php coding at the link url website
  16. You could set up 2 user profiles using the -profile switch in a desktop shortcut So for your development profile, you would point the directory to a no default location, here you would have your un pbo'd mission folders in your profiles username folder when you want to create a server mission, export the dev folder to Multiplayer via the editor = places it in the root MpMissions folder as a pbo file and not your profile user folder this way the only server missions you have would be in the root mpmissions folder
  17. directly updating a mission on a production server is bad practice. You should develop it seperately and once your happy the changes are stable, then replace the production server mission with the latest version. or better still add a new version with a slightly different file name version, example co 24 mymission v001.altis.pbo co 24 mymission v002.altis.pbo co 24 mymission v003.altis.pbo This way you can select the older version if you screwed up on the testing of the newer version Also do this less often, twice a week would be ample
  18. you can set up a symlink to drop box for your server mpmissions or synchronise a folder on a web site
  19. if you have an issue with a private server then you should take up your issues with them directly, this is not the place to do it. Also if your going to make a complain get your complaint right, the monkey reference according to your screenshot was to do with the portuguese language not the individuals ethnicity. Also you should have included the conversation that occurred that caused such a response, which would probably throw any complaint you have out of the window anyway. If your going to play online with other cultures/people , the first thing you should aquire is a sense of humour and a thick skin, this is the real world not some over protected school environment. Get used to it
  20. on their servers, ask Dwarden
  21. terox

    Just a quick question!

    well that would depend on your complaint, if you tell us what it is generally about without dropping any names maybe we could help point you in the right direction
  22. the post you linked to also has the fix
  23. I also revamped the loadouts, the only options I gave for the VAS box system was to give the players the ability to collect ammo for other players weapon systems (Everyones an ammo bearer) I removed everything I didnt want them to have, limiting options for simplicity and ability to share ammo etc and to stop them running around with uber scopes and thermal imaging equipment. Each role was given a specific loadout when it came to equipment. Recon for example were given low powered self defence weapons but high powered observation equipment, as would be correct for that role. No sniper equipment was made available (Spoils the fun for everyone else and attracts the players with the wrong mentality for the sniper role (When I design my own missions the sniper role is lucky if he has more than 1 mag) On our vanilla server we use VOIP and the command net channel as the platoon net so orbat layout is pretty important for us. Therefore I also changed the orbat so that there was a definitive Platoon commander and XO position without having any other units in their group to administer These 2 slots were then the only slot that could re-assign roles to anyone, it was removed from squad leaders to stop abuse. The amount of changes I made to Roy's original concept were made to custom fit our actual style of gameplay and fortunately Roy has always allowed this. HALO was restricted to recon only, which was only given to them so they could get into the AO quickly, start gathering intel and find a suitable LZ for the main helo insertion Fast air was restricted to 1 slot, nothing worse than having all the enemies destroyed by some idiot flyboys and spoiling it for the grunts and whoa betide him if he got shot down, he wouldn't be respawning and flying straight away, it required a CSAR unit to go and collect him, revive him from his none time out bleedout and then return him to the airfield where a nice shiny new aircraft was waiting. (This has a great effect on their flying skills) The beauty of Roy's patrol ops is 2 fold Firstly his design and implementation Secondly his open license agreement which does allow you to edit his work. Our community wouldnt be the same without PO3 and now eagerly awaiting PO4
  24. maybe you should take this to the mission editing forum, which is more apt for your query than the server administration forum