![]() |
Setmap will be disabled soon
The old setmap feature to connect levels will be removed in the next Graal version. Servers that still use it should switch to gmaps. I've seen that Delteria and N-Pulse still use it, hope it will not be a big problem.
The setminimap function will still work (although not required with gmaps). |
Will it still work offline?
|
Quote:
|
Quote:
|
There will not be a new editor yet. Converting setmap to gmap is normally quite easy, you can open an existing gmap to see where to put the level filenames.
|
Quote:
|
Quote:
Quote:
|
If you ask me, Stefan should just throw together some libs we can use to code our own new tools. I would be pleased.
|
There is no need, external scripting windows will soon be possible and I'm sure Stefan would want new tools created with GS2 so that those on Mac and other supported Systems could use them too.
|
Quote:
|
Quote:
Scripted tools will never match external ones, external windows or not. |
Quote:
|
Why can't they match the external versions?
|
Quote:
|
Well, there's tons of reasons that have been listed over the years.
If you're not scripting it, then there's no reason for there not to be a scripted editor. It won't steal any of your time away, order your slaves to get it done. I don't have a problem with it, just like the RC. I don't have a problem with the fact RC is scripted, it has its uses. BUT, if you're not scripting these tools, so you no longer spend time on tools for Graal, why is it so hard to ask for the external tools to be updated? Its not like you'll be working double time scripting the internal tools and coding the external ones. From my experiences with client-RC, I don't think internal tools will ever match the performance of external tools. They're sluggish, they carry the faults of the GUI interface, they reflect the performance of the client. Take for example... hmm, a gani editor(I assume this will be scripted as well?). Right now I can open up my gani editor and edit some gani's. It works full speed, no slow-down... its a simple application. But, I suspect, just like with RC, if I were to be using this as a tool in Graal, its performance would drop because Graal itself isn't that fast on my computer. Also the fact that internal tools will never have the flexibility of external. It's programming vs interpreted. The tools will be as limited as the security and flexibility of GS2. I mean, I do see the benefits of scripted tools... but personally for me they end up just being fail-safes. Like... "hmm, I'm not home so I won't bother installing the editor to edit this level, I'll just use the scripted one!" And that's about it. Scripted RC is a great accomplishment, and really pushes the limits of GS2... but as far as using it goes, I'll just stick to my external RC. If you're not doing the scripting(and therefor, not dividing your time between scripting AND coding) why are you so determined to abandon tools that are basically there and just need to be updated? |
The level editor and Graal Shop are basically just writing text files, I don't see the problem with giving us the source code for such programs.
Or maybe someone should just create their own using Python (which I recommend). |
Quote:
- What would Stefan and Unixmad think? - How would you implement GS2 support? - Wouldn't it be best if the editors became open-source so we can see the correct routines? That way, it'd be much easier. |
I would much prefer having the source codes myself.
|
Quote:
Plus, it'd be nice to see some sort of open-source activity in this community, which steps beyond just scripting. |
Sorry this has nothing to do with "setmap". The level editor is v2, we wont release the code for that. The scripted RC will replace the old RC in the near future, it's much easier to update and to improve and will also fix some several bugs with the current RC. The other tools will go the same way, probably first the level editor or an extension to the RCs npc-editor.
A big part of Graal is already open source, e.g. many scripts are available on the forums. |
Quote:
Quote:
I'm sure it is easier... but it seems more like cutting corners. I'm sure there are tons of easier paths to take, but sometimes it's not always the best way to do it. I can't seem to find too many other people who agree with the tools going fully scripted, so how exactly is this going to help if no one agrees? |
Quote:
Quote:
Quote:
I'm sure this would just make things a lot harder for people like Tig, with his horrendous latency. Also, why can't you just fix the bugs in the external RC? Keeping everything contain in just on executable isn't such a good idea :/ Quote:
It's quite clear that the majority, if not all, of the developers want updated external tools. Your biggest pitfall is you're just not LISTENING. We don't want "scripted tools with external windows", we want an updated external executable tools. Surely, if you had the brains for business, you'd fulfill this obvious necessity in the development community - developers are currently your most important players, as it seems. The idea for making the tools open-source was in response to your ultimate decision NOT to update external tools. To sum things up, here are some major, MAJOR issues I have with this:
|
External tools are much more work, much harder to update, less customizable, always lag behind in number of features, and mean double or triple effort. By improving the scripted tools we can at the same time improve Graal drastically, e.g. the scripted playerlist which should make things quite interesting. If you are neglecting all that and still stick to the 80s/90s idea of offline stuff then I don't know how I can convince you anymore.
|
Quote:
Edit: 80s/90s stuff? Excuse me? Last time I checked my developing tools didnt require a game to use them. |
People are requesting a lot of stuff, and we must decide how we do the things with the best strategy. Doing the things we planned, we can do:
- make the tools work on all platforms - make them customizable and easily updatable - having them always up-to-date There is a "downfall": you have to be online to script, you have to be online for modifying the game. But at the end this is an online game, you will need to chat with other people, you will need to watch documentation or code examples, you will need to test and debug the things you have worked on. All that requires online connectibility. So at the end that "downfall" can even be an advantage, because it forces people to speak and work together. If you want to learn C++ then learn C++, but don't start speaking about the easyness of making platform independent tools or similar. |
Quote:
|
Quote:
Have you ever felt the difference between scripted RC and external RC? Have you ever felt the difference between an OLE and the external level editor? Don't you know what it'd be like if my internet goes down and I cannot develop, mainly because you've made it so? I have no animosity towards you, Stefan but I have much animosity towards this whole idea of shifting towards a complete online, you-have-to-pay-to-develop idea. I don't think it's going to make you any money. PS: The playerlist is completely different from scripted tools. Having the above, I'm going to wait for the external windows to be implemented and see how things pan out. For scripted tools to be effective, they have to have exact or, if not, better functionality than the offline tools. |
Stefan, perhaps you could tell us the speed difference between the external scripted windows and the external RC? Specifically when editing large (hundreds of lines) script files?
|
uh, i hate the internal rc for going fullscreen everytime i write
PHP Code:
|
The scripted RC window is already faster for me now, the external RC often has problems when scrolling. The GuiMLTextCtrl can probably be optimized more though to only process the inserted text or the added text instead of parsing the whole text again when a modification has been made.
|
Quote:
|
Quote:
|
Quote:
Some people here really take stuff too much to their heart >_< Also the old RC doesn't even exist for Mac ? :confused: |
Quote:
Quote:
Quote:
|
Well Firefox plugins are not working on all platforms, they need to reprogrammed and repackaged for each platform. If you mean Firefox extensions, those are scripted :D
What do you mean with dragndrop, for scripting (?) or for file downloading? Normally it shoud already work for file uploading. |
Quote:
No, dragging and dropping for file browser does not seem to be working. Also, I apologize for getting mad about RC. Here's for everyone else: I have tried the external windows (testing ftw), and they work GREAT. A few bugs, but scripting is MUCH easier. Definitely it is fast enough to script. I did not think it would be as good as it is, but it definitely is better than I thought. It is running very well ... taking very, very little of my CPU. I'll report the bugs for it once I've had a bit more time to play with it -- no doubt I'll find some more. But seriously, it is really not that bad at all. I do believe that with a little work this could really replace the external RC. |
Quote:
|
1 Attachment(s)
rawr
|
How? :(
|
Quote:
|
| All times are GMT +2. The time now is 02:29 PM. |
Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2026, vBulletin Solutions Inc.
Copyright (C) 1998-2019 Toonslab All Rights Reserved.