Uro

Great, now I've creamed my pants

No, not in any way related or affiliated.
 
It just boggles my mind how entitled people become after making a donation. I get it's annoying that something stops working (for you), but that does not mean the creator owes you in any way.

Don't update to any 1.63 steam beta patch until commander is updated, gamespy actually shuts down, or epoch moves to 1.0.5.2.

How about this..
 
"A3Epoch: VMS"
"Vampire's Mission System for Arma 3 Epoch Mod, from the Creator of DZMS for A2 DayzEpoch Mod"
 
Keeps it specific and to the point, without throwing in any confusion.
 
Some of the suggestions above such as A3MS suggest a generic mission system for Arma 3, not one tailored to A3Epoch

Just grab most of the update files from github to fix some of the more important issues (crafting ore).
 
No need to push this out until commander updates as it will destroy the epoch community.

Good luck with this!
 
I started making a custom map ages ago, I got as far as getting a base map done with the BIS tools n some other tools, even got banned from Google Earth for 48 hrs (Twice!!) for downloading too much sattellite data too fast :D :D :rolleyes:
 
Then I lost interest due to the sheer amount of time it takes to construct a map from nothing and I discovered my final base map render was too big for Arma2 to handle :D
 
But since your going to attempt joining two maps, most of the hard work should be done already. 
 
Your gonna need a lot of patience for this project :)

I've had to sort a few clients out with this issue, I think one of the ways it's caused by all the beta-patches / steam patches people have updated to and mismatched versions of files due to the update path.
 
Once I get them to validate thier cache, launch the vanilla game (to regenerate registry keys), reinstall beta patch (I haven't moved over to steam patch yet :D ) they seem to be fine.
 
Although sometimes I have to get them to switch versions in the Betas tab in Steam (NONE>1.62>NONE) and revert it back which forces Steam to update the files correctly and then re-validate thier cache, and run the vanilla A2OA game, before joining any servers.
 
 
So I can confirm verifying and reinstalling whatever patch your using seems to fix this isssue for the people I've assisted.
 
And from the people I've helped it does seem to be mismatched file versions, OR they haven't run vanilla A2OA after updating.
 
 
The error people get when they have a black screen but can move / hear sound, from my experience is a mission file error somewhere, and you can fix this by looking through your server and client rpt file for any errors and fixing those.  I had one line I forgot to put in and it broke one of my servers when I updated to 1.0.5.1

Have you added the break leg for mismatched scripts script ? 

will be fixed in the next release

What you get when you got 2 overpoch servers :p

Looks like it was an error with the loot init. Didn't update it fully with 1.0.5.x

Herpderp

When you purchase Infistar your get a file called README that you are supposed to read.
 
If you would have done what the file says to do instead of posting here, all your problems would already be solved.
(There is even a visual installation if you can't read)

Instructions unclear, accidentally build a bridge. Please advise!

DayZ Epoch Server Installer   Hello folks I have created a Installer that will simply install your server for you on your dedicated box or home PC. All you have to do is run the DayZ Epoch Server SETUP.exe (read....README.txt) and follow the instructions as you go. This installer downloads the most recent version of the Epoch and BEC files so you can also use it too update when the time comes.    This package also includes some tools that help you manage your server including DayZ File Rotator - Rotates your new PBO or config files in after restart so no need for waiting around  Dayz Hive Rotator - Rotates your Hive files so you can have a custom day/night cycle   Please comment bellow or use the credentials provided in the readme.txt with any issues or help you may need   Thanks!   --Possible issues   Admin prompt issue with File Rotate tool on startup   --DOWNLOAD=============================== http://www.craftdoge.com/downloads/snow.html Thanks to Hollowaddiction of Craftdodge for hosting the download   Github - Source Code (for people uncomfortable with .exe) https://github.com/Snow724/Epoch-Server-Installer

Yeah , I gotcha. If people are sketchy on using it a understand.My first plan was to just release the batch file but I decided to convert to exe just for the sake of updates and the compiled and nicer outcome. I will most likely release the source code if it will put some people at ease :D
 
thanks

You should put this on a github so we can see the source code, or at least let awol have a look at it.
 
I'm not saying you've created anything nasty but using unvalidated third party software can sometimes pose risks. :)

That's a very shortsighted point of view.
The new command getPlayerUIDOld is clearly stated as a temporary stopgap measure and not intended to be used indefinitely.
Any attempt to keep backward compatibility for a longer interval is bound to fail, imo and any mod that makes use of getPlayerUIDOld to avoid issues or the pain of upgrading now, will have problems, later.
 
Imo the most elegant and only future-proof way to go is to change the DB fields and the according read/write procedures in the hiveExt.dll.
 
Now I'll sound like a wiseass, but: changing the dll now would be a lot easier if from the beginning one would have used DB column specific typedefs instead of standard variable types. Then the conversion for object_Data_characterID could have been done simply by changing the corresponding object_Data_characterID_type from int to long (or whatever standard type covers the needed range) in a central header file instead of having to hunt down every occurrence.

That's it. We're putting fucking tele-tubbies in Epoch.

It's going to be officially re-named "Tubby Poch; might have good mod"

I would think with the getPlayerUID if a player who doesn't have a PlayerUID it will report back the SteamID instead.
 
I wouldn't want to rely on the getPlayerUIDOld command for too long though, as it will be classed as legacy support, and like all legacy things they eventually get phased out over time as they are replaced with newer better things :)

They are referring to it as a hotfix so I think they will be soon.

Finally some headway with information from BIS, hope they push this through to the stabel branch asap :D

Thanks to David Foltyn:

check the new OA 1.63 beta (for upcoming hotfix) it has now getplayerUIDold command

A2: OA 1.63 hotfix beta updated with - fixed ui (squad url, steamID) - new command GetPlayerUIDOld ... some more fixes may follow

 

TUTORIAL/HOW-TO: CUSTOM SELF-BLOODBAG for EPOCH 1.0.5+
 
 
For people using maca134's right click options and wanting to run their own Self Tranfuse / Bloodbag scripts within Epoch 1.0.5 without having "Self Transfuse" & "Self Bloodbag" right click options on Bloodbags.
 
 
Why did I make this guide?

Some of us use custom self blood scripts with features other than in the default one.
Call it OCD but I don't like having duplicate Self Blood options in right click menus!
And also because setting DZE_SelfTransfuse = false; variable in the mission init file disables all right click options on bloodbags.
 
 
The following guide lets you use your own self bloodbag script utilising the existing self-transfuse code within Epoch 1.0.5+
 
 
Difficulty:

Easy/Moderate
 
 
Required:

Notepad++
PBO Manager / PBO tools.
Epoch 1.0.5 dayz_code.pbo
A working custom compiles.sqf in your mission file.
A working self-bloodbag script in your mission file.


Dont have a custom compiles? The forum search function and Google are your friends.


NB: For the benefit of this guide I'm using a folder called \custom\ in my mission file, yours may be different, change the appropriate lines below.
 
 
 
Step 1

In your mission file open up your custom compiles.sqf

Add the following:
player_useMeds =            compile preprocessFileLineNumbers "custom\player_useMeds.sqf"; Save the file.



Step 2


Open up your dayz_code.pbo

Copy this file \dayz_code\actions\player_useMeds.sqf

Paste it in the \custom\ folder in your mission file.



Step 3


Open the player_useMeds.sqf that you just put in your mission file.

Look for the line:
 
    case "ItemBloodbag": {         _id = [0,0,0,[player]] execVM "\z\addons\dayz_code\medical\self_transfusion.sqf"; Change it to this:
(or whatever your self-bloodbag script is called!)
 
    case "ItemBloodbag": {         _id = [0,0,0,[player]] execVM "custom\self_bloodbag.sqf"; Save the file.
    
 
Step 4
 
Open the init.sqf in your Mission file.

Scroll down to your DZE_ variables.

Add this line:
 
DZE_SelfTransfuse = true; Save the file.

Repack your mission file into a PBO.

    
 
Optional:

If you use maca134's right click menu http://epochservers.com/viewtopic.php?f=14&t=13
You can remove the options for Bloodbags.


Open your extra_rc.hpp in Notepad++

Remove these lines:
 
    class ItemBloodbag {         class UseBB {             text = "Use Bloodbag";             script = "execVM 'custom\SelfBB.sqf'";         };     };    
Save the file.

Repack your mission file into a PBO.  
 
 
 
Your self-bloodbag script now uses the built-in Epoch code to run!!

We are going for the long haul here guys. The A3 Epoch project will likely take a few years before we are at at 100% finished state. Alpha status will last until 1.0 at which point we will enter the beta phase.
 
Beta phase will be mostly feature complete with a slower/larger update cycles. Closed alpha is likely to last up to version 0.5 and hosting will be done by our own developers and will only allow whitelisted players to join.
 
Open alpha will likely start sometime after 0.5 (50% complete) and at this time we will start to welcome some server hosts to join in the testing. During open alpha we are going to only allow server hosting via an application process with acceptance of specific terms. For GSP's that want to host during the alpha we will ask that customers ability to access server files is limited from making any modifications to our files.
 
All of this is so that we can get proper feedback on our own work and fix any issues that are from the mod and hopefully make the game we all want to play.
 
Discussion here: