RtC - MindWorX Interview

[Serbianbeast]

Can't w8 to see it done. Well tbh can't w8 to start my project in it. Since it's been a while since you said anything about date finishing it, can you be a bit more precize now?

 

[HappyTauren]

Can't w8 to see it done. Well tbh can't w8 to start my project in it. Since it's been a while since you said anything about date finishing it, can you be a bit more precize now?

Probably no, as not all features are listed so far, but I think we should expect a new alpha soon.

 

[Eleandor]

Allow me to ask another question: If I just convert my GUI triggers in WE to text, and import them in a map in the RTC editor, will it work? I currently have no jass knowledge, and as I might not learn it very soon (and with me quite some fellow mappers), I wonder if I could still make my maps work in rtc

 

[SFilip]

Well ATM the WarSocAPI is nowhere near the "usable" state so it's hard to tell.
But once released we'll probably try to make it as friendly towards GUI users as possible (Jass would still be highly recommended though).
Either way simply converting your triggers to Jass will have no effect.

 

[HappyTauren]

You need to triggere everything, even the simplest "heal" ability, experience, and damage. It will not be usable if you have no jass knowledge.

 

[Eleandor]

yes, but those abilities will already be included in the installation, right? I mean, it'd be odd to have all standard jasstriggers installed on each and every (melee) map.

I believe you if you say that converting them into jass won't help, but can I ask why it won't help?

 

[MindWorX]

It wont work, because WarSocAPI will utilize a whole new set of natives, that doesn't work in conjunction with the normal wc3 engine. So any normal triggerwork that the map will have, will only be the server that has now, and the other maps, will react to what the server tells it to do.

 

[SFilip]

> but can I ask why it won't help?
Well to begin with it does absolutely nothing - just shows you how your triggers really look like.

 

[HappyTauren]

GUI is a shadowly language, only by converting it to jass you see what you have really done.

(GUI trigger == Converted Trigger) != Scratch JASS trigger

 

[Rui]

Question, why a new whole set of natives? The ones in-game don't work for the server?

 

[MindWorX]

Some does.. Most does actually... But if you use say... SetUnitPos on one of the maps, they wont happen on the others. You have to make sure it does, hence, i need to replace alot of things.

 

[HappyTauren]

The ingame ones will no longer be compatible, because of syncing issues. You can create unit on 1 comp, and it won't be seen on 2nd comp. It is good for hidden units/etc. though, but not recommended,

 

[Eleandor]

I understand the jass in WE will only partly be compatible with the triggers in a warsoc map, but just for clarification: converting a GUI trigger into text does convert it into jass, right? Else I don't have a clue what the "convert into text" actually does..

Oh, and what I don't understand either (sorry, maybe I'm just dumb) is why you can't send all your actions (like cast the heal spell on a unit) to the server and from there it's sent to all other clients (like I assume it works right now in war3)

 

[SFilip]

> does convert it into jass
Well a better way to put it is "allows you to use Jass".
You see every map's script is Jass, when you add something to your GUI trigger the map's Jass adds a line somewhere that does what you want.
"Convert" just shows this current code you already had, absolutely no changes done. But it allows you full access to Jass after that.

> why you can't send all your actions
Because if one player orders a unit to cast heal and then decides to cancel for example, not all of 30 players might get that cancel order in time and...there we have a desync.

 

[Eleandor]

First question: indeed it doesn't "change" anything to the trigger, as war3 automatically converts the GUI into jass when saving the map (I think so). So all I was wondering is if no custom natives would be used, converting your GUI triggers into jass and then import that jass into your map in rtc would be enough, right?
Well anyway it doesn't matter because you're using other natives

second question: k, explains it

 

[HappyTauren]

you HAVE TO USE CUSTOM NATIVES, else your map fails. GUI-JASS conversion IS JUST LEAVING IT AS IT IS, it WONT WORK.

 

[MR. FJ]

Correct me if im wrong : NO GUI (i have cried myself to sleep every night for the past 3 days)

Edit: i don't like jass... to hard to understand (brain overload)

 

[HappyTauren]

I don't like GUI. It kills your code and map. JASS is also easy to learn, 1 week max to learn it, month to get used to it.

 

[SFilip]

GUI support is not going to happen anytime soon, at least it wont be made by us.

 

[Cheeder]

Since RtC modifies how you CREATE maps and is not actually a part of playing, which is why people pay for the software, i think someone should contact Blizzard and ask if they can have permission to recreate how games are MADE, not played. Since it's basically WE2, and not WCIV, i'd bet you have a good chance of getting permission to do what you need to do to make map creation better. It would also promote WC3 and Blizzard..

And the point to make is that you can't make maps without first buying the software. I'm sure they'd come to terms with whomever is to ask.

 

[SFilip]

RtC modifies both map creation and playing, but it's more focused on the latter as the only change in the editor is a couple more natives mappers can use.