PDA

View Full Version : Graal v6.1 for Mac released


Admins
03-21-2014, 09:36 AM
Version 6.11 for Mac can be downloaded from http://www.graalonline.com/downloads/Graal6.dmg
A new Windows version will also follow in a few days.

Major improvements:
- Support for international text / UTF8
- Compatible with the latest versions for iOS, Android and Facebook
- Fixed several crashing bugs

Jakov_the_Jakovasaur
03-21-2014, 06:22 PM
- Compatible with the latest versions for iOS, Android and Facebook


hello!

what effect will this have on client-exclusive servers?

thank you!

fowlplay4
03-22-2014, 12:44 AM
There seems to be a bug on Zodiac with the new client. It seems to be an issue with findareanpcs but alas I don't have a Mac so can't confirm it.

Nvm it was a check like this:

temp.npc.attr[4] == ""

that failed when the attr[4] was set to "1 1" and similar.

Seem to have to do this.last = @attr[4]; echo(this.last == @attr[4]); to compare it properly.

Playerlist + PM Bug:


All right.
Finally pinpointed it to my habit more than an actual bug.

It's when you click F7 while being able to type inside pm box.

So I double click someone's name from F7 and hit F7 again.
Instead of closing the playerlist back out like in previous versions it writes it into the Pm.

So just hitting F7 in the pm results in ___
While hitting F7 and clicking to the far right of it, as shown in the earlier video, makes ___ appear.


Link: https://www.youtube.com/watch?v=0NEXgo7c8O4&feature=youtu.be

Admins
03-25-2014, 04:11 PM
Fixed the problem with F7, released 6.111

Jakov_the_Jakovasaur
03-25-2014, 05:33 PM
- Compatible with the latest versions for iOS, Android and Facebook


hello!

what effect will this have on client-exclusive servers?

thank you!

http://www.threadbombing.com/data/media/8/bummmp.gif

Admins
03-26-2014, 02:52 PM
It just means that we might open more mobile/Facebook servers to PC version once the Windows v6.1 is released.

Gos_pira
03-26-2014, 03:20 PM
It just means that we might open more mobile/Facebook servers to PC version once the Windows v6.1 is released.
Finally! Please release Classic for PC.

Jakov_the_Jakovasaur
03-26-2014, 05:57 PM
It just means that we might open more mobile/Facebook servers to PC version once the Windows v6.1 is released.

hello!

hasnt this been something that you "might" do for a number of years?
ive seen several instances both publicly and privately where this has been confirmed and then unconfirmed and then made ambiguous again, in the mean time existing pc servers have been left to fester with the out-dated policies

thank you for the swift response!

Stephen
03-26-2014, 06:00 PM
hello!

hasnt this been something that you "might" do for a number of years?
ive seen several instances both publicly and privately where this has been confirmed and then unconfirmed and then made ambiguous again, in the mean time existing pc servers have been left to fester with the out-dated policies

thank you for the swift response!
What you're describing is an over-arching goal. I anticipate this is something they're working towards.

Jakov_the_Jakovasaur
03-26-2014, 06:28 PM
for it to be a goal it needs to be something you stick to and not keep changing your mind about it or defaulting to "hm not sure", otherwise its simply an idea

Stephen
03-26-2014, 09:42 PM
for it to be a goal it needs to be something you stick to and not keep changing your mind about it or defaulting to "hm not sure", otherwise its simply an idea
This looks pretty clear to me.

Major improvements:
- Support for international text / UTF8
- Compatible with the latest versions for iOS, Android and Facebook
- Fixed several crashing bugs

Jakov_the_Jakovasaur
03-26-2014, 09:55 PM
This looks pretty clear to me.

if that is how you interpret it then fair enough, but it is possibly worth mentioning that it was compatible with mobile & facebook the last time the v6 client was updated, and nothing else has changed since then

though you would think graal administration would be gracious enough to give playerworld administration members actual knowledge of what to expect rather than leaving everyone guessing for so long

Torankusu
03-27-2014, 12:59 AM
though you would think graal administration would be gracious enough to give playerworld administration members actual knowledge of what to expect rather than leaving everyone guessing for so long

I'd assume improved security features iOS and FB servers already have integrated in regards to user detection, but seem to be ignored by the pc client.

But again, keyword, assume.

Gos_pira
03-27-2014, 01:19 PM
I wish that Eurocenter would be more open and clear about their plans/goals and seriously take suggestions into consideration when developing the engine, both from players and developers.

Maybe a developer blog? Or a milestone plan? Even if milestones are changed due to unexpected circumstances we'd know by the information being changed somewhere. Instead of just blindly assuming that "maybe next year".

Examples of promises that hasn't happened: New dev tools, "flying tech", guides for how to achieve FB/iOS/Android status for your server, and more.

We've been let down so many times at this point, so we know not to expect anything to happen. If it happens, that's great, otherwise, bummer.

Something like this might be useful for everyone. (https://trello.com/b/lG8jtz6v/rust-main)

Being able to vote for features and see what's going on is great, and everything doesn't needs to be visible either.

Jakov_the_Jakovasaur
03-29-2014, 11:34 AM
the problem described by fowlplay4 also seems to be happening for player.attr[] values with mac users, and likewise i do not use mac so cant confirm or debug it

I wish that Eurocenter would be more open and clear about their plans/goals

i have it on reliable authority that their logic is "we dont announce our plans because people complain when it doesnt happen". they dont seem to understand that it is mostly the lack of an explanation or status update which has caused people to complain in the past, effectively causing a vicious cycle

there is/was also an element of planning to do things which would inconvenience certain section(s) of the community, like wanting iera and iclassic respectively to amalgamate era and gta, knowing full well that an actual merge is impossible

Meph
04-01-2014, 08:14 PM
Super excited to see the ball is rolling with this.

When can we expect to see Era iPhone released for this new client?
I know a lot of Era PC players that have been waiting for client access.

http://puu.sh/7SqVw.jpg

Jakov_the_Jakovasaur
05-25-2014, 09:12 PM
Version 6.11 for Mac can be downloaded from http://www.graalonline.com/downloads/Graal6.dmg
A new Windows version will also follow in a few days.

Major improvements:
- Support for international text / UTF8
- Compatible with the latest versions for iOS, Android and Facebook
- Fixed several crashing bugs

hello!

whats the status on the new windows version?

there are some bugs with the mac version which really need to be fixed, but if thats going to take a while then it may also help if windows developers could debug them, a good suggestion i heard about was to make an equivalent windows client as an optional download on the login server

thank you!

lTBSl
06-12-2014, 07:25 AM
When will a Tile Editor be released for Mac? Not GConstruct?? Has this been talked about?

Jakov_the_Jakovasaur
06-15-2014, 09:41 AM
there is definitely a bug on the new mac client when it comes to reading player attr[] values which contain numbers like so: "1 0 0.1 etc", it also seems to be the case even when trying to concatenate it using @

this means that you cant use tokenize() on a space separated list of numbers within a player attr

Rave_J
06-15-2014, 06:41 PM
I know when they talk about releasing the clients on iPhone and androids devices that they were going to work on more updated dev tools but it hasn't happen yet. But if we do will prob be online tools like web based.

Jakov_the_Jakovasaur
07-06-2014, 02:22 PM
hello!

ive heard from a reliable source that the equivalent new windows client has been ready for some time but is no longer planned to be released, is this true?

then again with the bug for using tokenize on a player.attr value this is probably a good thing

callimuc
07-06-2014, 05:54 PM
And the stupid openGL bug which won't save the set option within the F3 menu. It's been a long time now we've had to deal with it and I don't get why a small update fixing at least that problem can't be released

Jakov_the_Jakovasaur
08-03-2014, 12:44 PM
just found that the bug with attr values starting with a number also applies to when doing:


GuiShowImgCtrl.actor.attr[index] = "1_OtherRandomChars";


i dont know who there is that can fix it now, but it should be fixed

Restraint
08-22-2014, 01:25 AM
just found that the bug with attr values starting with a number also applies to when doing:


GuiShowImgCtrl.actor.attr[index] = "1_OtherRandomChars";


i dont know who there is that can fix it now, but it should be fixed

I reported this a long time ago, when I ran into this situation with an account of mine ("100Zero100") getting passed server-to-client seemingly as "100"

The problem involves datatyping.

Although Graal does not have explicit datatypes, it does have IMPLICIT datatypes, which can be grabbed or corrected by using @.

For example:


temp.a = nil;
temp.b = "";
if (a == b) { // true
if (@a == @b) { // false


The former is true because null int and null string are the same when they're just "blob" datatypes. The latter is false because null int and null string are not the same when their datatype is invoked!

To fix your problem, simply put an @ before the attr.

Example:


function onCreated() {
this.attr[5] = "100Zero100";
}
//#CLIENTSIDE
function onCreated() {
sleep(1);
this.chat = this.attr[5];
}


Chat sets to: 100


function onCreated() {
this.attr[5] = "100Zero100";
}
//#CLIENTSIDE
function onCreated() {
sleep(1);
this.chat = @this.attr[5];
}


Chat sets to: 100Zero100

Hope that helps to shed some light and resolve these types of bugs.

Jakov_the_Jakovasaur
08-22-2014, 05:40 PM
I reported this a long time ago, when I ran into this situation with an account of mine ("100Zero100") getting passed server-to-client seemingly as "100"

The problem involves datatyping.

Although Graal does not have explicit datatypes, it does have IMPLICIT datatypes, which can be grabbed or corrected by using @.

For example:


temp.a = nil;
temp.b = "";
if (a == b) { // true
if (@a == @b) { // false


The former is true because null int and null string are the same when they're just "blob" datatypes. The latter is false because null int and null string are not the same when their datatype is invoked!

To fix your problem, simply put an @ before the attr.

Example:


function onCreated() {
this.attr[5] = "100Zero100";
}
//#CLIENTSIDE
function onCreated() {
sleep(1);
this.chat = this.attr[5];
}


Chat sets to: 100


function onCreated() {
this.attr[5] = "100Zero100";
}
//#CLIENTSIDE
function onCreated() {
sleep(1);
this.chat = @this.attr[5];
}


Chat sets to: 100Zero100

Hope that helps to shed some light and resolve these types of bugs.

hello!

the problem i mentioned previously involved writing to an attr rather than reading

as for the original problem i mentioned where it does involve reading an attr, usually using the concatenate method does fix it however even that fails in the latest mac client

Restraint
08-23-2014, 08:32 PM
hello!

the problem i mentioned previously involved writing to an attr rather than reading

as for the original problem i mentioned where it does involve reading an attr, usually using the concatenate method does fix it however even that fails in the latest mac client

My apologies. I have run into this question so many times I had assumed it was this (relatively common) Graal bug and not something new and more sinister.

How can you tell if the problem is with writing or reading the attr? If the problem is with reading and even the concatenation method doesn't fix it, then it would appear the same as writing!

Have you troubleshot it in other ways? Such as..

blah.attr[5] = "1_words";

blah.attr[5].length() -- is this 1 or is it 7?
blah.attr[5] @ "" -- is this still 1?

And have you tried it with different delimiters than "_" with no luck?

I suppose the worst case scenario involves setting the data acrossed multiple .attr[]'s or balling the data into one attr via numbers, and that's your current workaround?

I don't have a Mac unfortunately, so I'm not able to test any of this to see.

Jakov_the_Jakovasaur
08-23-2014, 08:58 PM
How can you tell if the problem is with writing or reading the attr? If the problem is with reading and even the concatenation method doesn't fix it, then it would appear the same as writing!

if i were to do:

GuiShowImgCtrl.actor.attr[1] = "timestamp_otherCharacters.png";

which is basically to set a hat image on a gui control, the hat is not displayed, even if i attempt to use the concatenation method when writing it

after doing echo(GuiShowImgCtrl.actor.attr[1]); it does output the correct filename, which is also a valid downloadable file which would for example download if used as an npc image, which leads me to believe that its a problem with the client itself in regards to interpreting the attr value

with that said, i have since noticed that the problem also applies to player.attr[i] and it is not exclusive to the mac client, whereas the original problem i mentioned with reading + tokenizing a player.attr[i] value such as "1 2 3" is exclusive to mac

Jakov_the_Jakovasaur
09-03-2014, 11:38 PM
the problem described by fowlplay4 also seems to be happening for player.attr[] values with mac users, and likewise i do not use mac so cant confirm or debug it


i just noticed now there that there is actually not a bug reading such strings which begin with a number within player attributes for the new mac client, it simply appeared to be the case because during my attempts to debug a problem the real bug turned out to be that a string value was being treated as if it were NULL

example:


function onCreated()
this.hash = new TStaticVar();

function something() {
//set these attributes just for the sake of an example
player.attr[5] = "1 3 0.05";
player.attr[6] = "2 4 0.1";
player.attr[7] = "0 0";

//lets just pretend that this is defined as an array
temp.save = this.hash.(@ player.account);

temp.h = player.attr[5] @ player.attr[6] @ player.attr[7];

echo(temp.h); //outputs: 1 3 0.052 4 0.10 0

/*is never true because temp.save[6] starts as NULL
and temp.h is treated as NULL when it actually isnt*/
if (temp.h != temp.save[6]) {
this.doSomethingElse(player);
temp.save[6] = temp.h;
this.hash.(@ player.account) = temp.save;
}

echo(temp.h == NULL); //outputs: 1

}



this example should show that there is a bug with concatenating strings which consist of numbers in such a way, as temp.h is being treated as if it is NULL when it is not NULL

Ceasar
12-05-2015, 11:54 PM
i don't have linux but i feel that there is no love for linux :cry: