Thanks to you for the clarification on it :P:
Printable View
You know where I failed? Because of the damn divorce that didn't work either and about which I had no idea... So after each divorce when I was taking another marriage and logging off-in it always worked <lol> I feel so dumb... But anyway... At least we know how to bypass this bug. And yes, I was unable to get my marriage to work at all, and after getting 343's code it worked after first try, so maybe I was too fast with saying that I found out what was wrong.
Maybe you just forgot, that normal dev do a weekly tests to be sure that they are right. Or minimum a 10-20 testing marriages and divorces in a day.
I am using 343s release and it already has the hex codes posted in this thread (the first ones). Unfortunately the marriage still isn't working for me.
I've tried many ways of getting it to stick by reading the forums, like leaving party, staying online for 15 mins, or force log out and staying offline for 15 mins. All attempts made the marriage stick but as soon as you leave the chapel and relog, it resets again.
I've noticed some people say they can get it working and some can't, could it be that the chmod of the files in the folder /PWServer/gamedbd/dbhomewdb/dbdata/ may be having an effect?
:lol: Probably way off but I thought I may as well ask
Squad with your beloved > Enter the Chapel > Marry you > Dismiss the squad > Both force log out > Wait 15min before login again.
Then you should be fine. If not, then Idk. It does work for my players on my server.
Ok I'll give that a go, I only waited 10 mins before so maybe that's why it didn't stick.
Hmm on russian dev forum i just saw this maybe can help...
Сообщение
P.s. i tryed look for it but coudlnt actually find those values
I have the same codes as well and for some reason mine works, as for 343's files i have identicle files related to wedding his works mine works but every release put out they dont work. i literally screwed around with mine for weeks to get it to work. occasionally it has its bugs but most of the time works.
i have noticed having all instances open or running till you got low ram and low swap left it tends to ignore it all
just some ideas :thumbup:
it's a litle weird with this mariage system, i remember when long time a go i have real 1.3.6 task data and using beastie server files. the meriege was working like official. but since i use 1.4.2 task data, it was change everything....
ok i tested this a lot and its odd.
i coppied the EXACT stucture as what my server runs to a VBOX and VMWare. this is what iv have discovered.
95% of the it will fail and the other 5% is half married (female) and sticks for half an hour or so or till you do another logout.
but on my actual server running dedicated works every time instantly.
i have a VERY STRONG theory to whats causing this to happen. this also results in failed invasions you run it and after a couple minutes or less it completely stops.
:thumbup:i have a theory and im pretty damn sure its right:thumbup:
will tell what it is once i test this theory.
first obvious one is. dont use vbox or vmware hahahaha:w00t:
Your theory is wrong.... where is trollface smilie...
you dont even know my theory.... and ive tested and works for me
well from extreme testing its based on cpu well for my end if your cpu is running high then the chances are it will fail. basicly ran everything to bog my ram up and my cpu like vmware or vbox does and when its around 90 - 100% the marriage quest never works. turned everything right off and made the cpu go down to about 30% and seemed to work fine along the fact of only using 1gb of ram never had a problem. also looking into this java system i noticed 3 services running on it and each one does something different, when i closed it, it stopped working and so on. but dont think the java has anything to do with it. so far this is what ive discovered. if you run the system low cpu and ram then marriage works flawlessly
well it works for me. and the CPU i also discovered if its at 100% and you run an invasion the whole invasion stops after a few seconds to a few minutes depending what you have going on.
these are just things ive detected and noticed and works for me, try for yourself and if it dont work maybe someone will figure out something that prevents it.