Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About bad

  • Rank
  1. Hello, i want to add some clanskins for my server. But i want that only that guys with the right license can wear it. Example: Player1 from the clan [AAE] has the license "civ_license_clan_aae" Player2 from the clan [AAG] has the license "civ_license_clan_aag" Player3 from no clan has no license both clans have the same uniform as a clanskin "U_B_CombatUniform_mcam" I want that Player 1 has the clanuniform from AAE, Player 2 From AAG and player 3 just the normal clothing, is this possible?
  2. bad

    error in config_vItems.hpp

    the thing is, i dont see a red dot
  3. bad

    error in config_vItems.hpp

    oh nice thank you. but how do you fixed it? because i have more files that are like these
  4. bad

    error in config_vItems.hpp

    hello. i have an error in my "config_vitems.hpp", but i dont understand where it is. log: https://hastebin.com/gukobecali.makefile vitems: https://hastebin.com/oyebikabac.cpp and here is the error: Warning Message: File mpmissions\Altis_Life.Altis\Config_vItems.hpp, line 885: '/VirtualItems.': 'ï' encountered instead of '='
  5. bad

    No Config Option Found:

    Config_vItems.hpp stringtable.xml also i installed a restrain script, but i dont think it has to broke smth. but i also send it: (tutorial) (data) fn_keyHandler.sqf fn_restrainAction.sqf Functions.hpp fn_vInteractionMenu.sqf
  6. bad

    No Config Option Found:

    server version is 4.4r4, i installed the server a week ago, changed some stuff, all worked fine. after i edited one of these: stringtable.xml , Config_vItems.hpp it stopped working. i reinstalled extdb2, nothing changed, tried extdb3, nothing changed, tried a wrong password, same error occures
  7. Hello. I have a problem with my Altis life RPG server database (extDB2) Here is the extDB2 log: 15-10-35.log the extDB config: extdb-conf.ini rpt: arma3server_2018-10-26_17-09-51.rpt when i change some database things like pass to something random, the error still occurs, but the password/name with navicat works fine.