MooClick : Name Bugs

[Dynamite]

It's been a while since I've used MooApi, or even posted another topic about something I'm stuck in.

But this is simple. I am using the text blitter to create names that float on the users heads. The problem is that when more then 2 people (3 or more people) are playing in the online engine then the text blitters stop following the users heads, so they just remain there floating.

There is only one event that makes it follow the user, so I'm guessing that the condition is interfered with the 3rd or more users.
Here is the condition that makes it follow the users:

Text$( "User Text Blitter" )
IS EQUAL TO
PCU_GetName$( "MooClick" )

Set position to 0,0 from user.

That is, if the text of the text blitter is equal to the Username then it sets it possition to 0,0 of the user.

So how come the 3rd player messes these events up?

PS, Each player has a different username not the same name.

[James]

You can't do that, it won't automatically select the right user.

You should try testing OINC- it's easier to do with that.

[Spike]

Try using PCU_GetID rather than PCU_GetName - Just off the top of my head so unsure if it'll make the difference.

Very keen to promote OINC huh Jamie . It's in alpha still remember, thats not stable for complete apps.

[DizzyDoo]

OINC is in alpha Spike, yes, but it deals with names in a different way. You can change a name much easier.

[Kimera]

That does not solve the issue DizzyDoo as the OINC object has many other issues, as pointed out in the OINC sub-forum, and should not be used for a release product since it's in alpha format, your just asking for issues when you use a product not ready for release as it tends to work fine to solve an immediate issue but you often find that a funtion you need later just does not work, and this is with any alpha product.

Keep in mind that if you start to use and alpha/beta product and have issues the developers first response will be to let you know it's in alpha/beta stage. Not that they will not fix it but now your timeline is based on theirs.

I would love to see the OINC finished yesterday but that would be rude of me to expect that type of response from Jamie as the work that Jamie has already done with the object is wonderful and I understand there is a web based interface for the server that is being added if not already released. My choice is to continue with MOO and watch the OINC progress. Even after the extention is finished there will be fixes that need to be done to polish it off but that would be the time to start using it.

If Jamie is anything like me, the more he developes the more he finds he can add to it, the longer it takes to finish and at some point you get it all done.

More On Topic...

Use spread value on the users and the text blitter...
- 0r -
use a alt string for the names for both...

by doing so you can loop the number of users to keep the names above their heads.

Done!

Hope this helps,
K

[izac]

You can't do that, it won't automatically select the right user.

You should try testing OINC- it's easier to do with that.

MooClick is just fine for these sort of things.

I think we'd rather use something that works, than something that will have issues.

[James]

Moo has issues, and if nobody helps test OINC, it's not going to improve, is it?

[Kimera]

Well, here we go...

Moo does not use UDP from what I understand, it also has an issue with blasting text from what I have heard but I have never had the issue myself.

DR never worked and we knew that going it to it years ago, thats part of the UDP thing from what I understand. Nothing I am aware of prevents the object from being used in production and just because you have created a partial product to replace it does not discount the value that MOO has brought to MMF for years.

You keep saying Moo has issues as you promote OINC but what are those issues? You want people to use your product yet when I sent you a PM asking for docs your reply, rather than an answer, was to tell me, (not ask me) to post it in the OINC sub-forum...

"You should post this in the OINC sub-forum."

That's all I got! I did not post this in the forum for good reason, I am tiered of peoples snide remarks and quick tempers. It even comes from people you try to help such as this example that just took place...

http://www.clickteam.com/epicenter/ubbthreads.php?ubb=showflat&Number=110234&fpart=2

I tried to help MechaBowser with an issue and because he did not have the foresight to put all the details of what he was doing and what he was using in the original post I missed where he said he was using Firefox at the end of a line that talked about CPU usage half way down the page at the bottom of a post. I read up to that point of that line and never saw the end since the CPU usage was not an important factor for the solution. Yet his reply to me was to point out he had already said that in a previous post. Fine, he can figure it out for himself if thats his way of addressing me and as far as OINC, unless your willing to work with others to allow them to test it the way they feel comfortable with a new product then live with what you get! You don't hear me crying about the fact that very few people did anything with the MMFDBE and that is something that MMF has needed for years. OINC is an upgrade to an abandoned object that currently can get the job done with a bit of work. What did you expect! Support for MOO comes from this forum as planned and announced when it was dropped by the creators and while it is limited support it gets the job done.

Now if your willing to provide the docs as I ask then I would be willing to even look at setting up a public server as I have several public IP's I could do this with but it will be done under my terms, not yours, so I will wait until you make some docs I can look at and make them available to me. Then I might consider moving my MOO projects that work just fine to OINC. Until then you should stop promoting a product in open forums that is not ready for production as this is causing confusion between what should be used for production and what should not be used for production as you can see in this post as well as others.

And since your so eager to talk about the issues with MOO can you point me to a list of the errors you are talking about? As a Moderator of this site who as been announcing the errors of MOO every chance you get I, as well as other I am sure, will expect one of two things from you.

1. Provide the list of errors your talking about and how they effect the inability to use the MOO API for what we need as developers.

2. Keep your mouth shut and do your job as a Moderator and stop using your position as a Moderator to promote a product that is not fulling working.

We need help that will work in the big picture when we develop for release and as a Moderator you should know better.

K

[Mathias]

My probably biased comment:

I would not use Moo for my online applications, mainly because:

* It's unsafe. I'm talking about the fact that the native Moo server is pretty easy to lag down by DOS'ing it (this might be in the client too, I'm not sure ).

* UDP doesn't work, which is really required for any traffic intensive online game.

* The Moo protocol is not as lightweight as OINC's protocol, which means more traffic in Moo-based games.

* Support for Moo has stopped. We should go towards a new product, like OINC.

* The OINC protocol has a valid protocol reference, which means any developer can implement the OINC protocol in their respective language.

So when Jamie thinks people should test OINC instead, I think he's right to do so.

[biased-likely comment end]

EDIT: Sorry for going offtopic!

[Spike]

I havn't read all this but -

topic