• We have updated our Community Code of Conduct. Please read through the new rules for the forum that are an integral part of Paradox Interactive’s User Agreement.
problem-1.png

The editor doesnt seem to take into account the expanded tech panels sizes.
 
Ver 0.39 has been released.
Download: Here

- Changed the tech editor window size to match the tech tree picture size.
- Abolished reassigning sequential number of the tech name.
- Supported for command: sub_detection

* sub_detection command
It is not in event commands.txt, but it seems to work.
So loading tech trees have failed with some mods.
 
you're still working on it :D great :)

Found this error:

If I want to create unit names this error messange appears and the Editor crushes.



Greez

StahlOpa
 
Last edited:
Found a errors

First, I want to say a BIG THANKS for your great work !!

But I encountered a few errors...

First:

Still a problem with bigger tech-trees. Techs can't be positioned beyond X=999 values. Y values seem to be no problem. Editor is crashing if a Tech item is position is more than X=999.

Second: The values for user models d_rsv_33 to d_rsv_40 and d_01 to d_99 are NOT written back into the division_types.txt file. The Branch of a class for custom units can not be changed!

Third: The values for user models b_rsv_36 to b_rsv_40 and b_01 to b_99 are NOT written back into the brigade_types.txt file. The Branch of a class for custom brigades can not be changed!

and I have two questions about the editor:

a) Are there any plans to expand the editor with the ability to edit scenario files?

b) Are there improvements planed for the TECH Tree Editor for editing the commands and actions of a TECH field? (Effect section)
 
First: Still a problem with bigger tech-trees. Techs can't be positioned beyond X=999 values. Y values seem to be no problem. Editor is crashing if a Tech item is position is more than X=999.
Second: The values for user models d_rsv_33 to d_rsv_40 and d_01 to d_99 are NOT written back into the division_types.txt file. The Branch of a class for custom units can not be changed!
Third: The values for user models b_rsv_36 to b_rsv_40 and b_01 to b_99 are NOT written back into the brigade_types.txt file. The Branch of a class for custom brigades can not be changed!

They will be fixed in the next release.

a) Are there any plans to expand the editor with the ability to edit scenario files?

I'm working on it but its progress is still about 20%.

b) Are there improvements planed for the TECH Tree Editor for editing the commands and actions of a TECH field? (Effect section)

Sorry. I postponed it because it would take much time to investigate.
 
Like this I think (just made this in few secounds, it isn't very great :D)



1: You can choose a Trigger from a library in the three sections AND OR and NOT.

2: Here you wrote the decribtion, automatically with an string to the .csv

3: same like 2, just with the Event-title

4: Event pic!

5: can define number of Actions here and choose for every Action the commands from a library like at 1


Okay, it's more Brainstorming than a real concept, Needs much of work before it has really every important Thing inside.


Greez
StahlOpa
 
Last edited:
Like this I think (just made this in few secounds, it isn't very great :D)



1: You can choose a Trigger from a library in the three sections AND OR and NOT.

2: Here you wrote the decribtion, automatically with an string to the .csv

3: same like 2, just with the Event-title

4: Event pic!

5: can define number of Actions here and choose for every Action the commands from a library like at 1


Okay, it's more Brainstorming than a real concept, Needs much of work before it has really every important Thing inside.


Greez
StahlOpa

+999
That is even beter than my original idea
 
Did you think of map editing? Where is some map editor, but it's slow and not really useful (it can't select many provinces and set them infra to lvl 5 for example).
 
+999
That is even beter than my original idea

Thanks :wub:

@map editing, I think that's not the "most important Thing" atm. It would be very nice, sure, but I think that also makes a lot of work. But an Event Editor, bugfixing etc. is imho much more important.
 
Very nice, makes tech tree editing easier. :)

Some small nitpick:
The editor removes comments that used to be in the tech tree file, I'm assuming it doesn't parse them. If you parsed and saved them as entries that are essentially ignored by the editor, that would be better.
 
Last edited:
You're bloody quick kodak! This is awesome! Last I looked it was only 0.38! Thanks again :)