| Blockland Forums > Suggestions & Requests |
| V13/Blockland update suggestions |
| << < (13/17) > >> |
| Placid:
--- Quote from: pixl on August 27, 2009, 05:42:34 AM ---I want %1 to work on client>chatmessage events ): --- End quote --- You know if you have VCE V5 you can type <var:cl:name> and it shows the name. |
| M:
--- Quote from: Badspot on August 27, 2009, 09:53:22 PM ---The purpose of the moving the client name into a set/get function is to prevent people from changing it and impersonating other users. Your name is your name. You can't be an impersonating friend anymore. Sorry. --- End quote --- I had no intention of using it to impersonate another player, about all I would use it for would be to display classes in a class-based deathmatch. --- Quote from: Badspot on August 27, 2009, 09:53:22 PM --- The Torque resource manager is completely forgeted. It took an incredible amount of effort just to be able to connect to a server, download files, and not crash (there are still some crash/invalid packet bugs in v12 that are fixed for v13). I do not want to rewrite it right now. --- End quote --- I guess that's fair enough, although really it seems to make sense to have it after this long. And those invalid packet fixes sound good. --- Quote from: Badspot on August 27, 2009, 09:53:22 PM ---That isn't even coherent enough to read, let alone program. --- End quote --- Well, the main thing that I meant by this is being able to add conditions to an input event. Design-wise, a dialog which shows when you select an input event (if it allows selecting of conditions) that allows you to select logic by which that input event would be called. ie, onActivate [ If Client BL_ID is 4332 ] -> Client -> ChatMessage [ Hello Clockturn! ] onActivate [ If Client BL_ID is not 4332 ] -> Client -> ChatMessage [ You are not me! Get out of my house. ] Something like a list of values for a class, and you can select any one of the usual input targets to compare a value. Variable events with a better implementation really, but skipping the annoying variable* stuff. Sorry if my explanation is still ass. And what I meant by the stuff at the start was, well, I added some arrows to shift events up and down in the GUI, adding them to the swatch of the line. They appeared fine, but as soon as I changed the input event, they were deleted. So I had to use an absolutely horrible hack to get them to work at all, and even then not very well (I'm not proud of it). |
| Truce:
--- Quote from: M on August 28, 2009, 08:29:30 AM ---I had no intention of using it to impersonate another player, about all I would use it for would be to display classes in a class-based deathmatch. --- End quote --- --- Quote from: Truce on August 27, 2009, 10:14:37 PM ---I think M was trying to mainly get across the ability to add things to a user's name. For example, if I tried setting my shape name to "Badspot", it would instead set it to "Truce [Badspot]". This way it's much easier to display custom statuses/etc in different gamemodes. Not sure if you have reasons of your own about why not to do that, but I personally think that'd both add features for modders and prevent impersonation at the same time. --- End quote --- |
| Regulith:
--- Quote from: Truce on August 28, 2009, 08:33:24 AM --- --- End quote --- This man speaks the truth that I previously didn't see. |
| AGlass0fMilk:
I don't really know what I want in V13 >> Most of my opinions and ideas have been stated by other people. I don't really care about the shapename stuff though. |
| Navigation |
| Message Index |
| Next page |
| Previous page |