chat bubbles
 

Re: chat bubbles
 

Currently it wouldn't be simple to make. The largest problem is that, to my knowledge, default text can't be turned off. What I'd like is two commands:

disablechatdrawing; //stops Graal from drawing #c over players' heads and leaves it open for a gani script to do so instead

disablechatbox; //stops Graal from automatically sending the contents of the chat bar to the server, instead triggering the player with the text as a param, so it could be interpreted like this:

NPC Code:

---

if(actionplayerchats){

 if(strequals(#p(0),/sit)){

  //do sitting stuff

 }

 //check other commands

 else{

  setplayerprop #c,#p(0);

 }

}

---

I've already wanted to do this for Oasis chatting. I made the chat system for it, and now Stefan just needs to make the disable default chatting. :)

Well, couldn't you just make a script to detect whenever there is text above the head, and tell it to display blank text above the head instead? Then save the original text in a string for display using your alternate way.

Yeah, that'd be fairly trivial. Only downside is chat-triggered stuff would have to detect the string instead of #c

Thats not entirely true..though to us it may seem like an instant, if will not with the NPCs. You could make a system like that and STILL allow the NPCs to react to #c...I've had a problem with that in some movie systems I made...

you forget the handy dandy callnpc index,flag; ?

You can't make a players chat text disappear. Playerprop only sets the chat invisible clientside. So if that was done, you would have a player say something like "Hello!", and to the player it would display properly, but to everyone else, they would see the speech bubble, and also the chat text "Hello!". It doesn't set "" as chat serverside.

Well then, stefan will have to add another serveroptions wont he...

Really? It always worked globally for me...

Konidias, that wouldn't make much sense at all if you think about it.

The text display is client side input...if you think about it, shouldn't the script be emulating that client side input? Hitting tab, then typing in "Hello" and pressing enter would be the same thing as a script running setplayerprop #c, Hello. Its all clientside input, it would make no sense at all if Stefan made setplayerprop sent only to the client, and not to the server like typing in text manually does.

Just my thought, it seems pretty logical to me...

Trust me, I've tried this already. Yes set playerprop TEXT shows up for all players, but putting:

setplayerprop #c,;

Only works for the player. Do not ask me why because I don't know. I just know that it only works for the player.

Well...thats kinda weird. Maybe have it in a NPCW, out of the //#CLIENTSIDE area? It is just...very weird. I'll take your word for it though, I haven't tested this out myself considering I don't have a server.

Kooky. Try it with a space then. setplayerprop #c, ;

doesnt setstring whatever, #c; setplayerprop #c,;
get rid of the text and allow the scripter to still manipulate the chat?
I dont recall that working for the player only, when i used it, no one saw the chat.

Setting #c to null removes the text (though not immediately - there's an ugly little pause before it's wiped), but then what? You've just deleted #c so you don't have chat text anymore. Put it in a string? Then how would you deliver the contents of that string to the other players? Problems.

That's why the chat bubbles, goober. You'd have to ganiscript it in to keep it from bouncing all over...

you could also try a null or space character like..

setplayerprop #c,#K(0); or setplayerprop #c,#K(32);

Wait. Stop. What are you talking about?

See also: The thread title. It would be delivered in the form of chat bubbles, probably via ganiscript displaying #s(P8) or something

Yeah, I know about the chat bubbles. But the problem is getting the chat text to the other players. Putting it into an arbitrary string doesn't work. The #Px stuff is okay, but those are limited in number. And can gani scripts even access them?