Ridiculous
#19681 posted by Redfield on 2018/05/29 06:30:52
The spam here is utterly pathetic. Metslime is there any plans to modernize this place?
And That Is Modernize?
#19682 posted by anonymous user on 2018/05/29 07:20:21
you are bit obsessed with modernizing, as it were better.
#19683 posted by muk on 2018/05/29 08:53:32
you either just suggested google as a form of help or your in a position to easily be confused with a bot linking to google.
if the former, youre a prick. if the latter, your opinions on literally anything will be nullified by bots posting spam.
:shrug:
#19684 posted by muk on 2018/05/29 08:54:40
also, the place being more modern would remove your position of being confused with bots and having a worthless opinion as a result but :shrug:
Spam
#19685 posted by anonymous user on 2018/05/29 10:59:19
oh hai.
the fact that anyone can post anonymously, without logging in, is a bit silly.
if anon posting was disabled then i think that would remove a lot of the spam problems.
and anyone who is not a spammer who wants to post anonymously is just a malicious dick anyway. will we really miss those posts?
Aw Dang
#19687 posted by Qmaster on 2018/05/29 16:20:10
And here I find myself wishing for the ability to see the IP address again just to see if all these anonymous users are the same guy trolling.
Just Curious
#19688 posted by Kinn on 2018/05/29 16:26:42
What is the reason for allowing anonyposting? Surely spam would drop to a tiny fraction of current levels if only account holders could post, right?
I Could Guess Several ...
#19689 posted by Cocerello on 2018/05/29 18:52:58
- Allows people that want to post but don´t know if will be joining the community, which are usually lurkers which are usually double the number of registered users. If they begin to post easily it will be easier for them to finally join, and we don´t have a surplus of users here on Func, even less recently with the migration to Discord. The more ways to help with that the better.
- Allows to post even if forgetting the password or with account problems. I was in both situations myself.
- Allows for faster posting or posting without having to worry about the password being leaked for those of us that use many computers, with several being public. Have been in this situation some times.
- Allows to post on the work with less problems. I know there are several that do this.
- And the most important: why not? Also, and most important: most of the problem is about people being more hostile to anons that to registered users no matter if they say the same, and we are quite hostile already on certain topics. The problem is no big but its not uncommon to see overreacting when an anon appears.
- And there are many others, really.
Cocerello
#19690 posted by Kinn on 2018/05/29 19:26:02
I only sort of half agree with your post but you do make some valid points.
Maybe a worthwhile change could be to just not allow the Name field to be blank. I can't think of a single reason why anyone wouldn't want to fill in the name field unless it's a shitpost.
#19691 posted by bob on 2018/05/29 21:06:11
80% of the anon posting I'm seeing is anti-anon trying to make some point. Where is all this malicious troll shit posting? I must be reading the wrong threads.
#19692 posted by anonymous user on 2018/05/29 21:27:37
hi bob, you must be new here.
This Sure Is Some Cool Mapping Help Guys
#19693 posted by Kinn on 2018/05/29 21:36:49
(and yes I am aware of the irony)
Kinn
#19694 posted by anonymous user on 2018/05/29 21:43:53
I thought that too, but passed on saying because what that would change is people filling it with anything to pass through that requirement.
I can't think of a single reason why anyone wouldn't want to fill in the name field unless it's a shitpost.
Fear of verbal reprisal or harrasing from the most vocal parts of the community when talking about certain topics that are considered taboo, or those considered holy by some fans. Or to summarize, cowardy.
Yep
#19695 posted by Cocerello on 2018/05/29 21:48:33
i think i can solve that. A random question, let's see ... if i turn a brush entity like a trigger into a point entity to avoid a limit, does it still keep the bbox? Does the player need to go to the point to trigger it?
By the way, the previous meessage was me. Forgot to put the nick.
Mapping Help 2: Anon Conversation Boogaloo
#19696 posted by Kinn on 2018/05/29 21:52:06
I was thinking about it from an anti-spam perspective. I'll concede that if blocking anon posting is not an option, then I'm all out of ideas of how spam and shitposting can be reduced.
Mapping Help Probably Includes Entity Help.
#19697 posted by Shambler on 2018/05/30 12:11:16
Entity Enemy Help. [EDIT]
Posted by kibbles on 2018/05/29 01:08:43
I've been searching for information on how to make monsters attack other types. Is there a way to do this within worldcraft? I can't find the entity index online
#1 posted by kibbles on 2018/05/29 01:10:46 spam
I tested smartedit adding enemy 6 to key and values to a monster enemy and placed all the monsters near it, he didn't attack
He Protec But He Also Attac
#2 posted by anonymous user on 2018/05/29 01:19:28 spam
Post in Mapping Help if you don't want a smac.
Need Help With Mapping?
#3 posted by anonymous user on 2018/05/29 01:23:35 spam
Get in line like everybody and ask in mapping help thread.
#4 posted by mankrip on 2018/05/29 03:04:44 spam
IIRC, in vanilla Quake the .enemy reference is cleared by the QC code during entity initialization. You need custom QC code.
Make Enemies Atrack
#19698 posted by Qmaster on 2018/05/30 20:45:55
I had a thought just now...if you make a trigger hurt, and set the .owner field to the edict number of another monster, then drop a monster into the hurt trigger, and cleanup by killtargetting the hurt trigger soon after...runs off to double check T_Damage code.
Make Enemies Atrack
#19699 posted by Qmaster on 2018/05/30 20:46:43
I had a thought just now...if you make a trigger hurt, and set the .owner field to the edict number of another monster, then drop a monster into the hurt trigger, and cleanup by killtargetting the hurt trigger soon after...runs off to double check T_Damage code.
|