Page 1 of 3

Jaymod 2.3.0 update

Posted: Wed May 18, 2011 10:42 am
by BubbaG1
Any update on 2.3.0 progress? No rush, just curious... :)

Re: Jaymod 2.3.0 update

Posted: Sun Aug 07, 2011 9:23 am
by Dragon
Does no response mean there is no progress? :cry:

Re: Jaymod 2.3.0 update

Posted: Mon Aug 08, 2011 10:30 am
by hellreturn
tbh I am more concerned about security fixes and omni bot fixes. I just hope Jaybird releases one new build asap.

Re: Jaymod 2.3.0 update

Posted: Thu Aug 25, 2011 11:00 am
by Dragon
hellreturn wrote:I just hope Jaybird releases one new build asap.
Not only you I think :roll:

Re: Jaymod 2.3.0 update

Posted: Sat Sep 10, 2011 5:41 am
by Dragon
Any news?

Re: Jaymod 2.3.0 update

Posted: Mon Sep 12, 2011 7:59 am
by Tankey
Jaybird again AFK? D:

Bad new is bad..

Re: Jaymod 2.3.0 update

Posted: Tue Sep 13, 2011 6:53 am
by Dragon
Still no Lua and even no reacts on propositions/requests.

Re: Jaymod 2.3.0 update

Posted: Tue Sep 13, 2011 7:04 am
by Ligustah
Jaybird has never made any promises about when to relase the new version, and neither did he make a secret about that this is a fun spare time project for him. There's no point in asking over and over again, it just won't make him do it any faster.

Re: Jaymod 2.3.0 update

Posted: Tue Sep 13, 2011 8:36 am
by Dragon
But it will make the situation clear... No new Jaymods - OK, no more spam here or in "Features Requests" forum.

Re: Jaymod 2.3.0 update

Posted: Wed Sep 14, 2011 7:47 pm
by hellreturn
I am deadly waiting for 2 fixes and 1 enhancement:

1. server crash cos of omni.
2. Server crash cos of security
3. Auto move to spec if user inactive for defined xx amount of seconds.

I never understood why Jaybird doesn't add someone in his dev team who can keep up with the mod. He even didn't provided debug build to omni team for helping with crash issues. *me sad*

Re: Jaymod 2.3.0 update

Posted: Thu Sep 15, 2011 4:47 am
by Ligustah
hellreturn wrote:2. Server crash cos of security
Would you mind explaining that one?

Re: Jaymod 2.3.0 update

Posted: Thu Sep 15, 2011 5:37 pm
by hellreturn
Ligustah wrote:
hellreturn wrote:2. Server crash cos of security
Would you mind explaining that one?
Sorry, no! I am really tired banning those players and I really don't want to share it with anyone.. i told to jaybird but no idea when he is going to fix it! I told him at the time of last release in itself.

No offense or disrespect intended.

Re: Jaymod 2.3.0 update

Posted: Sat Sep 17, 2011 6:52 am
by Dragon
And the bug "CvOps with SMG" wasn't fixed yet AFAIK.

Re: Jaymod 2.3.0 update

Posted: Sat Sep 17, 2011 8:46 am
by Ligustah
hellreturn wrote:Sorry, no! I am really tired banning those players and I really don't want to share it with anyone..
Ok, i was just asking because I wrote some bugfixes (similar to combined fixes for LUA) using QMM for the older Jaymod releases. I haven't quite kept track of what Jaybird fixed and which exploits still work, so what you're calling unfixed might be fixed by my plugin, and if it's not i'd really appreciate some information so i can add it to my list to get it fixed.

No obligations of course, just asking ;)

Re: Jaymod 2.3.0 update

Posted: Sun Sep 18, 2011 8:12 am
by hellreturn
Ligustah wrote:
hellreturn wrote:Sorry, no! I am really tired banning those players and I really don't want to share it with anyone..
Ok, i was just asking because I wrote some bugfixes (similar to combined fixes for LUA) using QMM for the older Jaymod releases. I haven't quite kept track of what Jaybird fixed and which exploits still work, so what you're calling unfixed might be fixed by my plugin, and if it's not i'd really appreciate some information so i can add it to my list to get it fixed.

No obligations of course, just asking ;)
I understand but for some reason QMM adds lag on 30+ server and sometimes it's the cause of crash or used to be before when i tested with jaymod and etpub and omni .71/.66

I tried to run server with least add ons to avoid any issue and hence waiting for next release.

@Dragon: I thought that issue is fixed in 2.2.0? No?