-
Notifications
You must be signed in to change notification settings - Fork 398
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Seeking Collaborators for DayZ Epoch #1660
Comments
I am here to help Awol. Was waiting for this update for a long time. |
Also wanting to help. Also waiting for *.2. What about packing-in some Overwatch-included mods ? Admins |
let me know what I can do to help.. sorry I haven't been around that much On Fri, Jun 5, 2015 at 9:57 AM, slunski [email protected] wrote:
|
[11:27:01 AM | Edited 11:27:18 AM] David Foltyn: new update for OA beta is out, more likely final in terms of core unless you got something new (bugs) |
So, who will takeover Epoch? Do you have somebody in mind @vbawol? |
I'm willing to help test if there's a server available at some point. |
aka Zupa. Forked, will loop over the issues and do pull requests. |
@Windmolders has been added as a collaborator so he may merge pull requests. |
Hey guys, I'm willing to lend a hand around here again. I've set up a test server @ 37.59.229.103 port 2402 the server name is "Epoch 1.0.6 Unofficial Test Server" and the password is epochtest106 I will update the files on the test server as often as needed but the quickest method would be to set up your own test server on your local machine and use the test server I have set up for extended testing. I will upload the a ZIP of the client .PBO files the server is running shortly. the ZIP will NOT contain all necessary files, you will need to copy an existing Epoch 1.0.5.1 folder and overwrite the files with the ones I uploaded. |
nice |
I'm aware of that, but a sign of someone interested in the project might bring some people willing to lend a hand. Awol doesn't seem against this becoming a community project either. if it doesn't there's no loss. I'm obviously not looking to takeover this repo by myself, so I don't see lending a hand and simply updating a test server once or twice a week as much bother. |
It's nice to see interessent in the matter. Me myself and I might be helping again in the future aswell, been extremely bussy as i promoted to teamlead and do some work on the sides. But as soon as i can get my hands abit back on arma, I'm happy to help :). I can assist quickly for accepting merge request and stuff if you need it. |
nice job, thanks Zupa. I am also setting up a new rig. should be ready in On Mon, Dec 14, 2015 at 2:02 PM, Zupa [email protected] wrote:
|
This project has been open for anyone to fork since its inception. The work is released so that other people can build upon it and hopefully contribute back to the project. @icomrade Sounds good, please let me know if there is anything you need assistance with. @Gr8z, @icomrade is a contributing developer on the project I think he knows the status of the project. From what I have heard the next near EOL Arma 2 patch is due out soon: |
@ebaydayz Thanks for pointing out the code pbo was missing. Considering the lack of interest since December I took the server down since I'm working on putting up an ArmA 3 server. However, I'll set it up again provided there's some interest in the project still. |
@ebaydayz was added as a collaborator, thanks joining in the fun! Please make sure you guys collaborate as much as possible about your changes and please do let me know if you need any assistance. |
I made a discord channel if any of you guys want to ask me any questions or just talk with each other please join: https://discord.gg/0k4ynDDCsnQ5WpJo |
FYI, I have transfered the github to EpochModTeam org on github. old links will be redirected but the new link is now: https://github.com/EpochModTeam/DayZ-Epoch |
Glad to see you continued work on the mod guys @ebaydayz @icomrade. Hope to see an update to latest DayZ mod code in future. Thank you a lot. |
@vbawol @Windmolders if you want i can run a test server for the community and keep it up to date everytime there is a push. If interested :)? |
I have a dedicated server, but it's being updated to server 2016 so I haven't updated it recently (I've kept it down for the past couple days), I will update it today since the host literally just sent me an email about the setup being finished. We encourage everyone to host a test server and send logs and or feedback to us |
@icomrade ah, well i have enough space left :) so i'm not that bothered. I love arma 2, and i don't mind maintaining it. ^^ so just let me know if its okay :P. I will post feedback when i've got things :). Is it possible to add the testserver in the thread when its up? |
I've been having some trouble getting the server up on windows server 2016. It appears the server doesn't load .dll files anymore, either from the mod folders or directly in the A2OA root. |
I hear the references to unblocking DLLs in quite a lot of howtos, could that be the case? I think they suggest right click DLL and goto unblock On 3 November 2016 8:28:07 AM NZDT, icomrade [email protected] wrote:
|
First thing I checked, it's not as big of an issue in 2016 as it was in 2012. |
@icomrade folder permissions and c++ runtimes. Set the Arma 2 folder to full access to group "Everyone" or alternately make sure you're running it as an administrator (log in with an account that is in the administrator group, don't bother with "run as"). Make sure you got all your c++ runtimes installed as well. I would also not run it from the default steam install location (%program files%). I would install steam elsewhere like directly on the root of the drive (or just run the server from a copy of OA in the root, but copy the A2 "addons" folder into it if you do that). I installed steam in the root of the drive in order to avoid folder permissions in 2012. I actually have had no issue with 2012 R2 and running Arma, it just worked right out of the box for the most part (after installing the appropriate runtimes). I have not played with 2016 yet, you may need to sign your dlls now. That's always a possibility. Also look in the application, system and security windows event logs for errors, it should be logging the fact that it's preventing hive from being loaded into memory. Usually you only have to sign drivers, but they may have made a change to make malware harder to infect a system by requiring dlls and executables to be signed. Also set compatibility for the arma executables if none of this works. It could be something new with running x86 code on x64 in 2016. One other thing to check is DEP, you could switch it to essential windows services and programs only or add exceptions for the arma server executable and hive. I highly doubt the dll is being executed or loaded in the default heap or stack, but who knows, it's Arma and this version is pretty old... Most likely it's folder permissions. Check the permissions of the user logged in, right click folder >> properties >> security >> advanced >> effective access >> pick user >> view effective access. |
was missing the 2010 redistributable... thanks for the suggestions, I swear I installed every last one, I'm surprised that I wasn't getting any errors |
Yeah C++ redistributables happens to me whenever I install a new mod somewhere, I forget at least one and spend 2 days trying to figure out what went wrong :P |
Since November 2012 the source code for DayZ Epoch as been available and over the years we have had many contributors to the project. Most are no longer active however, and the task of maintaining DayZ: Epoch is monumental for any one person.
If you want to become a Collaborator on the DayZ Epoch Project you must:
If some of you are willing to put some work in, I am willing pack and push at least one more update for DayZ Epoch.
Notes
The EOL (End Of Life) patch for Arma 2 will come out soon and is already on the beta branch for testing. This update will inevitably break something and DayZ Epoch may need updates. https://twitter.com/FoltynD/status/600680145314140160
The text was updated successfully, but these errors were encountered: