Volleyball Manager - series of freeware volleyball management simulation games

  • We work on new version which will include major changes but it will take some time so don't ask about realease date.
    New features are: trainer & assistant module, improved scouting & sponsorship, optimized database structure, added Czech language (thx to Repick), developed XML database editing (player contract lengths, competition history, trainers etc.), fixed some reported bugs. Should you have any questions, please write in this topic.
    Once more it will take some time so do not ask about release date especially on our official forum. I wrote it only because to inform people that VM Team still exists.

  • We publish new edition of our modest game version 1.37 for season 2013/2014:


    What's new in VM 2013?


    Link to download:
    http://www.dhost.info/vbmanager/ccount11/click.php?id=22


    Copy this adress and paste in a IE/Moziila adress windows

  • I would like to know which new options and improvements our foreign players want to see in next versions of our game.
    You probably know game author is not a professional game maker so one thing is what we want and second what we can rationally expect from him but you can let your imagination run away with you a little :wink: Maybe you would like to see something known from Championship Manager series or other management simulation games? Let us know in this topic http://tiny.pl/qmj9m or below my post !!!

  • Small update on season 2013/2014 based on recent Bartek's update and some work on extenting coach lists
    Changes in comparison with database VM_dbase_2013-14-v1
    - about 150 players changed their clubs
    - end of career of about 50 players (most of them become coaches)
    - circa 50 new players
    -circa 400 real coaches


    Unpack this to folder Data of VM 2013
    http://volleyballmanager.y0.pl/download/file.php?id=150

  • More than a year ago we set up our group Volleyball Manager Zone on facebook. Everyone is welcome to join our community. It is a place for players and we plann to place there informations about Volleyball Manager.
    https://www.facebook.com/groups/120108428028066/ -our group for players
    A month ago we also created our account on twitter - it is called VolleyManager- you can become our fan on twitter and read recent information about this programme.


    Our recent website is dedicated for projected Volleyball Manager 2014 - it is english spoken area and you can visit it by simple clicking on this link - https://www.facebook.com/volleyballmanager2014 .


    And of course main source of minor informations is our official forum with english spoken topics- http://volleyballmanager.y0.pl/

  • Information about new version
    I talked with Novrain VM's author and he told me that he tries to solve known bugs and implement new options but main task is to do so in conformity with the latin rule primum non nocere. And the fact that this is a non-profit project and he is a a amateur is another thread you must take under consideration when you wait for new version.


    From VM 2014 you will be able to edit the database in broad spectrum so there will be only our unofficial proposals od database for season 2014/2015 made by notable coworkers and that wont be confirmed by Novrain.

  • We are searching people which would like to help VM TEAM to update database for season 2014/2015. If you want to help inform us about it - people responsible for database are Jor and Bartek on our forum. We especially are looking for people which would like to make their native competitions and also asian competitions or any other competitions that are out of date for some time becuase they are hard to scout.

  • I've several times asked how to use an editor in VM 2013 by private messages so this is an official manual from Novrain - game author
    [quote]This topic will be used to provide you with informations how to customize VM database, what is possible since VM 2012 has been officially released. The following description concerns VM ver. 1.33 (for information about VM 2013+ database customizing options click here: viewtopic.php?f=54&t=2572).


    To edit VM database you need to create XML file with the same name like original database file and store it in /data folder (example: if the original database is named VM_dbase_2011_12.dat, your file should be named VM_dbase_2011_12.xml. You can create such a file in Notepad. You can edit existing XML file in Notepad or in MS Excel, what is more user-friendly. Database changes can be applied only by the start of the new game. There is no option to change anything in the saved game file.


    You can edit:
    1. Existing player data.
    2. New player data.
    3. Team data.


    This is an example of the sample XML file content:


    KOD: ZAZNACZ CAŁY
    <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
    <ns1:VolBaseDataSet xmlns:ns1="http://tempuri.org/VolBaseDataSet.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <ns1:Zawodnicy>
    <ns1:id>1042</ns1:id>
    <ns1:zespol>0</ns1:zespol>
    <ns1:numerWZespole>0</ns1:numerWZespole>
    </ns1:Zawodnicy>
    <ns1:Zawodnicy>
    <ns1:id>834</ns1:id>
    <ns1:zespol>121</ns1:zespol>
    <ns1:numerWZespole>1</ns1:numerWZespole>
    </ns1:Zawodnicy>
    <ns1:Zawodnicy>
    <ns1:id>705</ns1:id>
    <ns1:zespol>-1</ns1:zespol>
    <ns1:numerWZespole>0</ns1:numerWZespole>
    </ns1:Zawodnicy>
    <ns1:Zawodnicy>
    <ns1:id>2235</ns1:id>
    <ns1:zespol>275</ns1:zespol>
    <ns1:numerWZespole>2</ns1:numerWZespole>
    <ns1:pozycja>P</ns1:pozycja>
    </ns1:Zawodnicy>
    </ns1:VolBaseDataSet>


    The beginning and the end is common for every XML file:


    KOD: ZAZNACZ CAŁY
    <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
    <ns1:VolBaseDataSet xmlns:ns1="http://tempuri.org/VolBaseDataSet.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">


    -- here put your edited content


    </ns1:VolBaseDataSet>


    Meaning of tags used for editing player data:


    <ns1:Zawodnicy>
    <ns1:id>6</ns1:id>
    <!-- player's unique ID -->


    <ns1:imie>Brook</ns1:imie>
    <!-- name -->


    <ns1:nazwisko>Billings</ns1:nazwisko>
    <!-- surname -->


    <ns1:dopelniacz>Billingsa</ns1:dopelniacz>
    <!-- surname genitive in Polish language -->


    <ns1:dataUrodzenia>1980-04-30</ns1:dataUrodzenia>
    <!-- birth date in the format YYYY-MM-DD, if unkown: 1900-01-01 -->


    <ns1:narodowosc1>75</ns1:narodowosc1>
    <!-- nationality ID, see national team database ID -->


    <ns1:pozycja>A</ns1:pozycja>
    <!-- position, R: setter, A: diagonal, P: receiver, S: middle block, L: libero -->


    <ns1:wzrost>196</ns1:wzrost>
    <!-- height, numeric value -->


    <ns1:zasiegAtaku>353</ns1:zasiegAtaku>
    <!-- spike (cm), numeric value -->


    <ns1:zasiegBloku>336</ns1:zasiegBloku>
    <!-- block (cm), numeric value -->


    <ns1:sila>18</ns1:sila>
    <!-- strength, range 1-20 -->


    <ns1:skocznosc>15</ns1:skocznosc>
    <!-- jumping, range 1-20 -->


    <ns1:szybkosc>17</ns1:szybkosc>
    <!-- speed, range 1-20 -->


    <ns1:wytrzymalosc>15</ns1:wytrzymalosc>
    <!-- stamina, range 1-20 -->


    <ns1:zrecznosc>14</ns1:zrecznosc>
    <!-- agility, range 1-20 -->


    <ns1:decyzje>16</ns1:decyzje>
    <!-- decisions, range 1-20 -->


    <ns1:determinacja>16</ns1:determinacja>
    <!-- determination, range 1-20 -->


    <ns1:charyzma>10</ns1:charyzma>
    <!-- charisma, range 1-20 -->


    <ns1:intuicja>14</ns1:intuicja>
    <!-- intuition, range 1-20 -->


    <ns1:kreatywnosc>15</ns1:kreatywnosc>
    <!-- creativity, range 1-20 -->


    <ns1:atak>17</ns1:atak>
    <!-- attack, range 1-20 -->


    <ns1:blok>16</ns1:blok>
    <!-- block, range 1-20 -->


    <ns1:technika>13</ns1:technika>
    <!-- technique, range 1-20 -->


    <ns1:ustawianie>14</ns1:ustawianie>
    <!-- positioning, range 1-20 -->


    <ns1:zagrywka>15</ns1:zagrywka>
    <!-- serve, range 1-20 -->


    <ns1:doswiadczenie>14</ns1:doswiadczenie>
    <!-- experience, range 1-20 -->


    <ns1:zespol>671</ns1:zespol>
    <!-- team ID, when 0, player is on free transfer -->


    <ns1:numerWZespole>11</ns1:numerWZespole>
    <!-- shirt number, range 0-18 -->


    <ns1:kontrakt>1</ns1:kontrakt>
    <!-- contract length - must be greater than 0, when the player is assigned to any team -->
    </ns1:Zawodnicy>
    <!-- -->


    Everything, what is placed between tags <ns1:Zawodnicy> and </ns1:Zawodnicy>, concerns one player. Please note that only some database are editable in the currently released game version.


    Existing player data editing options:
    1.1. Release player on free transfer
    1.2. Assign player to the team
    1.3. Remove player from database
    1.4. Change player's position


    To edit player data you need to find the following information in the game:
    - player ID: visible in player profile and in the transfer list
    - team ID: visible in team profile: team info board


    1.1. Release player on free transfer (1st example in the code)
    Player ID = 1042 (Miguel Angel Falasca) has been released from the team Skra Bełchatów. Team ID and shirt number have to be equal to 0.


    KOD: ZAZNACZ CAŁY
    <ns1:Zawodnicy>
    <ns1:id>1042</ns1:id>
    <ns1:zespol>0</ns1:zespol>
    <ns1:numerWZespole>0</ns1:numerWZespole>
    </ns1:Zawodnicy>


    1.2. Assign player to the team (2nd example in the code)
    Player ID = 834 (Nico Freriks) joined Knack Roeselare team. His shirt number is 1. Roeselare database ID is 121. If there is currently any other player in Roeselare playing with shirt number = 1, he will be released on free transfer and Freriks will be added to the team squad.


    KOD: ZAZNACZ CAŁY
    <ns1:Zawodnicy>
    <ns1:id>834</ns1:id>
    <ns1:zespol>121</ns1:zespol>
    <ns1:numerWZespole>1</ns1:numerWZespole>
    </ns1:Zawodnicy>


    1.3. Remove player from database (3rd example in the code)
    Player ID = 705 (Sebastian Świderski) has finished his professional career. He will be replaced in the database by a randomly generated player. Database settings: team ID = -1, shirt number = 0.


    KOD: ZAZNACZ CAŁY
    <ns1:Zawodnicy>
    <ns1:id>705</ns1:id>
    <ns1:zespol>-1</ns1:zespol>
    <ns1:numerWZespole>0</ns1:numerWZespole>
    </ns1:Zawodnicy>


    1.4. Change player's position (4th example in the code)
    Player ID = 2235 (Paul Lotman) is a receiver. His playing position has to be changed to "P" - see the specification for the tag "pozycja". His team ID = 275, shirt number = 2.


    KOD: ZAZNACZ CAŁY
    <ns1:Zawodnicy>
    <ns1:id>2235</ns1:id>
    <ns1:zespol>275</ns1:zespol>
    <ns1:numerWZespole>2</ns1:numerWZespole>
    <ns1:pozycja>P</ns1:pozycja>
    </ns1:Zawodnicy>


    Useful tips: the description above looks a bit complicated, but it is necessary for the basic understanding of this issue. I advice you editing XML data in MS Excel, what is much more convenient.


    Troubleshooting tips: please check if you don't use the same player's ID twice in the file. If you edited XML file in Notepad, please also try to open it later in MS Excel. If it opens without problems, you file was made technically correct. Don't use Polish signs in the XML file!

  • [/quote]
    Still too complicated?
    I directed a movie how to use an editor but I am not sure whether you can watch it on youtube
    http://www.youtube.com/watch?v=SXDVWmeKqJM


    Should you have any questions, please post it below.

  • Because I frequently received some question we inform that we rather dont plan female version of our game. For couple of times we thought about just making female database in VM but in fact female and male volleyball are 2 different disciplines and we rather will not make female database because we have even big problems with updating male database - we have not enough people to do this in the begining of the season and we are non-profi project so time of our database designers is limited due to other more important duties. So sorry we wont make it . Only chance is that some other people will make the database instead of us and this will be added as database to our programme if Tomasz Novrain Slusarek gives his permission.